Release theme
v0.8.46 should make tools feel like a studio, not a bag of subprocesses. Documents, images, code execution, search, and conversion should feel native, inspectable, and safe.
This is the tool-studio release.
Product thesis
The agent should have more leverage, but each capability must be discoverable, dependency-aware, permissioned, explainable, and compatible with the same state/evidence model as the TUI.
In scope
- Document and rich-input workflows: PDF extraction, optional OCR, image analysis, document conversion, and region-aware web search.
- Dependency probes and doctor/status messages that explain missing capabilities without noisy false alarms.
- Tool output previews and detail handles so large results do not flood the transcript.
- Tool registry work only where it serves real tool ergonomics; broad plugin architecture belongs in v0.9.0 unless a narrow slice is proven.
- Prompt/tool guidance so the model knows when to use each tool and when to ask.
- Approval previews that show what will happen before the user signs off.
Candidate issue/PR clusters
Review lenses
- Systems/tooling builder with taste: does each tool earn its place as a composable primitive, or is it just a wrapper?
- Security/sandbox reviewer: are approvals, file access, network access, dependencies, and output provenance explicit?
- Terminal power user: do previews and handles reduce noise without hiding the useful raw detail?
- Brave beginner: does doctor explain missing dependencies and fallback behavior clearly enough to fix setup?
Acceptance criteria
- At least one rich-input workflow ships end-to-end with dependency probe, doctor surface, prompt guidance, and tests.
- Large tool outputs get preview/detail treatment instead of transcript flooding.
- New tool capability does not bypass existing approval, cost, or audit paths.
- Broad tool-registry work is either narrowed into tested slices or moved to v0.9.0.
- Release notes clearly state optional dependencies and fallback behavior.
Release theme
v0.8.46 should make tools feel like a studio, not a bag of subprocesses. Documents, images, code execution, search, and conversion should feel native, inspectable, and safe.
This is the tool-studio release.
Product thesis
The agent should have more leverage, but each capability must be discoverable, dependency-aware, permissioned, explainable, and compatible with the same state/evidence model as the TUI.
In scope
Candidate issue/PR clusters
Review lenses
Acceptance criteria