mika kuns
ca6eb62b5c
batch_get_tasks with includeDescription=true had no size guard: 8 tasks' full Description/Result serialized to a single 51k-char line, blowing past the tool-result token budget and forcing a file/PowerShell workaround to read it back. Roadblock text was also only reachable via a second get_task call per task, since roadblockCount (in the lean ref) has no text sibling. - descriptionMaxChars (default 1500, was unlimited) truncates Description and Result independently, flagged via *Truncated/*FullLength so a caller never silently works off a cut string. - fields narrows taskFull to just the named properties, including the new roadblockText (the tail of Result after TaskRunner's roadblock marker) — reachable without pulling in the rest of Result/Description. - taskFull is now BatchTaskDetailDto, a batch-only shape decoupled from TaskDto so get_task's own contract is untouched. - The whole response is capped (MaxResponseChars); over that, the call throws naming which parameter (descriptionMaxChars/fields/taskIds) to adjust instead of shipping an oversized payload. 10 tasks with 5000-char descriptions (default settings) serialize to ~13.8k chars, comfortably under the 25k-char cap.
Explore-notes
Distilled, reusable maps of complex subsystems, produced by deep code exploration. The goal: stop re-exploring the same subsystem from scratch in every new session.
These sit between the CLAUDE.md files and the code:
- CLAUDE.md — high-level orientation, hand-maintained, always-loaded.
- explore-notes — deeper subsystem detail (flows, who-calls-whom, invariants) that is too fine-grained for a CLAUDE.md but stable enough to be worth caching. Read on demand.
- code — the only source of truth.
Index
| Note | Covers |
|---|---|
| worker-task-pipeline | TaskRunner end-to-end: config resolution, worktree, CLI invocation, streaming, commit |
| usage-monitoring | OAuth usage endpoint, gate, throttle, per-run token accounting, usage pill/modal |
| external-mcp | The claudedo MCP tool surface + its two test-enforced conventions |
| review-merge | Approve=merge-unit, verify gate, MergeCommit/revert, diff stack, conflict resolver |
| conpty-sessions | Interactive/planning/list-handler launch specs + the arg-flattening gotcha |
| installer-preflight | CLI version/login/auto-mode research, the ExecutableResolver/shim root cause, and the Installer's Checks/+SystemCheckPage implementation status |
Rules
- Only stable structure. Flows, responsibilities, entry points, invariants, relative file paths. No line numbers, no exhaustive symbol dumps — those rot fastest.
- Verify before trusting. A note is a starting map, not authority. Always confirm against current code before acting on it. Each note records the commit it was verified against so you can diff for drift.
- Not a substitute for CLAUDE.md. If a fact belongs in orientation, put it there.
Header every note must carry
> **Explore-note — verify before trusting.** Distilled map of a subsystem, not authoritative.
> Last verified against commit `<short-hash>` (<date>).
> Drift check: `git log --oneline <short-hash>..HEAD -- <paths this note covers>`
> Stable structure only (no line numbers). See docs/explore-notes/README.md.
Workflow
- Before deep-exploring a subsystem, check for a matching note here and read it first; explore only to fill gaps or confirm.
- After a deep explore, distill the durable findings into a new/updated note and bump its "verified against" commit line.
- If the drift check shows the covered paths changed a lot since the verified commit, treat the note as suspect and re-verify the parts you rely on.