[jnumainville]

• Adds a minimal plan for consoles. No exec yet, which is tracked in a different ticket as it has additional nuances.
• Adds refined and explicit strategies for failure handling, which will becomes increasingly important with consoles and is a significant pain point in v2 (especially in regards to timeout). The emphasis here is enabling agents to handle most of this with targeted feedback and simple options.

[semanticdiff-com]

Review changes with  

[Copilot]

🟡 Changes recommended

Profile-reference identity and conflicting override persistence rules need clarification before implementation.

2 open issues

• Clarify whether --profile changes the workspace profile · New
• Include operate-as user in profile reference key · New

What changed in this PR

This documentation-only PR plans console management for the dh CLI and lightweight workspaces that isolate profile and console selections for projects and parallel agents. Script execution remains out of scope.

Changes:

• Defines console commands, creation defaults, lifecycle behavior, and errors.
• Specifies workspace resolution, copying, freezing, and selection persistence.
• Outlines implementation stages and acceptance criteria.

File	Description
plans/​console.md	Adds the console and workspace design, implementation sequence, and completion checklist.

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

The readiness rule must allow inspection and deletion of stopped or failed selected consoles.

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Allow show and destroy for stopped or failed consoles

plans/​console.md:102

The unconditional console_not_ready rule also applies to show and destroy without an explicit console, since both default to the console in use. This prevents inspecting or cleaning up a selected console after it stops or fails, despite those operations not needing a running console. Please distinguish console resolution from readiness validation and explicitly allow show and destroy for stopped/failed consoles.

2 resolved since last review

• Include operate-as user in profile reference key
• Clarify whether --profile changes the workspace profile

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

This documentation-only plan has one non-blocking contract clarification and introduces no executable changes.

1 open issue

• Allow show and destroy for stopped or failed consoles · New

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The documentation-only plan has no unresolved findings and introduces no executable changes.

No open issues 🎉

1 resolved since last review

• Allow show and destroy for stopped or failed consoles

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

The create retry contract needs an explicit attempt identifier to distinguish recovery from independent creates.

1 open issue

• Add idempotency support to distinguish console create retries · New

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

This documentation-only plan has no identified blocking issues and clearly separates new console creation from inspecting uncertain outcomes.

No open issues 🎉

1 resolved since last review

• Add idempotency support to distinguish console create retries

_{Review effort: Balanced}

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

_{Tip: disable this comment in your organization's Code Review settings.}

[jnumainville]

Oops, unintentional rerequest

[Copilot]

🟢 Approval recommended

No active review issues are identified for the documentation-only console-management design plan.

No open issues 🎉

_{Review effort: Balanced}

[bmingles]

This looks good to me. Just left 1 clarification question

[bmingles]

What does "Per field: flag > --json > default" mean?

[jnumainville]

That's the priority the args are used. So flag has higher priority than the same field in json which has priority higher than the default.

[Copilot]

🟡 Changes recommended

The plan places console actions in src/console/, conflicting with the architecture’s required src/actions/console/ layout.

1 open issue

• Place console actions under src/actions/console/ · New

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Human assessment is needed because shortcode mapping and subsequent detail authentication are undefined for environment-authenticated users without a saved profile.

No open issues 🎉

1 resolved since last review

• Place console actions under src/actions/console/

_{Review effort: Balanced}

[jnumainville]

No meaningful changes from the approved version. Going to go ahead and start on stack instead of addressing it all in this PR.