@matheuskrumenauer/tanya 0.13.0-beta.0 → 0.15.0-beta.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -25
- package/dist/cli.js +591 -990
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -296,6 +296,24 @@ up to `TANYA_ESCALATION_CAP` per session.
|
|
|
296
296
|
See [docs/routing.md](./docs/routing.md) for schema, examples, context-window
|
|
297
297
|
guards, per-tool model overrides, and sub-agent model pins.
|
|
298
298
|
|
|
299
|
+
## Live status
|
|
300
|
+
|
|
301
|
+
Interactive `tanya chat` sessions show a compact status footer derived from the
|
|
302
|
+
same events already sent to the human sink:
|
|
303
|
+
|
|
304
|
+
```text
|
|
305
|
+
[deepseek:deepseek-chat | tool_call | $0.04 | 2 tools | 1 child]
|
|
306
|
+
[awaiting permission: run_shell]
|
|
307
|
+
[escalated deepseek:deepseek-chat->openai:gpt-4.1-mini: parse_failure]
|
|
308
|
+
```
|
|
309
|
+
|
|
310
|
+
The footer is TTY-only. Piped output, JSONL output, and Cosmo bridge streams stay
|
|
311
|
+
byte-stable and receive no ANSI cursor control bytes. Disable it with
|
|
312
|
+
`TANYA_LIVE_STATUS=0` or the legacy `TANIA_LIVE_STATUS=0` alias.
|
|
313
|
+
|
|
314
|
+
See [docs/live-status.md](./docs/live-status.md) for the surfaced fields,
|
|
315
|
+
streaming strategy, and TTY fallback behavior.
|
|
316
|
+
|
|
299
317
|
`--verify` adds required verification commands to the run context. Tanya must run and report each exact command before finishing the coding task.
|
|
300
318
|
|
|
301
319
|
`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.
|
|
@@ -361,30 +379,6 @@ Tanya trims model-visible tokens while keeping state reversible and auditable.
|
|
|
361
379
|
|
|
362
380
|
See [docs/token-economy.md](./docs/token-economy.md) for the full model, cache locations, and tool-definition knobs.
|
|
363
381
|
|
|
364
|
-
## Structural repo-map
|
|
365
|
-
|
|
366
|
-
Lite prompts can include a generated structural map from
|
|
367
|
-
`.tania/index/repo-map.json`. The map lists workspace-relative files, language,
|
|
368
|
-
parser provenance, top-level symbols, imports, and exports so cheap providers
|
|
369
|
-
can target likely files before spending turns on blind reads.
|
|
370
|
-
|
|
371
|
-
Tanya indexes TypeScript/JavaScript, Python, Go, Swift, and Kotlin with a
|
|
372
|
-
lightweight ripgrep-style parser and falls back to path-only entries when file
|
|
373
|
-
content cannot be read. Generated, binary, ignored, and oversized files are
|
|
374
|
-
skipped. The repo-map is advisory context only: agents must still read files
|
|
375
|
-
before editing, and the verifier remains the final authority.
|
|
376
|
-
|
|
377
|
-
Use `TANYA_LITE_PROMPT=1` to inject a ranked repo-map excerpt. Tune the default
|
|
378
|
-
1000-token section budget with `TANYA_REPO_MAP_PROMPT_BUDGET`; the legacy
|
|
379
|
-
`TANIA_*` alias is also accepted. If the prompt budget is tight, the repo-map
|
|
380
|
-
drops before skill packs because it is generated and recoverable.
|
|
381
|
-
|
|
382
|
-
Use `inspect_repo_map` when the model needs more structural detail by file,
|
|
383
|
-
symbol, or language without burning prompt tokens on the whole map.
|
|
384
|
-
|
|
385
|
-
See [docs/repo-map.md](./docs/repo-map.md) for schema, parser status, ranking,
|
|
386
|
-
budget interaction, and cache invalidation.
|
|
387
|
-
|
|
388
382
|
Context files are generic JSON envelopes for caller-supplied task metadata, artifacts, instructions, and verification commands.
|
|
389
383
|
|
|
390
384
|
## Current Tools
|
|
@@ -392,7 +386,6 @@ Context files are generic JSON envelopes for caller-supplied task metadata, arti
|
|
|
392
386
|
- `list_files`
|
|
393
387
|
- `read_file`
|
|
394
388
|
- `search`
|
|
395
|
-
- `inspect_repo_map`
|
|
396
389
|
- `inspect_project_context`
|
|
397
390
|
- `find_reusable_artifacts`
|
|
398
391
|
- `build_task_brief`
|