taskuary 0.3.3.1__tar.gz → 0.3.3.2__tar.gz

{taskuary-0.3.3.1/taskuary.egg-info → taskuary-0.3.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: taskuary
-Version: 0.3.3.1
+Version: 0.3.3.2
 Summary: Automate your job - the local-first operating system for your work: AI triage in, coding agents out.
 License: MIT
 Project-URL: Homepage, https://github.com/ldbumble/taskuary
@@ -62,22 +62,18 @@ Dynamic: license-file
 # Taskuary
 
 [![CI](https://github.com/ldbumble/taskuary/actions/workflows/ci.yml/badge.svg)](https://github.com/ldbumble/taskuary/actions/workflows/ci.yml)
-[![PyPI](https://img.shields.io/pypi/v/taskuary.svg?cacheSeconds=600)](https://pypi.org/project/taskuary/)
+[![PyPI](https://img.shields.io/pypi/v/taskuary.svg?cacheSeconds=300&release=0.3.3.2)](https://pypi.org/project/taskuary/)
 [![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-3776ab.svg)](https://github.com/ldbumble/taskuary)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 
-## Your inbox, staffed by AI agents.
+## Your inbox, staffed by AI agents
 
-Taskuary brings your mail, chats, issues, and scheduled reports into one local conversation:
-a live work pipe on the left and chat on the right. AI triage decides what is real work,
-your coding CLI works the tasks in your own repos, and replies wait for your approval.
-Nothing sends or ships without you.
+Taskuary turns incoming messages into organized work. It sorts what matters, hands tasks to
+your agents, and brings decisions back to you. Nothing sends or ships without your approval.
 
-![The Taskuary Studio: work arrives, triage decides what needs action, and agents take seats to work it.](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/hero.gif)
+![Taskuary: the pipe ranked by triage beside the assistant chat - a mail pulled in with its drafted reply, the Timeline in task view, the Reports and the Board.](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/hero.gif)
 
-Taskuary is early—currently **v0.3.3.1**—and moving fast. The funnel, review queue,
-agent sessions, and reports pipeline are in daily use; breaking changes are still possible
-before 1.0.
+Taskuary is early—currently **v0.3.3.2**—so breaking changes are still possible before 1.0.
 
 <p align="center">
   <a href="https://taskuary.com/demo/"><img
@@ -85,43 +81,61 @@ before 1.0.
     alt="Try Taskuary now, in your browser"></a>
 </p>
 
-<p align="center"><sub>The real app over invented work — the unified pipe and chat, triage,
-a coding session mid-run, and reports with charts. Nothing to install and nothing connects
-to anything.</sub></p>
+<p align="center"><sub>The real app with invented data. Nothing connects, sends, or runs.</sub></p>
 
-## One timeline, one chat
+## What Taskuary can do
 
-Outlook, Gmail, Teams, Slack, Telegram, WhatsApp, GitHub, Jira, alerts, and reports all
-arrive in the pipe beside the same conversation. **Unread** is the prioritized walkthrough;
-**All** is the recent timeline. Click any row—or name a sender, subject, or task in chat—to
-pull it into the conversation with its context, triage reasoning, draft, and available actions.
+**One Timeline and Assistant**
+
+Mail, chats, issues, alerts, and reports appear on one Timeline and in one Assistant chat.
+Open any item to see its context, status, and available actions.
 
 ![Taskuary's unified work pipe and chat, populated only with fictional demo data.](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-chat.png)
 
-*Everything shown is generated by the built-in demo. Dana Whitfield, Northwind Facilities,
-the people, messages, repositories, tasks, and reports are all fictional.*
-
-The same conversation also speaks up when something falls between tasks: a reply went
-unanswered, a meeting needs context, a task went quiet, or a pattern appears across the
-week's work. Each observation carries its evidence and can be acted on, dismissed, snoozed,
-or taught away with **Not this**. These observations now appear in this same chat instead of
-as separate Assistant posts on the Timeline.
-
-These checks can watch the systems you run on, not only incoming messages. Point one at a
-Sage Intacct query, a database, a file, a REST or MCP tool, a cloud log group, or an agent
-skill—no saved report has to stand behind it—and Taskuary reads it silently on schedule.
-Describe what a check should watch and AI can write the source cards using only connected
-systems, after reading their real schema and asking rather than guessing a filter. The same
-help sits on every source card in the report builder. Voice, schedule, model, and thresholds
-remain yours to change; a check stays silent when there is nothing useful to add to the chat.
-
-Coding work can go straight to Claude Code, Codex, Gemini, Cursor, Copilot, or any CLI that
-accepts a prompt on stdin. You watch the live terminal, answer questions, review the diff,
-and approve what happens next. Research, marketing, and other general work belong in a
-conversational workspace built with assistant-ui and your existing Taskuary AI connections.
-Chat and terminal are two views of the same session: model, history, queued instructions,
-image attachments, and the side-by-side browser stay put when you switch. The same workspace
-also appears on the Wall.
+**AI triage**
+
+Triage files routine updates, turns real requests into tasks, and puts urgent decisions first.
+
+**Agents in your own repos**
+
+Send coding work to Claude Code, Codex, Gemini, Cursor, Copilot, or another CLI.
+
+**Live workspaces**
+
+Watch the terminal, answer questions, review changes, and use the built-in browser without
+losing the session.
+
+**Scheduled checks**
+
+Watch databases, files, APIs, cloud logs, reports, or agent skills. Quiet checks stay silent.
+
+**You stay in control**
+
+Replies and proposed actions wait in Review. You decide what sends, runs, closes, or gets dismissed.
+
+**Catches what slipped**
+
+Surface unanswered replies, upcoming meetings, quiet tasks, failed reports, and important changes.
+
+## How work flows
+
+### 1. Work arrives and gets sorted
+
+Taskuary reads connected inboxes, separates tasks from noise, and shows the result on one Timeline.
+
+![The Timeline in task view: every message with its verdict, and the drafted reply waiting on you](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-timeline-crop.png)
+
+### 2. An agent works on it
+
+Tasks move from **Queued** to **Agent working**. The Board shows live progress and anything waiting on you.
+
+![Taskuary Board with queued, active, and waiting work](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-board.png)
+
+### 3. The result comes back to you
+
+Finished work, draft replies, questions, and loose ends return for review. You decide what to send, change, snooze, or dismiss.
+
+![Taskuary assistant showing loose ends and suggested actions](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-assistant.png)
 
 ## Install
 
@@ -164,25 +178,15 @@ connection before it goes live.
 taskuary --demo                    # or: docker compose --profile demo up
 ```
 
-A full Taskuary over invented work — a morning's mail and chats already triaged with the
-reasons attached, drafts waiting in Review, agents on the board with their transcripts
-playing, live task handoffs on the Board, and the durable, high-signal company Hub.
-Every Hub post names its human or agent author and originating task; Board handoffs are short-lived
-checkout coordination that rolls up nightly. The AI answers from a script and every door
-to the outside world is shut at the API layer (`taskuary/demo.py`): nothing sends, no
-connection can be made or edited, no tool runs, and no CLI starts. Nobody's real data is in
-it — Dana Whitfield and Northwind Facilities are invented.
+The demo is the real interface with fictional work and scripted replies. It cannot connect to
+outside systems, send messages, run tools, or start agents. Its changes reset when you reload.
 
 ## Installs
 
 ![Daily installs of taskuary from PyPI, mirror traffic excluded](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/downloads.svg)
 
-Redrawn every morning by [`downloads.yml`](.github/workflows/downloads.yml) from PyPI's own
-numbers, with mirror traffic excluded — a full PyPI mirror pulls every release, so counting it
-would let a handful of real users read as hundreds. What it does **not** claim is that CI
-installs have been removed: the field that would separate `pip install` in a build runner from
-one on somebody's laptop is in PyPI's BigQuery dataset, not in the public API. The daily series
-is [docs/downloads.csv](docs/downloads.csv).
+Updated daily from PyPI with mirror traffic excluded. The raw series is
+[docs/downloads.csv](docs/downloads.csv).
 
 ## Documentation
 

taskuary-0.3.3.2/README.md

@@ -0,0 +1,140 @@
+# Taskuary
+
+[![CI](https://github.com/ldbumble/taskuary/actions/workflows/ci.yml/badge.svg)](https://github.com/ldbumble/taskuary/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/taskuary.svg?cacheSeconds=300&release=0.3.3.2)](https://pypi.org/project/taskuary/)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-3776ab.svg)](https://github.com/ldbumble/taskuary)
+[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
+
+## Your inbox, staffed by AI agents
+
+Taskuary turns incoming messages into organized work. It sorts what matters, hands tasks to
+your agents, and brings decisions back to you. Nothing sends or ships without your approval.
+
+![Taskuary: the pipe ranked by triage beside the assistant chat - a mail pulled in with its drafted reply, the Timeline in task view, the Reports and the Board.](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/hero.gif)
+
+Taskuary is early—currently **v0.3.3.2**—so breaking changes are still possible before 1.0.
+
+<p align="center">
+  <a href="https://taskuary.com/demo/"><img
+    src="https://img.shields.io/badge/%E2%96%B6%20Try%20it%20now-no%20install%2C%20in%20your%20browser-2f4858?style=for-the-badge&labelColor=1f2a22"
+    alt="Try Taskuary now, in your browser"></a>
+</p>
+
+<p align="center"><sub>The real app with invented data. Nothing connects, sends, or runs.</sub></p>
+
+## What Taskuary can do
+
+**One Timeline and Assistant**
+
+Mail, chats, issues, alerts, and reports appear on one Timeline and in one Assistant chat.
+Open any item to see its context, status, and available actions.
+
+![Taskuary's unified work pipe and chat, populated only with fictional demo data.](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-chat.png)
+
+**AI triage**
+
+Triage files routine updates, turns real requests into tasks, and puts urgent decisions first.
+
+**Agents in your own repos**
+
+Send coding work to Claude Code, Codex, Gemini, Cursor, Copilot, or another CLI.
+
+**Live workspaces**
+
+Watch the terminal, answer questions, review changes, and use the built-in browser without
+losing the session.
+
+**Scheduled checks**
+
+Watch databases, files, APIs, cloud logs, reports, or agent skills. Quiet checks stay silent.
+
+**You stay in control**
+
+Replies and proposed actions wait in Review. You decide what sends, runs, closes, or gets dismissed.
+
+**Catches what slipped**
+
+Surface unanswered replies, upcoming meetings, quiet tasks, failed reports, and important changes.
+
+## How work flows
+
+### 1. Work arrives and gets sorted
+
+Taskuary reads connected inboxes, separates tasks from noise, and shows the result on one Timeline.
+
+![The Timeline in task view: every message with its verdict, and the drafted reply waiting on you](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-timeline-crop.png)
+
+### 2. An agent works on it
+
+Tasks move from **Queued** to **Agent working**. The Board shows live progress and anything waiting on you.
+
+![Taskuary Board with queued, active, and waiting work](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-board.png)
+
+### 3. The result comes back to you
+
+Finished work, draft replies, questions, and loose ends return for review. You decide what to send, change, snooze, or dismiss.
+
+![Taskuary assistant showing loose ends and suggested actions](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-assistant.png)
+
+## Install
+
+### Windows app
+
+Download the latest single-file
+[Taskuary.exe](https://github.com/ldbumble/taskuary/releases/latest/download/Taskuary.exe)
+and open it. No Python or installer is required.
+
+### Python
+
+Python 3.10 or newer works on Windows, macOS, and Linux:
+
+```bash
+pip install taskuary
+taskuary
+```
+
+Taskuary opens at [http://127.0.0.1:7787](http://127.0.0.1:7787). For a native desktop
+window instead, install `pip install "taskuary[desktop]"` and run `taskuary-desktop`.
+
+### Docker
+
+```bash
+git clone https://github.com/ldbumble/taskuary
+cd taskuary
+docker compose up
+```
+
+Then open [http://127.0.0.1:7787](http://127.0.0.1:7787). Docker runs the web app;
+coding CLIs and the optional WhatsApp bridge remain on the host.
+
+On first run, connect an AI provider or local Ollama model, add at least one inbound
+channel, then choose the coding CLI that should receive tasks. The setup wizards test each
+connection before it goes live.
+
+## Try it without installing anything
+
+```bash
+taskuary --demo                    # or: docker compose --profile demo up
+```
+
+The demo is the real interface with fictional work and scripted replies. It cannot connect to
+outside systems, send messages, run tools, or start agents. Its changes reset when you reload.
+
+## Installs
+
+![Daily installs of taskuary from PyPI, mirror traffic excluded](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/downloads.svg)
+
+Updated daily from PyPI with mirror traffic excluded. The raw series is
+[docs/downloads.csv](docs/downloads.csv).
+
+## Documentation
+
+- [Getting started](docs/getting-started.md)—installation, first-run setup, Docker, and data
+- [Product guide](docs/product-guide.md)—the workflow, learning loop, agents, and operator documents
+- [Integrations](docs/integrations.md)—channels, AI providers, work systems, and report sources
+- [Reports and proactive checks](docs/reports-and-assistant.md)—the report pipeline, AI-written source cards, and what Taskuary watches
+- [Status and roadmap](docs/roadmap.md)—what works today and what is next
+- [Contributing](CONTRIBUTING.md)—development setup and contribution guide
+
+Taskuary is free and open source under the [MIT License](LICENSE). Issues and pull requests
+are welcome; security reports belong in [SECURITY.md](SECURITY.md).

{taskuary-0.3.3.1 → taskuary-0.3.3.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "taskuary"
-version = "0.3.3.1"
+version = "0.3.3.2"
 description = "Automate your job - the local-first operating system for your work: AI triage in, coding agents out."
 readme = "README.md"
 license = { text = "MIT" }

{taskuary-0.3.3.1 → taskuary-0.3.3.2}/taskuary/terminal.py

@@ -544,9 +544,9 @@ def open_session(store, agent: str = None, task_id: int = None, repo: str = None
         row = store.get_agent(agent)
         if not row: raise ValueError(f'unknown agent: {agent}')
         profile = json.loads(row.get('Config') or '{}')
-        argv, label = agent_argv(profile, model), agent
+        label = agent
     else:
-        argv, label = default_shell(), 'shell'
+        label = 'shell'
     # A named repo with no path used to fall through to the agent's default folder, so a task about
     # one system opened a session in another and the agent edited the wrong tree in good faith.
     # Refuse instead: not starting is recoverable, working the wrong checkout is not.
@@ -578,6 +578,10 @@ def open_session(store, agent: str = None, task_id: int = None, repo: str = None
         if len(paths) == 1: cwd = next(iter(paths.values()))
     cwd = cwd or profile.get('cwd') or os.getcwd()
     if not os.path.isdir(cwd): raise ValueError(f'working directory does not exist: {cwd}')
+    # WHICH CHECKOUT comes first, and only then which binary: resolving the CLI up here meant a box
+    # without it answered "'claude' not found on PATH" to a task whose real problem was that nothing
+    # said where it belonged - the wrong sentence, and the one the owner cannot act on.
+    argv = agent_argv(profile, model) if agent else default_shell()
     if agent:
         try: pretrust(cwd, ' '.join(str(a) for a in argv))     # no first-run dialog to park on
         except Exception as e: logger.debug(f'pretrust skipped: {e}')