Understand an actual project's code through standard editor AI chat, real execution and the native debugger in VS Code and Cursor. Save an explained code path as learning material, or independently generate a repository-wide DeepWiki site.
| Feature | Experience |
|---|---|
| Live explanation | Ask /codebook in Copilot Chat or Cursor Agent. The AI operates the real application/runtime, pauses actual source, explains in chat and continues. Inspect values in the native debugger. |
| Learning replay / time-travel debugging | Replay the application, the source executing at that time and historical values/stack in the native debugger in sync. Repeatedly step backward/forward and seek after runtime exit. The live chat area becomes a learning summary with a sequence diagram. |
| Independent LLM Wiki / DeepWiki | Reproduce DeepWiki itself through the editor AI's generation skill: full chapters, diagrams, source citations, reader navigation and repository Q&A. Keep local/configurable output, chat/browser updates and source links into your editor. Runtime/debug MCP and learning are independent. |
The owner retired the three selectable UI themes, not these distinct feature screens. Codebook Activity Bar navigation reaches them. The v9 product image is owner-approved after GStack design review. Implementation follows the local execution guide and acceptance map, reached from AGENTS.md, with mandatory visual inspection.
This is a private preview, not a Marketplace or Open VSX release. The delivered version is 0.2.29.0, delivered by Cycle 0045 through PR #86: the frozen natural /codebook request was submitted three times in each editor and every Codebook cause that stopped it is fixed (sixteen, each with a test; the last four are proved on prepared runs of the declarations that failed, in both editors), the replay keeps its image where a stop's recorded pause ends, and the 222 defects Cycle 0044 left are closed (191 by a fix with a test that fails without it, 31 by recorded evidence). No submission reached the observed result on its first admitted run, so that proof goes to the next feature cycle's frozen request. Its installed trials ran on pre-release builds in VS Code 1.140.0 and Cursor 3.23.12 for Linux, shown through WSLg on a Windows host; the Wiki update in Cursor was observed with a labelled stand-in for the Cursor Agent CLI, which is not installed there, and every native observation is bounded development evidence for the build its record names, not acceptance. Cycle 0046 is a bug-fix cycle that takes every defect Cycle 0045 left (the list); the feature cycle after it starts clean. What each earlier cycle delivered, with its tests, trials and limits, is in the change history and in that cycle's record under docs/cycles; PROJECT_STATE.md holds the verified scope and the open gaps.
The specification is goal version 9, and the implementation targets external repositories. Historical fixture or coupled-Wiki success is not proof of that destination.
Until final acceptance begins, actual-editor development verification uses the owner-designated nextjs-dashboard checkout. Final acceptance requires all nine designated projects in two stages, both editors and every applicable runtime use case. No version 9 Stage 1 or Stage 2 PASS is claimed.
| Question | Source of truth |
|---|---|
| How must an agent build and verify the product? | AGENTS.md, IMPLEMENTATION.md |
| What image must an agent open and inspect? | Approved v9 PNG and visual contract |
| What are the features and how do they relate? | PRODUCT_GOAL.md |
| What exactly is saved learning? | Learning replay specification |
| How is Wiki independent, generated and updated? | LLM Wiki specification |
| What must pass before completion? | Final acceptance, fixed project matrix |
| What is implemented, verified and next? | PROJECT_STATE.md |
| How does the existing preview work? | Version-qualified installation and usage, change history |
| How do development and review work? | DEVELOPMENT.md |
| What is the current design authority? | DESIGN.md, behavioral design |
Read AGENTS.md when starting or resuming work. Claude Code also enters through CLAUDE.md. Repository documents own outcomes/state; issues mirror them.
- Goal Issue #1 remains open until all acceptance conditions and owner acceptance hold.
- Cycle 0045 Issue #85 is closed after PR #86 (record): the frozen natural
/codebookrequest was submitted three times per host, sixteen causes that stopped it are fixed and the 222 defects Cycle 0044 left are closed (rows); what it leaves is the task list of Cycle 0046, a bug-fix cycle (the list). - Cycle 0044 Issue #83 is closed after PR #84 (record): Update LLM Wiki ends with a result the learner can see on the Wiki page and in the editor, and of the 440 defects earlier cycles left open 439 were closed before the pull request and the last one on it, when the new DOM check job passed (its first run failed for a missing video encoder on the CI runner, and the workflow was fixed) (rows). It is the first cycle under the cycle rule.
- Cycle 0043 Issue #80 is closed after PR #81 (record): a stop the debugger binds on the next line is accepted there instead of ending the run. Work resumed on the owner's direction of 2026-10-03 on a Windows host with WSL (hosts rule).
- Cycle 0042 Issue #78 is closed after PR #79 (record): a pause away from the next declared stop's line that the debugger makes and resumes by itself after a continuation no longer ends a live run.
- Cycle 0041 Issue #76 is closed after PR #77 (record), Cycle 0040 Issue #74 after PR #75 (record), Cycle 0039 Issue #72 after PR #73 (record), Cycle 0038 Issue #70 after PR #71 (record), Cycle 0037 Issue #67 after PR #68, Cycle 0036 Issue #65 after PR #66, Cycle 0035 Issue #63 after PR #64, Cycle 0034 Issue #61 after PR #62, Cycle 0033 Issue #59 after PR #60, Cycle 0032 Issue #56 after PR #58, Cycle 0031 Issue #53 after PR #54, Cycle 0030 Issue #50 after corrective PR #52, and Cycle 0029 Issue #46 after PR #48. Each next cycle Issue is created through
/spec(delivery chain). - Closed cycle records preserve historical results, failed attempts and their exact source/host boundaries.
Advance only the active phase authorized by the owner. After the v9 design review, the owner authorized product implementation; PROJECT_STATE.md records the current phase and next action. Record actual evidence and update the active cycle and PROJECT_STATE.md before handoff.