You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added a dedicated plan review and approval workflow, with compact summaries
in the thread and a focused surface for reviewing revisions before execution.
Added durable plan approval and handoff tracking so approved plans can be
delegated or implemented in a new thread without losing lifecycle context.
Isolated terminal drawer state by workspace and surfaced the number of active
scoped terminals directly in the chat header.
Added support for opening verified existing GitHub or GitLab branches, pull
requests, and merge requests as editable workspaces.
Plan Review and Handoff
Plan responses now render as compact summary cards that open a dedicated
review surface with version, status, step count, and revision controls.
Reviewers can comment on selected passages, request revisions, approve the
current plan version, and then delegate it or implement it in a new thread.
Approval and handoff events are persisted, published live, restored from
session history, and matched to the exact plan message, version, and content.
Completed plan versions remain available as read-only references after their
implementation handoff.
Terminal and Workspace Isolation
Terminal drawer visibility, expansion, and project or worktree scope are now
maintained independently for each workspace.
Switching workspaces no longer leaks terminal or session state from a
previously active workspace.
The chat header now counts terminals that are starting or running across the
current workspace's project and worktree scopes.
Added regression coverage for workspace drawer isolation, active terminal
counting, plan lifecycle projection, approval, and handoff state.
Existing Branch and Change Request Workspaces
The create-workspace flow can now validate a branch, GitHub pull request, or
GitLab merge request URL against the repository already open in DCC.
DCC verifies the forge host, repository identity, remote branch, change
request state, and source commit before creating an editable worktree.
Imported workspaces preserve source metadata and use the resolved head and
base branches for subsequent Git and forge actions.
Validation Before Publishing
Run desktop type checks: yarn workspace @dcc/desktop typecheck
Run the complete desktop test suite: yarn workspace @dcc/desktop test
Run the Rust workspace tests: cargo test --workspace
Check the Tauri crate: cargo check --manifest-path src-tauri/Cargo.toml
Confirm release metadata is 0.1.29 in package.json, sidecar/package.json, sidecar/src/index.mjs, src-tauri/Cargo.toml, and src-tauri/tauri.conf.json.