Changelog

Unreleased · 146 changes · page 4 of 4

coding.sh v0.1.6

CLI 2

  • # Changed --agent, --tag, --session and the other repeatable id flags take a comma list: --agent claude-code,codex is the same as --agent claude-code --agent codex, on sessions, usage, search, export and the rest. CLI reference.
  • # Changed Default --json reads are digests an agent can afford. sessions --json rows, tree --json nodes and status --json latest drop stats.phases and each derail's eventId and index. show --json on a session over 200 events prints events: [] with eventCount and the phases unless --limit N or --all is given, each event drops sessionId (and agent/cwd when equal to the session's), and subagents lists the first 50 with subagentCount and subagentsTruncated. tree --json and MCP session_tree return 50 nodes a page with nextCursor and truncated (--limit/--cursor; MCP limit up to 200). New --fields a,b.c on sessions and show picks paths from the full document. Explore guide

Query 2

  • # Changed A date without a zone in --since, --until, since: and until: is local time: 2026-11-09 is local midnight (it was UTC midnight) and equals 2026-11-09T00:00:00. today and yesterday work, and until is exclusive. sessions, usage and stats print the resolved window on stderr and carry window in --json. The MCP tools read times the same way, and GET /api/metrics reads a date without a zone as midnight in the request's tz, the zone its buckets use, so the first and last day of a range are whole days. Query reference, API
  • # Changed sessions --where with event.duration or error alone reads an index instead of every event. On a 1.4M-event store on the test desktop, --where 'event.duration>60s' went from 840 ms to under 1 ms and --where 'error:*timeout*' from 2.7 s to 3 ms. The first run upgrades the index once (schema v11), with progress on stderr and the old index kept beside it; that store (2.7 GB) took 59 s and grew by 1%. Query reference

Harness 1

  • # Changed harness audit (CLI and MCP) reads session rows instead of every event: ingest keeps the memory and instruction files each session's events name in stats.memoryUse. On a store of 3,600 sessions and 1.4M events it takes 0.4 s and 132 MB, where it took 10 to 27 s and up to 969 MB. After an upgrade the audit reads events as before until an ingest has refolded the stored sessions. Memory and instruction files

Doctor 1

  • # Fixed An agent whose hook is not installed or is blocked is a ! warning row with every blocker and the file and line to change (Codex: config.toml:<line>); recent events alone no longer earn a check mark. The last line is N agents not capturing instead of ok, and doctor --json lists them under warnings. ok and the exit code still report spool and store health only. Troubleshooting

Gateways 4

  • # Fixed gateway enrich --gateway cliproxyapi no longer joins another client's usage record to your call. A record whose session id is not in the store is kept for a later run, a record joins by time and model only when it has no session id, and records that name a session join first, so each call gets its own tokens, cost and account. LLM gateways
  • # Fixed gateway enrich --gateway cliproxyapi no longer joins a failed or retried CLIProxyAPI request to a call that answered, which gave every later call its neighbour's usage record. A failed record joins only a call that failed, a record that answered joins only a call that did not fail, and a call whose token counts equal the record's wins over a nearer one. A failed record with no failed call is kept for a day, then dropped. LLM gateways
  • # Fixed After init --proxy chains through a gateway (CLIProxyAPI, OpenRouter, LiteLLM, …), new sessions keep their gateway:<name> tag: the proxy names the gateway on each call it logs, also in capture mode metadata. gateway status and doctor report the route, marked "through the coding.sh proxy". Capture with the proxy
  • # Fixed A background re-parse, refold or end-of-turn snapshot no longer drops the gateway:<name> tag and the billed cost that gateway enrich stored at the same moment. A session that got events while its row was being built is folded again before the row is written, and gateway enrich stores its events and the session rows in one transaction. LLM gateways

From CHANGELOG.md · RSS · All releases