Repository navigation
feat(usage): include bounded local OpenCode history - #886
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
|
UI evidence attempt (isolated state): started this PR head with a new task-owned base directory, opened a fresh collaborative-browser tab using its one-use pairing URL, and attempted a snapshot. The preview returned PreviewAutomationExecutionError; the Vite server reported HTTP 431 (request header fields too large). No before/after image could be captured. I stopped only the task-owned dev server. The focused service and client typechecks remain the UI contract verification; this is an evidence gap, not a claim that the browser flow passed. |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
OpenCode task-host usage history was absent from Pylon's usage view, even though local SQLite and legacy JSON stores can hold project-level token and cost records. This adds a bounded local reader and merges its records into Pylon's existing usage cache and v8 contract while retaining v7 source attribution and existing Antigravity behavior. External OpenCode
serverUrlinstances remain outside this local history scan; Cursor account-wide history remains a separate maintainer decision.The reader caps root entries, files, bytes, nested entries, and records; reports partial coverage for limits or malformed source data; and does not cache corrupt files as complete. Canonical roots and record fingerprints prevent duplicate counting. The contract retains compatibility with v7 summaries.
Verification: focused reader and shared merge tests 25/25; targeted service integration 1/1, covering SQLite/legacy JSON, duplicate roots, remote exclusion, warm/restart cache and partial status; final reader regression tests 6/6; scoped typechecks for server, contracts, shared, client-runtime, web and mobile passed; scoped lint, format and diff checks passed. An independent pre-PR adversarial review rechecked the final head and reported no high-confidence issue. The final review revision changed only the reader and its tests, so the slower service test was not repeated after that revision.
Related: #865; frozen T3 source
e5a46d6c5d00b89afba5274a94d42428c8d79763(#10409).Model: GPT-6 Sol (low), Pylon Codex harness.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.