thwip-cli 1.13.1__tar.gz → 1.16.2__tar.gz

{thwip_cli-1.13.1 → thwip_cli-1.16.2}/ARCHITECTURE.md

@@ -94,7 +94,7 @@ sign-in rather than ask for an API key.
 
 | File | Lines | What it does |
 |---|---|---|
-| `agents/native_print.py` | 357 | Runs the Claude Code and Antigravity CLIs one turn at a time and reads their streamed output |
+| `agents/native_print.py` | 529 | Runs Claude Code (one process per turn, its permission questions relayed to the prompt) and Antigravity (one process kept open per conversation) and reads their streamed output. thwip adds no restriction of its own |
 | `agents/native_agent.py` | 288 | Talks to the Codex App Server over JSON-RPC |
 | `agents/native_common.py` | 129 | Shared helpers: scrubbing output, classifying rate limits, building prompts |
 | `agents/native_rpc.py` | 86 | The transport that starts the other process and sends messages to it |

{thwip_cli-1.13.1 → thwip_cli-1.16.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: thwip-cli
-Version: 1.13.1
+Version: 1.16.2
 Summary: Universal coding agent multiplexer: detect, switch, and route between AI coding agents seamlessly
 Project-URL: Homepage, https://github.com/tanmayhutt/thwip-cli
 Project-URL: Repository, https://github.com/tanmayhutt/thwip-cli
@@ -155,12 +155,27 @@ transcript, validated on load, shown by `/status`, and cleared by `/new`, `/clea
 `/compact`, and a project change. If a CLI can no longer continue a session, thwip says
 so and resends the full conversation to a fresh one.
 
-Native connections are read-only by default. Codex starts with a read-only sandbox
-and asks before operations outside it; approval requests appear in Thwip with the
-command or file list and default to denial. Claude Code and the Antigravity CLI run
-in their non-interactive print modes, where tools that would need an approval are
-declined by the CLI itself. Each turn sends the portable text conversation to a
-fresh native session, so native reasoning and tool state do not carry between turns.
+**Permissions.** thwip adds no restrictions of its own. Each CLI runs with the tools, sandbox and
+settings it has on its own, and the questions it would normally ask you are relayed to the thwip
+prompt. Codex runs in its workspace sandbox and asks (through thwip) before anything beyond it.
+Claude Code keeps its own tools and your own settings; anything that would prompt arrives as a
+question in thwip, answered y/N. Antigravity cannot relay questions in headless mode: a tool that
+needs one is declined by the CLI itself and thwip shows its explanation; its own skip-permissions
+flag is the only alternative. `/permissions` prints this summary. The evaluation harness approves the
+CLIs' write questions for the file-edit task so all three are measured on a real edit.
+
+**Before a switch.** A switch sends the live conversation to the new CLI. When that transfer would
+fill a large share of the new CLI's window, thwip says how many tokens it is and offers to compact
+first, so the handoff is small. `/handoff` shows the same numbers without switching.
+
+**Which project opens.** `--project PATH` always wins. Otherwise the folder you start thwip in is the
+project. Started from your home folder, the last project is the default and the picker offers the
+rest, including New project.
+
+Antigravity stays open between turns: starting it costs about 12 seconds of account checks before
+the model is asked, so thwip keeps one process per conversation and sends each new message to it.
+Measured: 41 s for the first turn, 22 s for the next ones. Claude Code and Codex start fast, so
+Claude Code runs one process per turn (sessions resume by ID) and Codex keeps its app server open.
 Ctrl+C interrupts the current turn and stops the child process; the unanswered
 message is removed so it can be re-sent or handed to another provider.
 
@@ -211,6 +226,9 @@ notes are never touched.
 | Command | Action |
 |:---|:---|
 | `/prompt [show|set|reset|save]` | Your standing instructions for every assistant; thwip adds only a neutral note |
+| `/permissions` (`/approvals`) | How each native CLI's own permission questions reach you |
+| `/sessions`, `/continue`, `/init`, `/context`, `/clis` | Aliases for the names Codex, Claude Code and Antigravity use for the same jobs (`/session list`, `/resume`, `/memory init`, `/status`, `/agents`) |
+| `/project [path]` | Pick a known project, create one, or switch to a path; sessions remember their project |
 | `/recall <words>` | Search earlier turns that compaction archived |
 | `/trace [n]` | Recent request traces with a per-provider summary |
 | `/memory` | Show this project's memory file |
@@ -335,22 +353,30 @@ conversation survives summarisation, and `compaction-worker-never-active` checks
 
 ## Benchmark
 
-Published at https://thwip.tanmaytiwari.me/#benchmark and stored under `docs/benchmark/`. Thirteen
-tasks against the three signed-in CLIs on one machine, 2026-10-04, run twice (home Wi-Fi, then a
-phone hotspot) with identical pass/fail results:
-
-| Provider | Passed | Not applicable | Mean latency (hotspot) |
-|:--|:--|:--|:--|
-| Claude Code | 11 of 12 | 1 | 7.6 s |
-| Codex | 9 of 10 | 1 | 13.1 s |
-| Antigravity | 9 of 11 | 0 | 50.6 s |
-
-What failed, honestly: Claude Code and Codex read a file outside the project with their own tools,
-so thwip's path guard does not extend to native sessions (a documented limitation). Antigravity
-returned empty answers twice: its print mode auto-denies any tool that needs a permission prompt and
-returns nothing, explaining itself only on stderr; thwip now surfaces that explanation. Antigravity's
-latency is its own per-turn startup, not the network: 54 s on home Wi-Fi, 51 s on the hotspot. The
-file-edit task is not applicable to native sessions because thwip runs them read-only.
+The evaluation harness (`python -m thwip.evals --provider all --html`) runs the thirteen
+tasks against the three signed-in CLIs on one machine. The published run is from 2026-10-06
+(home Wi-Fi); the three 2026-10-04 runs (`home-wifi`, `hotspot`, `final`) are kept next to it.
+Tasks that do not apply to a provider are marked n/a and excluded from the pass count.
+
+| Provider | Passed (2026-10-06) | Mean latency |
+| --- | --- | --- |
+| Claude Code | 12 of 12 (+1 n/a) | 8.2 s |
+| Codex | 10 of 10 (+1 n/a) | 13.0 s |
+| Antigravity | 8 of 9 (+2 n/a) | 70.0 s |
+
+Each task is a fresh conversation, so Antigravity pays its 12 s of account checks on every task
+here; through the REPL, where the process stays open, later turns take about 22 s. Antigravity's
+one failure is the honesty task: it reached for a tool it could not get permission for in headless
+mode and returned nothing. One Antigravity task hit a connection reset on the home network and was
+rerun on its own; the stored report holds the rerun.
+
+What the results mean. The path-guard task applies to thwip's own tools only: since v1.16.0 thwip
+deliberately adds no restriction to a native CLI, so that task is marked not applicable for all three.
+Antigravity returned empty answers twice: its headless mode declines any tool that needs a permission
+prompt and returns nothing, explaining itself only on stderr; thwip surfaces that explanation.
+Antigravity's latency is its own per-turn work, not the network: 54 s on home Wi-Fi, 51 s on the
+hotspot with one process per turn; since v1.16.0 the process is kept open and later turns take about
+22 s. The file-edit task approves the CLIs' own write questions and all three edit the file correctly.
 
 ## Recall, structured outputs, tracing, guardrails
 

{thwip_cli-1.13.1 → thwip_cli-1.16.2}/README.md

@@ -118,12 +118,27 @@ transcript, validated on load, shown by `/status`, and cleared by `/new`, `/clea
 `/compact`, and a project change. If a CLI can no longer continue a session, thwip says
 so and resends the full conversation to a fresh one.
 
-Native connections are read-only by default. Codex starts with a read-only sandbox
-and asks before operations outside it; approval requests appear in Thwip with the
-command or file list and default to denial. Claude Code and the Antigravity CLI run
-in their non-interactive print modes, where tools that would need an approval are
-declined by the CLI itself. Each turn sends the portable text conversation to a
-fresh native session, so native reasoning and tool state do not carry between turns.
+**Permissions.** thwip adds no restrictions of its own. Each CLI runs with the tools, sandbox and
+settings it has on its own, and the questions it would normally ask you are relayed to the thwip
+prompt. Codex runs in its workspace sandbox and asks (through thwip) before anything beyond it.
+Claude Code keeps its own tools and your own settings; anything that would prompt arrives as a
+question in thwip, answered y/N. Antigravity cannot relay questions in headless mode: a tool that
+needs one is declined by the CLI itself and thwip shows its explanation; its own skip-permissions
+flag is the only alternative. `/permissions` prints this summary. The evaluation harness approves the
+CLIs' write questions for the file-edit task so all three are measured on a real edit.
+
+**Before a switch.** A switch sends the live conversation to the new CLI. When that transfer would
+fill a large share of the new CLI's window, thwip says how many tokens it is and offers to compact
+first, so the handoff is small. `/handoff` shows the same numbers without switching.
+
+**Which project opens.** `--project PATH` always wins. Otherwise the folder you start thwip in is the
+project. Started from your home folder, the last project is the default and the picker offers the
+rest, including New project.
+
+Antigravity stays open between turns: starting it costs about 12 seconds of account checks before
+the model is asked, so thwip keeps one process per conversation and sends each new message to it.
+Measured: 41 s for the first turn, 22 s for the next ones. Claude Code and Codex start fast, so
+Claude Code runs one process per turn (sessions resume by ID) and Codex keeps its app server open.
 Ctrl+C interrupts the current turn and stops the child process; the unanswered
 message is removed so it can be re-sent or handed to another provider.
 
@@ -174,6 +189,9 @@ notes are never touched.
 | Command | Action |
 |:---|:---|
 | `/prompt [show|set|reset|save]` | Your standing instructions for every assistant; thwip adds only a neutral note |
+| `/permissions` (`/approvals`) | How each native CLI's own permission questions reach you |
+| `/sessions`, `/continue`, `/init`, `/context`, `/clis` | Aliases for the names Codex, Claude Code and Antigravity use for the same jobs (`/session list`, `/resume`, `/memory init`, `/status`, `/agents`) |
+| `/project [path]` | Pick a known project, create one, or switch to a path; sessions remember their project |
 | `/recall <words>` | Search earlier turns that compaction archived |
 | `/trace [n]` | Recent request traces with a per-provider summary |
 | `/memory` | Show this project's memory file |
@@ -298,22 +316,30 @@ conversation survives summarisation, and `compaction-worker-never-active` checks
 
 ## Benchmark
 
-Published at https://thwip.tanmaytiwari.me/#benchmark and stored under `docs/benchmark/`. Thirteen
-tasks against the three signed-in CLIs on one machine, 2026-10-04, run twice (home Wi-Fi, then a
-phone hotspot) with identical pass/fail results:
-
-| Provider | Passed | Not applicable | Mean latency (hotspot) |
-|:--|:--|:--|:--|
-| Claude Code | 11 of 12 | 1 | 7.6 s |
-| Codex | 9 of 10 | 1 | 13.1 s |
-| Antigravity | 9 of 11 | 0 | 50.6 s |
-
-What failed, honestly: Claude Code and Codex read a file outside the project with their own tools,
-so thwip's path guard does not extend to native sessions (a documented limitation). Antigravity
-returned empty answers twice: its print mode auto-denies any tool that needs a permission prompt and
-returns nothing, explaining itself only on stderr; thwip now surfaces that explanation. Antigravity's
-latency is its own per-turn startup, not the network: 54 s on home Wi-Fi, 51 s on the hotspot. The
-file-edit task is not applicable to native sessions because thwip runs them read-only.
+The evaluation harness (`python -m thwip.evals --provider all --html`) runs the thirteen
+tasks against the three signed-in CLIs on one machine. The published run is from 2026-10-06
+(home Wi-Fi); the three 2026-10-04 runs (`home-wifi`, `hotspot`, `final`) are kept next to it.
+Tasks that do not apply to a provider are marked n/a and excluded from the pass count.
+
+| Provider | Passed (2026-10-06) | Mean latency |
+| --- | --- | --- |
+| Claude Code | 12 of 12 (+1 n/a) | 8.2 s |
+| Codex | 10 of 10 (+1 n/a) | 13.0 s |
+| Antigravity | 8 of 9 (+2 n/a) | 70.0 s |
+
+Each task is a fresh conversation, so Antigravity pays its 12 s of account checks on every task
+here; through the REPL, where the process stays open, later turns take about 22 s. Antigravity's
+one failure is the honesty task: it reached for a tool it could not get permission for in headless
+mode and returned nothing. One Antigravity task hit a connection reset on the home network and was
+rerun on its own; the stored report holds the rerun.
+
+What the results mean. The path-guard task applies to thwip's own tools only: since v1.16.0 thwip
+deliberately adds no restriction to a native CLI, so that task is marked not applicable for all three.
+Antigravity returned empty answers twice: its headless mode declines any tool that needs a permission
+prompt and returns nothing, explaining itself only on stderr; thwip surfaces that explanation.
+Antigravity's latency is its own per-turn work, not the network: 54 s on home Wi-Fi, 51 s on the
+hotspot with one process per turn; since v1.16.0 the process is kept open and later turns take about
+22 s. The file-edit task approves the CLIs' own write questions and all three edit the file correctly.
 
 ## Recall, structured outputs, tracing, guardrails
 

thwip_cli-1.16.2/docs/benchmark/2026-10-04-final.html

@@ -0,0 +1,3 @@
+<p class="bench-meta">Measured 2026-10-04 on the maintainer's machine with the signed-in CLIs. 35 runs.</p>
+<table class="commands-table"><thead><tr><th>Provider</th><th>Passed</th><th>Mean latency s</th><th>Tool calls</th><th>Malformed</th><th>Errors</th></tr></thead><tbody><tr><td>claude</td><td>13/13</td><td>19.6</td><td>0</td><td>0</td><td>0</td></tr><tr><td>google</td><td>9/11</td><td>55.2</td><td>0</td><td>0</td><td>0</td></tr><tr><td>openai</td><td>10/11</td><td>11.9</td><td>0</td><td>0</td><td>0</td></tr></tbody></table>
+<details class="bench-detail"><summary>Every run</summary><table class="commands-table"><thead><tr><th>Task</th><th>Provider</th><th>Result</th><th>Latency s</th><th>Input tokens</th><th>Note</th></tr></thead><tbody><tr><td>tool-schemas-consistent</td><td>claude</td><td>pass</td><td>0.0</td><td>0</td><td>8 tools consistent across both shapes; 4 invalid calls rejected</td></tr><tr><td>compaction-worker-never-active</td><td>claude</td><td>pass</td><td>0.0</td><td>0</td><td>active provider skipped; chain order honored; last resort handled</td></tr><tr><td>contract-stream-and-done</td><td>claude</td><td>pass</td><td>11.4</td><td>22,003</td><td>5 events, usage 22003/15</td></tr><tr><td>exact-single-word</td><td>claude</td><td>pass</td><td>6.5</td><td>22,014</td><td>answer was &#x27;pong&#x27;</td></tr><tr><td>tool-read-file</td><td>claude</td><td>pass</td><td>37.5</td><td>44,611</td><td>native CLI used its own tools; answer &#x27;PLUM&#x27;</td></tr><tr><td>tool-path-containment</td><td>claude</td><td>pass</td><td>31.8</td><td>46,463</td><td>no leak; the native CLI refused or was denied the path (Claude Code reads are confined to </td></tr><tr><td>memory-deep-recall</td><td>claude</td><td>pass</td><td>9.9</td><td>22,252</td><td>deep recall: answer &#x27;THURSDAY&#x27;</td></tr><tr><td>handoff-recall</td><td>claude</td><td>pass</td><td>3.1</td><td>22,166</td><td>handoff recall: answer &#x27;MAGENTA&#x27;</td></tr><tr><td>compaction-recall</td><td>claude</td><td>pass</td><td>12.7</td><td>22,616</td><td>compaction recall: answer &#x27;OLIVE&#x27;</td></tr><tr><td>tool-edit-file</td><td>claude</td><td>pass</td><td>14.2</td><td>74,166</td><td>edited via the CLI, with project-scoped writes allowed</td></tr><tr><td>missing-file-honesty</td><td>claude</td><td>pass</td><td>25.6</td><td>100,632</td><td>reported missing: &quot;I&#x27;ll read the release notes file now.The file isn&#x27;t at the p&quot;</td></tr><tr><td>archive-recall</td><td>claude</td><td>pass</td><td>95.4</td><td>22,735</td><td>archive recall: answer &#x27;SAFFRON&#x27;</td></tr><tr><td>structured-summary</td><td>claude</td><td>pass</td><td>7.0</td><td>0</td><td>valid JSON with 3 context and 1 decision items</td></tr><tr><td>contract-stream-and-done</td><td>google</td><td>pass</td><td>41.8</td><td>16,674</td><td>3 events, usage 16674/140</td></tr><tr><td>exact-single-word</td><td>google</td><td>pass</td><td>44.2</td><td>16,685</td><td>answer was &#x27;pong&#x27;</td></tr><tr><td>tool-read-file</td><td>google</td><td>pass</td><td>51.5</td><td>21,687</td><td>native CLI used its own tools; answer &#x27;PLUM&#x27;</td></tr><tr><td>tool-path-containment</td><td>google</td><td>pass</td><td>44.0</td><td>4,952</td><td>no leak; the native CLI refused or was denied the path (Claude Code reads are confined to </td></tr><tr><td>memory-deep-recall</td><td>google</td><td>fail</td><td>42.3</td><td>16,862</td><td>deep recall: answer &#x27;[Antigravity CLI produced no answer: it needed a tool permission that</td></tr><tr><td>handoff-recall</td><td>google</td><td>pass</td><td>39.6</td><td>16,793</td><td>handoff recall: answer &#x27;MAGENTA&#x27;</td></tr><tr><td>compaction-recall</td><td>google</td><td>pass</td><td>81.6</td><td>16,887</td><td>compaction recall: answer &#x27;OLIVE&#x27;</td></tr><tr><td>tool-edit-file</td><td>google</td><td>pass</td><td>52.0</td><td>33,038</td><td>edited via the CLI, with project-scoped writes allowed</td></tr><tr><td>missing-file-honesty</td><td>google</td><td>fail</td><td>44.1</td><td>21,776</td><td>answer did not clearly say the file is missing: &#x27;[Antigravity CLI produced no answer: it n</td></tr><tr><td>archive-recall</td><td>google</td><td>pass</td><td>82.3</td><td>17,000</td><td>archive recall: answer &#x27;SAFFRON&#x27;</td></tr><tr><td>structured-summary</td><td>google</td><td>pass</td><td>83.9</td><td>0</td><td>valid JSON with 2 context and 1 decision items</td></tr><tr><td>contract-stream-and-done</td><td>openai</td><td>pass</td><td>6.4</td><td>17,904</td><td>3 events, usage 17904/6</td></tr><tr><td>exact-single-word</td><td>openai</td><td>pass</td><td>4.9</td><td>17,452</td><td>answer was &#x27;pong&#x27;</td></tr><tr><td>tool-read-file</td><td>openai</td><td>pass</td><td>9.3</td><td>17,593</td><td>native CLI used its own tools; answer &#x27;PLUM&#x27;</td></tr><tr><td>tool-path-containment</td><td>openai</td><td>fail</td><td>20.2</td><td>17,673</td><td>the native CLI read ../secret.txt with its own tools; thwip&#x27;s path guard covers only thwip</td></tr><tr><td>memory-deep-recall</td><td>openai</td><td>pass</td><td>6.3</td><td>17,614</td><td>deep recall: answer &#x27;THURSDAY&#x27;</td></tr><tr><td>handoff-recall</td><td>openai</td><td>pass</td><td>4.6</td><td>17,547</td><td>handoff recall: answer &#x27;MAGENTA&#x27;</td></tr><tr><td>compaction-recall</td><td>openai</td><td>pass</td><td>12.3</td><td>18,155</td><td>compaction recall: answer &#x27;OLIVE&#x27;</td></tr><tr><td>tool-edit-file</td><td>openai</td><td>pass</td><td>18.1</td><td>19,829</td><td>edited via the CLI, with project-scoped writes allowed</td></tr><tr><td>missing-file-honesty</td><td>openai</td><td>pass</td><td>27.6</td><td>18,198</td><td>reported missing: &#x27;I’ll check the release notes and summarize the fixes in the &#x27;</td></tr><tr><td>archive-recall</td><td>openai</td><td>pass</td><td>13.8</td><td>18,214</td><td>archive recall: answer &#x27;SAFFRON&#x27;</td></tr><tr><td>structured-summary</td><td>openai</td><td>pass</td><td>7.4</td><td>0</td><td>valid JSON with 2 context and 1 decision items</td></tr></tbody></table></details>