taskuary 0.2.0__tar.gz → 0.2.1__tar.gz

{taskuary-0.2.0/taskuary.egg-info → taskuary-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: taskuary
-Version: 0.2.0
+Version: 0.2.1
 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
@@ -51,6 +51,7 @@ Dynamic: license-file
 [![CI](https://github.com/ldbumble/taskuary/actions/workflows/ci.yml/badge.svg)](https://github.com/ldbumble/taskuary/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 [![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-3776ab.svg)](https://github.com/ldbumble/taskuary)
+[![PyPI](https://img.shields.io/pypi/v/taskuary.svg)](https://pypi.org/project/taskuary/)
 [![PRs welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](CONTRIBUTING.md)
 [![GitHub stars](https://img.shields.io/github/stars/ldbumble/taskuary?style=social)](https://github.com/ldbumble/taskuary/stargazers)
 
@@ -60,7 +61,7 @@ Dynamic: license-file
 scheduled reports land on one timeline; AI triage says what is real work; the coding CLI
 you already use does it; you approve the result. Runs entirely on your machine.
 
-![Taskuary in use: the timeline of email, chats and scheduled reports; a mail opened to show why triage made it a task and the AI reply drafted for approval; a scheduled report landing with its bar chart and spreadsheet; the Reports pipeline list; and the agent board with live sessions and the note one agent left the next](docs/hero.gif)
+![Taskuary in use: the timeline of email, chats and scheduled reports; a mail opened to show why triage made it a task and the AI reply drafted for approval; a scheduled report landing with its bar chart and spreadsheet; the Reports pipeline list; and the agent board with live sessions and the note one agent left the next](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/hero.gif)
 
 <sub>Real app, real data — a mail triaged and its reply drafted for your approval, then a scheduled SQL report landing on the same rail with its chart and spreadsheet. Nothing sends without you.</sub>
 
@@ -92,7 +93,7 @@ sender (yours to review under Settings → Agent memory).
 
 The general lessons take a stricter road, so one odd Tuesday never becomes a rule:
 
-![Your verdicts become a hypothesis with score s:2; agreeing verdicts add a point and contradictions remove one; at s:4 with proof from two or more people it is promoted into LEARNED.md, which then rides into every triage, draft and agent run](docs/learning-loop.svg)
+![Your verdicts become a hypothesis with score s:2; agreeing verdicts add a point and contradictions remove one; at s:4 with proof from two or more people it is promoted into LEARNED.md, which then rides into every triage, draft and agent run](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/learning-loop.svg)
 
 **How the memory works, concretely.** Each lesson is one line in `LEARNED.md` (Docs tab) —
 a guess with a score. Say you strip the greeting off three drafts this week; the file soon
@@ -129,7 +130,7 @@ markers always survive. What each one feeds from then on:
 ## Get started
 
 ```bash
-pip install git+https://github.com/ldbumble/taskuary
+pip install taskuary
 taskuary        # opens http://127.0.0.1:7787
 ```
 
@@ -161,7 +162,7 @@ No cloud key at all? Set **Settings → Triage & routing → Triage brain** to y
 and skip step 1 — one brain does everything, slower and pricier per message. See
 [One brain or two](#one-brain-or-two).
 
-Prefer a desktop app? `pip install "taskuary[desktop] @ git+https://github.com/ldbumble/taskuary"`
+Prefer a desktop app? `pip install "taskuary[desktop]"`
 then `taskuary-desktop` — the same UI in a native window. A prebuilt single-file
 `Taskuary.exe` is attached to every CI run.
 
@@ -215,7 +216,7 @@ with no AI connected messages file visibly instead of heuristics spraying tasks.
 
 ## Many agents, one repo — no stepping on each other
 
-![Two agents share one checkout: each working card shows the files ITS agent has modified (claude in the theme files, codex in the report code and its tests), and a third task waits in Queued with the reason written on the card — waiting on TQ-0009, both would modify ReportsView.jsx, starts by itself when it can](docs/screenshot-board.png)
+![Two agents share one checkout: each working card shows the files ITS agent has modified (claude in the theme files, codex in the report code and its tests), and a third task waits in Queued with the reason written on the card — waiting on TQ-0009, both would modify ReportsView.jsx, starts by itself when it can](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-board.png)
 
 Auto-dispatch can put several CLIs to work at once — and the board keeps them out of each
 other's way with three light moves. No locks, no worktrees, no manager agent:
@@ -265,7 +266,7 @@ Plain markdown, all on the Docs tab, all yours to edit. Three you write, two wri
 themselves, and two can **bootstrap themselves from your mail history** (`TRIAGE.md` and
 `STYLE.md` — the Generate from history button). Each feeds exactly the calls it belongs in.
 
-![TRIAGE.md, STYLE.md, SOUL.md and LEARNED.md feed triage and replies on the cheap model; SOUL.md, CODER.md and LEARNED.md feed coding agents on your CLI; DIGEST.md is your own morning read — and TRIAGE.md and STYLE.md can be generated from three months of your own mail](docs/six-docs.svg)
+![TRIAGE.md, STYLE.md, SOUL.md and LEARNED.md feed triage and replies on the cheap model; SOUL.md, CODER.md and LEARNED.md feed coding agents on your CLI; DIGEST.md is your own morning read — and TRIAGE.md and STYLE.md can be generated from three months of your own mail](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/six-docs.svg)
 
 | document | what it is | who reads it |
 |---|---|---|

{taskuary-0.2.0 → taskuary-0.2.1}/README.md

@@ -3,6 +3,7 @@
 [![CI](https://github.com/ldbumble/taskuary/actions/workflows/ci.yml/badge.svg)](https://github.com/ldbumble/taskuary/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 [![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-3776ab.svg)](https://github.com/ldbumble/taskuary)
+[![PyPI](https://img.shields.io/pypi/v/taskuary.svg)](https://pypi.org/project/taskuary/)
 [![PRs welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](CONTRIBUTING.md)
 [![GitHub stars](https://img.shields.io/github/stars/ldbumble/taskuary?style=social)](https://github.com/ldbumble/taskuary/stargazers)
 
@@ -12,7 +13,7 @@
 scheduled reports land on one timeline; AI triage says what is real work; the coding CLI
 you already use does it; you approve the result. Runs entirely on your machine.
 
-![Taskuary in use: the timeline of email, chats and scheduled reports; a mail opened to show why triage made it a task and the AI reply drafted for approval; a scheduled report landing with its bar chart and spreadsheet; the Reports pipeline list; and the agent board with live sessions and the note one agent left the next](docs/hero.gif)
+![Taskuary in use: the timeline of email, chats and scheduled reports; a mail opened to show why triage made it a task and the AI reply drafted for approval; a scheduled report landing with its bar chart and spreadsheet; the Reports pipeline list; and the agent board with live sessions and the note one agent left the next](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/hero.gif)
 
 <sub>Real app, real data — a mail triaged and its reply drafted for your approval, then a scheduled SQL report landing on the same rail with its chart and spreadsheet. Nothing sends without you.</sub>
 
@@ -44,7 +45,7 @@ sender (yours to review under Settings → Agent memory).
 
 The general lessons take a stricter road, so one odd Tuesday never becomes a rule:
 
-![Your verdicts become a hypothesis with score s:2; agreeing verdicts add a point and contradictions remove one; at s:4 with proof from two or more people it is promoted into LEARNED.md, which then rides into every triage, draft and agent run](docs/learning-loop.svg)
+![Your verdicts become a hypothesis with score s:2; agreeing verdicts add a point and contradictions remove one; at s:4 with proof from two or more people it is promoted into LEARNED.md, which then rides into every triage, draft and agent run](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/learning-loop.svg)
 
 **How the memory works, concretely.** Each lesson is one line in `LEARNED.md` (Docs tab) —
 a guess with a score. Say you strip the greeting off three drafts this week; the file soon
@@ -81,7 +82,7 @@ markers always survive. What each one feeds from then on:
 ## Get started
 
 ```bash
-pip install git+https://github.com/ldbumble/taskuary
+pip install taskuary
 taskuary        # opens http://127.0.0.1:7787
 ```
 
@@ -113,7 +114,7 @@ No cloud key at all? Set **Settings → Triage & routing → Triage brain** to y
 and skip step 1 — one brain does everything, slower and pricier per message. See
 [One brain or two](#one-brain-or-two).
 
-Prefer a desktop app? `pip install "taskuary[desktop] @ git+https://github.com/ldbumble/taskuary"`
+Prefer a desktop app? `pip install "taskuary[desktop]"`
 then `taskuary-desktop` — the same UI in a native window. A prebuilt single-file
 `Taskuary.exe` is attached to every CI run.
 
@@ -167,7 +168,7 @@ with no AI connected messages file visibly instead of heuristics spraying tasks.
 
 ## Many agents, one repo — no stepping on each other
 
-![Two agents share one checkout: each working card shows the files ITS agent has modified (claude in the theme files, codex in the report code and its tests), and a third task waits in Queued with the reason written on the card — waiting on TQ-0009, both would modify ReportsView.jsx, starts by itself when it can](docs/screenshot-board.png)
+![Two agents share one checkout: each working card shows the files ITS agent has modified (claude in the theme files, codex in the report code and its tests), and a third task waits in Queued with the reason written on the card — waiting on TQ-0009, both would modify ReportsView.jsx, starts by itself when it can](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-board.png)
 
 Auto-dispatch can put several CLIs to work at once — and the board keeps them out of each
 other's way with three light moves. No locks, no worktrees, no manager agent:
@@ -217,7 +218,7 @@ Plain markdown, all on the Docs tab, all yours to edit. Three you write, two wri
 themselves, and two can **bootstrap themselves from your mail history** (`TRIAGE.md` and
 `STYLE.md` — the Generate from history button). Each feeds exactly the calls it belongs in.
 
-![TRIAGE.md, STYLE.md, SOUL.md and LEARNED.md feed triage and replies on the cheap model; SOUL.md, CODER.md and LEARNED.md feed coding agents on your CLI; DIGEST.md is your own morning read — and TRIAGE.md and STYLE.md can be generated from three months of your own mail](docs/six-docs.svg)
+![TRIAGE.md, STYLE.md, SOUL.md and LEARNED.md feed triage and replies on the cheap model; SOUL.md, CODER.md and LEARNED.md feed coding agents on your CLI; DIGEST.md is your own morning read — and TRIAGE.md and STYLE.md can be generated from three months of your own mail](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/six-docs.svg)
 
 | document | what it is | who reads it |
 |---|---|---|

{taskuary-0.2.0 → taskuary-0.2.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "taskuary"
-version = "0.2.0"
+version = "0.2.1"
 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.2.0 → taskuary-0.2.1}/taskuary/agents.py

@@ -59,7 +59,10 @@ def _shim_target(path: str) -> list:
     here = os.path.dirname(path)
     found = []
     for tok in re.findall(r'"([^"]+)"', txt):
-        real = os.path.normpath(tok.replace('%dp0%', here).replace('%~dp0', here))
+        # a batch file always writes \ - a separator on Windows, an ordinary character
+        # everywhere else. Translating it means this parser can be exercised by CI on
+        # Linux and macOS too, rather than only on the platform that has the bug.
+        real = os.path.normpath(tok.replace('%dp0%', here).replace('%~dp0', here).replace(chr(92), os.sep))
         if os.path.isfile(real) and real.lower().endswith(('.exe', '.js')): found.append(real)
     exe = next((f for f in found if f.lower().endswith('.exe')), None)
     js = next((f for f in found if f.lower().endswith('.js')), None)

{taskuary-0.2.0 → taskuary-0.2.1}/taskuary/terminal.py

@@ -636,6 +636,18 @@ def _cut(text: str, n: int, what: str = 'message') -> str:
             'Ask the owner for the rest before assuming anything past this point.]')
 
 
+# An agent working a repository has no use for anybody's email address, and every prompt is
+# a copy handed to a third-party CLI, written into its transcript and its own logs. So the
+# addresses come out of everything we inject: SOUL.md carries the owner's, the coder rules and
+# handover notes quote correspondents, and none of it changes a line of code. The NAME stays -
+# "Sign as Uri J Nussbaum" still means something without the mailbox next to it.
+_EMAIL = re.compile(r'\b[\w.+-]+@[\w-]+\.[\w.-]+')
+
+
+def no_emails(text: str) -> str:
+    return _EMAIL.sub('[email removed]', text or '')
+
+
 def seed_text(store, tid: int, instruction: str = None, repo: str = None, cwd: str = None) -> str:
     """What gets typed into a fresh session, and the ONLY context it should need: the ask, the
     mail behind it, which checkout to work in, and the coder rules. One line - a newline
@@ -676,7 +688,7 @@ def seed_text(store, tid: int, instruction: str = None, repo: str = None, cwd: s
     note = next((c['Body'] for c in reversed(store.list_comments(tid))
                  if str(c.get('Body') or '').startswith(PAUSE_MARKER)), None)
     if note: parts.append('HANDOVER: an earlier session on this task was paused and left this - '
-                          f'continue from it, do not start over: {_cut(note, 3000, "handover note")}')
+                          f'continue from it, do not start over: {no_emails(_cut(note, 3000, "handover note"))}')
     # SOUL.md rides in WITH the coder rules, because the coder rules refer to it: CODER.md says
     # "work only in the repository the task names (see the repository map in SOUL.md)" and
     # claims it is "stacked on top of SOUL.md for every coder run" - and for a live session it
@@ -685,9 +697,9 @@ def seed_text(store, tid: int, instruction: str = None, repo: str = None, cwd: s
     # structurally incapable of seeing. It was right. These docs live in Taskuary's database;
     # if the prompt does not carry them, nothing does.
     soul = ' '.join(str(store.doc('soul') or '').split())[:SOUL_CHARS]
-    if soul: parts.append(f'OPERATOR RULES (SOUL.md - authoritative): {soul}')
+    if soul: parts.append(f'OPERATOR RULES (SOUL.md - authoritative): {no_emails(soul)}')
     rules = rules_text(store)
-    if rules: parts.append(f'RULES: {rules}')
+    if rules: parts.append(f'RULES: {no_emails(rules)}')
     # The job, spelled out. An agent handed a bare task description went looking for the ticket
     # it came from - Taskuary's own API, its database, the mailbox - and spent its first minute
     # re-fetching what is already in this paragraph.

{taskuary-0.2.0 → taskuary-0.2.1/taskuary.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: taskuary
-Version: 0.2.0
+Version: 0.2.1
 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
@@ -51,6 +51,7 @@ Dynamic: license-file
 [![CI](https://github.com/ldbumble/taskuary/actions/workflows/ci.yml/badge.svg)](https://github.com/ldbumble/taskuary/actions/workflows/ci.yml)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 [![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-3776ab.svg)](https://github.com/ldbumble/taskuary)
+[![PyPI](https://img.shields.io/pypi/v/taskuary.svg)](https://pypi.org/project/taskuary/)
 [![PRs welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](CONTRIBUTING.md)
 [![GitHub stars](https://img.shields.io/github/stars/ldbumble/taskuary?style=social)](https://github.com/ldbumble/taskuary/stargazers)
 
@@ -60,7 +61,7 @@ Dynamic: license-file
 scheduled reports land on one timeline; AI triage says what is real work; the coding CLI
 you already use does it; you approve the result. Runs entirely on your machine.
 
-![Taskuary in use: the timeline of email, chats and scheduled reports; a mail opened to show why triage made it a task and the AI reply drafted for approval; a scheduled report landing with its bar chart and spreadsheet; the Reports pipeline list; and the agent board with live sessions and the note one agent left the next](docs/hero.gif)
+![Taskuary in use: the timeline of email, chats and scheduled reports; a mail opened to show why triage made it a task and the AI reply drafted for approval; a scheduled report landing with its bar chart and spreadsheet; the Reports pipeline list; and the agent board with live sessions and the note one agent left the next](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/hero.gif)
 
 <sub>Real app, real data — a mail triaged and its reply drafted for your approval, then a scheduled SQL report landing on the same rail with its chart and spreadsheet. Nothing sends without you.</sub>
 
@@ -92,7 +93,7 @@ sender (yours to review under Settings → Agent memory).
 
 The general lessons take a stricter road, so one odd Tuesday never becomes a rule:
 
-![Your verdicts become a hypothesis with score s:2; agreeing verdicts add a point and contradictions remove one; at s:4 with proof from two or more people it is promoted into LEARNED.md, which then rides into every triage, draft and agent run](docs/learning-loop.svg)
+![Your verdicts become a hypothesis with score s:2; agreeing verdicts add a point and contradictions remove one; at s:4 with proof from two or more people it is promoted into LEARNED.md, which then rides into every triage, draft and agent run](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/learning-loop.svg)
 
 **How the memory works, concretely.** Each lesson is one line in `LEARNED.md` (Docs tab) —
 a guess with a score. Say you strip the greeting off three drafts this week; the file soon
@@ -129,7 +130,7 @@ markers always survive. What each one feeds from then on:
 ## Get started
 
 ```bash
-pip install git+https://github.com/ldbumble/taskuary
+pip install taskuary
 taskuary        # opens http://127.0.0.1:7787
 ```
 
@@ -161,7 +162,7 @@ No cloud key at all? Set **Settings → Triage & routing → Triage brain** to y
 and skip step 1 — one brain does everything, slower and pricier per message. See
 [One brain or two](#one-brain-or-two).
 
-Prefer a desktop app? `pip install "taskuary[desktop] @ git+https://github.com/ldbumble/taskuary"`
+Prefer a desktop app? `pip install "taskuary[desktop]"`
 then `taskuary-desktop` — the same UI in a native window. A prebuilt single-file
 `Taskuary.exe` is attached to every CI run.
 
@@ -215,7 +216,7 @@ with no AI connected messages file visibly instead of heuristics spraying tasks.
 
 ## Many agents, one repo — no stepping on each other
 
-![Two agents share one checkout: each working card shows the files ITS agent has modified (claude in the theme files, codex in the report code and its tests), and a third task waits in Queued with the reason written on the card — waiting on TQ-0009, both would modify ReportsView.jsx, starts by itself when it can](docs/screenshot-board.png)
+![Two agents share one checkout: each working card shows the files ITS agent has modified (claude in the theme files, codex in the report code and its tests), and a third task waits in Queued with the reason written on the card — waiting on TQ-0009, both would modify ReportsView.jsx, starts by itself when it can](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/screenshot-board.png)
 
 Auto-dispatch can put several CLIs to work at once — and the board keeps them out of each
 other's way with three light moves. No locks, no worktrees, no manager agent:
@@ -265,7 +266,7 @@ Plain markdown, all on the Docs tab, all yours to edit. Three you write, two wri
 themselves, and two can **bootstrap themselves from your mail history** (`TRIAGE.md` and
 `STYLE.md` — the Generate from history button). Each feeds exactly the calls it belongs in.
 
-![TRIAGE.md, STYLE.md, SOUL.md and LEARNED.md feed triage and replies on the cheap model; SOUL.md, CODER.md and LEARNED.md feed coding agents on your CLI; DIGEST.md is your own morning read — and TRIAGE.md and STYLE.md can be generated from three months of your own mail](docs/six-docs.svg)
+![TRIAGE.md, STYLE.md, SOUL.md and LEARNED.md feed triage and replies on the cheap model; SOUL.md, CODER.md and LEARNED.md feed coding agents on your CLI; DIGEST.md is your own morning read — and TRIAGE.md and STYLE.md can be generated from three months of your own mail](https://raw.githubusercontent.com/ldbumble/taskuary/master/docs/six-docs.svg)
 
 | document | what it is | who reads it |
 |---|---|---|