@matheuskrumenauer/tanya 0.9.0-beta.0 → 0.11.0-beta.0

package/README.md

@@ -174,6 +174,7 @@ tanya runs                    # show recent run logs with cost/status
 tanya video presets           # list available video presets
 tanya video one-terminal-simctl # generate the exact transparent terminal asset
 tanya providers test          # provider smoke test
+tanya mcp serve               # expose Tanya verifier/run/skills over MCP stdio
 tanya doctor                  # local environment check
 ```
 
@@ -188,6 +189,7 @@ model:
 /verify           # print the deterministic verifier report for the cwd
 /cost             # show persisted token usage and estimated cost
 /memory --limit 5 # list recent golden-task memory
+/mcp              # list connected MCP servers and tools
 ```
 
 Project-local commands live in `.tania/commands/*.{js,ts,sh}` and appear in
@@ -227,6 +229,44 @@ children.
 See [docs/sub-agents.md](./docs/sub-agents.md) for permission inheritance,
 budget-ledger semantics, cancellation, verifier composition, and memory rollup.
 
+## MCP integration
+
+Tanya can consume external Model Context Protocol servers and expose Tanya's own
+verifier and memory primitives to MCP-speaking clients.
+
+Client configuration is allowlist-only. User-global servers are read from
+`~/.tanya/mcp.json` with a fallback read of `~/.tania/mcp.json`; project servers
+live in `.tania/mcp.json` and override same-named user servers. Connected tools
+are registered as normal Tanya tools named `mcp:<server>:<tool>`, so permission
+rules, audit logging, truncation, and verifier visibility apply exactly as they
+do for native tools.
+
+```json
+{
+  "version": 1,
+  "servers": [
+    {
+      "name": "filesystem",
+      "transport": "stdio",
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-filesystem", "."]
+    }
+  ]
+}
+```
+
+Use `/mcp` in the REPL to inspect connected servers. Use `tanya mcp serve` to
+start Tanya's MCP server over stdio; it exposes `tanya.verify`,
+`tanya.golden_task_search`, `tanya.run`, and `tanya.skills_list`.
+
+MCP servers are untrusted code. Tanya refuses undeclared servers, gates every
+MCP tool call through the permission engine, captures stdio server stderr under
+`.tania/mcp/logs/`, restarts crashed servers up to three times, and rejects
+schema-invalid tool responses before they reach model history.
+
+See [docs/mcp.md](./docs/mcp.md) for the full schema, transports, server tools,
+and security model.
+
 ## Multi-model routing
 
 Tanya can route each agent step to a different provider/model. Planning and
@@ -256,6 +296,26 @@ up to `TANYA_ESCALATION_CAP` per session.
 See [docs/routing.md](./docs/routing.md) for schema, examples, context-window
 guards, per-tool model overrides, and sub-agent model pins.
 
+## Reasoning models
+
+Reasoning routes such as `deepseek-reasoner`, `qwen3-thinking-*`, and
+`grok-3-reasoning` are handled as a separate stream. Tanya archives reasoning to
+`.tania/runs/<runId>/reasoning.jsonl`, emits `reasoning_chunk` events, and keeps
+assistant history reasoning-free so replay and verifier inputs stay stable.
+
+Reasoning tokens appear separately in `/cost` and `/budget`. Route rules can set
+`reasoningCap.maxTokens`; built-in defaults are 2k for planning-like turns and
+8k for synthesis/verification/reasoning turns. If the cap is exceeded, Tanya
+emits `reasoning_truncated` and asks the model to finish.
+
+Use `/memory --reasoning <runId>` to inspect archived reasoning. Use
+`TANYA_HIDE_REASONING=1` to hide reasoning from the human UI while preserving
+JSONL/Cosmo events. Verifier reasoning annotations are off by default; enable
+them with `--verbose-verifier` or `TANYA_VERIFIER_INCLUDE_REASONING=1`.
+
+See [docs/reasoning.md](./docs/reasoning.md) for provider notes, billing math,
+budget defaults, and UX modes.
+
 `--verify` adds required verification commands to the run context. Tanya must run and report each exact command before finishing the coding task.
 
 `tanya benchmark run --all` currently exercises 27 executable low-to-medium regression fixtures: targeted edits, new files, dependency/lockfile updates, framework-style migrations, failing-test repair, frontend smoke checks, artifact/context reuse, streaming long-tool execution, compaction-boundary recovery, run-history logging, dirty worktrees, report repair, and the CosmoHQ mobile/backend smoke profiles.