Repository navigation
Release 1.3.0 - #11
Conversation
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Saved state and migration types/index.d.ts, hooks/limits.ts, hooks/register.tsx, AGENTS.md, README.md, docs/usage.md, .claude-plugin/plugin.json |
New saved-view types and size limits support module-memory inboxes, legacy-state migration, and mirroring to $.state. The documentation describes reload behavior, and the plugin version changes to 1.3.0. |
Session selection and inbox recording hooks/register.tsx, hooks/inbox.ts, README.md, docs/usage.md |
Session hooks copy inboxes for branches, restore retained inboxes for qualifying resumes, and create fresh inboxes otherwise. Event handlers record conversation and agent updates in memory. The documentation describes these session rules. |
Pane actions and branch context hooks/register.tsx, hooks/inbox.ts, hooks/text.ts, hooks/views.tsx, docs/usage.md |
Pane actions use the displayed drawing’s inbox identity and sequence limits. Status and rendering read in-memory inbox state. Branch captures display parent-conversation context. The usage guide describes pane history and status behavior. |
Priority:
Estimated code review effort: 4 (Complex) | ~60 minutes
Change: Feature
Sequence Diagram(s)
sequenceDiagram
participant ClaudeCode
participant RegisterHooks
participant ModuleMemoryInbox
participant PluginState
ClaudeCode->>RegisterHooks: session.end and classic.SessionStart events
RegisterHooks->>ModuleMemoryInbox: retain, copy, restore, or create inbox
RegisterHooks->>PluginState: mirror current inbox view
Possibly related PRs
- dot-agi/high-command#9: Introduced the saved state that this PR migrates.
- dot-agi/high-command#7: Introduced pane and agent-lane state fields that this PR restructures.
Merge Risk: 
Minimal · up to b9f9d
-
This release changes how inboxes follow
/branch,/resumeand/clear. No actionable merge-blocking issue was found in the supplied changes, so it looks ready to merge after normal checks.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
Docstring coverage is 87.04% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 54 functions across 6 files. (4 skipped: 4 unsupported.)
-
Finishing Touches
-
📝 Generate docstrings
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
The inbox now follows the conversation across
/branch,/resume, and/clear./branchkeeps the inbox as it stood at the branch point: the main inbox, the agent lanes, the peers, and the read and Hide marks. A message you had not read stays unread, with its sender label and anysuspiciousmark. The pane and/highcommandsay when you branched and how many messages came from the parent conversation./resumeof a conversation that ended in the same Claude Code process restores its inbox, for the last 10 conversations./clearstarts an empty inbox./resume. A/forkcopy,/background, andclaude --resumefrom a shell start a new process, where High Command starts empty.Update:
claude plugin update high-command@high-command, then start a new session or run/reload-plugins.Summary by CodeRabbit
/resumerestores an inbox only if the mod has not reloaded; reloads preserve the current inbox but discard retained ones./branchcopies the inbox. Fresh or forked conversations start with an empty inbox.