Dev Command Center v0.1.30

v0.1.30 Release Notes

Highlights

• Added fork-safe delivery workflows that preserve source repository identity
  while keeping pushes, reviews, and merge targets explicit.
• Expanded the Inspector with normalized GitHub and GitLab review state,
  approval requirements, pipelines, jobs, and actionable failure context.
• Added assisted recovery for Git and pipeline failures, plus a configurable
  Delivery Gate that derives whether work is blocked, needs attention, is ready,
  or has been delivered.
• Brought live agent activity and delivery context into the workspace rail.

Fork-Safe Delivery

• Workspaces now retain source and target repository metadata instead of
  assuming that every branch should be delivered through the default remote.
• Push and change-request actions resolve the intended remote, repository,
  branch, provider, and authenticated forge account before making changes.
• GitHub pull requests and GitLab merge requests share normalized review data
  while preserving provider-specific concepts and links.

Review, Pipelines, and Recovery

• The Inspector now surfaces reviewers, pending approvals, review decisions,
  pipeline status, jobs, and failure details for GitHub and GitLab.
• Delivery failures capture a structured snapshot and are classified into
  actionable categories such as authentication, permissions, branch conflicts,
  protected branches, and failing checks.
• Recovery guidance offers safe retry or follow-up actions based on the current
  failure instead of leaving raw Git or provider errors without context.

Delivery Gate

• Delivery Status combines local changes, commits, review state, approvals,
  conflicts, and pipeline health into a single derived state.
• Repositories can define delivery policies for required approvals, clean
  pipelines, resolved discussions, and other merge-readiness expectations.
• The workspace rail reuses this delivery context to show compact progress,
  elapsed activity time, recent completion state, and PR or MR readiness.
• Rail metadata refreshes at a lower background cadence than the active
  Inspector to keep provider and Git activity predictable across many visible
  workspaces.

Models and Validation

• Added Claude Opus 5 to the Claude Code model catalog and migrated legacy Opus
  aliases to the current model identifier.
• Added an opt-in authenticated smoke harness for validating GitHub and GitLab
  delivery flows against real repositories without running in the default test
  suite.
• Added regression coverage for review normalization, failure classification,
  recovery actions, delivery policies, workspace activity timestamps, rail
  recaps, and model resolution.

Validation Before Publishing

• Run desktop type checks: yarn workspace @dcc/desktop typecheck
• Run the complete desktop test suite: yarn workspace @dcc/desktop test
• Build the desktop application: yarn workspace @dcc/desktop build
• 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.30 in package.json,
  sidecar/package.json, sidecar/src/index.mjs, src-tauri/Cargo.toml, and
  src-tauri/tauri.conf.json.

Dev Command Center v0.1.29

v0.1.29 Release Notes

Highlights

• 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.

Dev Command Center v0.1.28

v0.1.28 Release Notes

Highlights

• Added a one-click way to run the workspace's configured fix tasks directly
  from the Inspector, with confirmation before any task can change files.
• Improved the integrated terminal with persistent custom tab names and a fix
  for terminal applications that started before their initial size was ready.
• Added validation for typographic dashes in workspace task flags, preventing
  commands such as —fix from silently running with the wrong argument.

Workspace Automation

• The Inspector now shows when the current workspace has configured fix
  tasks and can run all of them from a single action.
• Fix-task runs use the saved workspace configuration, show the execution
  report, and refresh Git and automation data when files change.
• Commands in .dcc.toml are now rejected when a flag begins with a
  typographic dash; the error explains to use ASCII hyphens, such as --fix.

Terminal Experience

• Terminal tabs can now be renamed without restarting or interrupting their
  running PTY; the name is preserved for the project.
• The terminal keeps the first measured viewport size while its PTY starts,
  so full-screen applications receive the correct dimensions immediately.
• Added regression coverage for terminal startup sizing and saved tab names.

Inspector and Review

• CodeRabbit review remains available when a branch has committed changes,
  even when the working tree itself is clean.
• Workspace paths in the branch toolbar now show their full value on hover.

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.28 in package.json,
  sidecar/package.json, sidecar/src/index.mjs, src-tauri/Cargo.toml, and
  src-tauri/tauri.conf.json.

Dev Command Center v0.1.27

v0.1.27 Release Notes

Highlights

• Improved Claude provider execution so authenticated sessions and sidecar
  lifecycle handling remain reliable across command launches and resumptions.
• Made file mentions and Quick Open search more resilient, keeping the composer
  focused on the intended file while results update.
• Expanded the Git conflict resolver with safer agent-assisted suggestions and
  clearer controls for reviewing, applying, and saving resolutions.
• Added visible Git-refresh feedback after commit, push, pull-request, merge,
  and sync actions, so changed-file updates never appear to vanish silently.

Claude Provider Reliability

• Strengthened the Claude sidecar protocol handling for streamed events,
  commands, and session continuation.
• Improved recovery and diagnostics around sidecar startup and provider output so
  failures can be surfaced without losing the active workspace context.

Composer File Navigation

• Fixed file mention matching and selection behavior when filtering composer
  suggestions.
• Improved Quick Open result filtering and keyboard navigation so searches keep
  the selected file stable as their result set changes.
• Added regression coverage for mention search and file navigation behavior.

Conflict Resolution and Git Feedback

• Improved agent-assisted conflict resolution with more reliable turn tracking,
  cancellation, and safeguards around proposed file content.
• Added clearer conflict-resolution feedback and protections before saving a
  result that could unintentionally discard content.
• Git actions now show a compact loading indicator while the changed-file tree
  refreshes; existing file-tree animations remain visible.
• When Git state is initially unavailable, the Inspector now explicitly reports
  that changed files are being read instead of leaving the area unexplained.

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.27 in package.json,
  sidecar/package.json, sidecar/src/index.mjs, src-tauri/Cargo.toml, and
  src-tauri/tauri.conf.json.

Dev Command Center v0.1.26

v0.1.26 Release Notes

Highlights

• Added simple multi-workspace tasks that keep one conversation while safely
  authorizing multiple project worktrees.
• Preserved the existing single-workspace experience: planning remains optional,
  and normal conversations can inspect, edit, and test the projects selected for
  the task.
• Added coordinated delivery that commits, pushes, and opens or updates a separate
  pull request only for projects that actually changed.
• Improved agent-assisted Git conflict resolution with live activity, cancellation,
  session access, and safeguards against applying an unexpected empty file.

Simple Multi-workspace Flow

• Select one or more registered projects while creating a workspace.
• DCC creates an isolated worktree and branch for every selected repository and
  exposes only those managed roots to the agent session.
• A single composer and history are shared across the task, allowing the agent to
  coordinate producer and consumer changes without manually copying context between
  projects.
• Codex, Cursor, Claude, and Gemini receive additional workspace roots through their
  native multi-root mechanisms. Providers without validated isolation remain
  unavailable for multi-workspace sessions instead of receiving unsafe filesystem
  access.
• The project switcher directs Inspector, file navigation, search, and terminal
  actions to the selected member while preserving the shared conversation.

Delivery and Lifecycle

• Deliver N rechecks every project, skips clean worktrees, runs configured
  beforePush checks, and processes each changed repository independently.
• Existing pull requests are updated when possible; closed or merged branches are
  reported clearly instead of being reused silently.
• Partial failures stay isolated to their project and never trigger a destructive
  cross-repository rollback.
• Archiving, restoring, and removing a multi-workspace task now operate on the whole
  bundle, including its member worktrees and sessions, without leaving secondary
  workspaces behind in the single-project navigation.

Conflict Resolution Safety

• Agent conflict suggestions now wait for the actual turn completion instead of
  treating the initial running state as a failure.
• The resolver displays summarized activity and streamed output in a collapsible
  panel, links to the underlying session, supports cancellation, and warns when the
  agent requests permission or user input.
• Whole-file suggestions that unexpectedly return empty content are rejected when
  either conflict side contains text.
• The editable result reports line and character counts and warns before saving an
  empty file. Saving marks only that file as resolved; it does not create a commit or
  push.

Compatibility and Limits

• Existing project registration, single-workspace creation, archive, diff, review,
  and pull-request flows remain available without multi-root behavior.
• Git operations across repositories are intentionally not transactional. A
  successful pull request in one project is not rolled back if a later project
  fails.
• Grok and Droid remain unavailable for multi-workspace tasks until their native
  isolation behavior is validated; they continue to work in supported
  single-workspace flows.

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.26 in package.json,
  sidecar/package.json, sidecar/src/index.mjs, src-tauri/Cargo.toml, and
  src-tauri/tauri.conf.json.

Dev Command Center v0.1.25

v0.1.25 Release Notes

Highlights

• Prevented the persisted desktop query cache from exhausting WebKit's
  localStorage quota and leaving the application on a blank dark screen.
• Preserved fast restarts with a bounded snapshot of useful workspace and
  session metadata while keeping the complete in-memory cache unchanged.
• Added automatic recovery for users who already have an oversized, legacy, or
  malformed dcc-query-cache entry.

Query Cache Reliability

• Limited the persisted query snapshot to 1 MB so drafts, preferences, and
  other application state retain ample storage headroom.
• Prioritized repositories, workspaces, providers, session summaries, and
  recent thread histories in the restart snapshot.
• Excluded file contents, searches, diffs, and other heavy or ephemeral query
  payloads from persistence without changing their live in-memory caching.
• Added size-aware compaction that keeps the most useful and most recently
  updated queries when the snapshot approaches its budget.

Automatic Recovery

• Migrated the query cache to a versioned snapshot that automatically removes
  only an incompatible or oversized dcc-query-cache during startup.
• Kept the SQLite database, worktrees, sessions, composer drafts, selections,
  themes, and all unrelated localStorage keys untouched.
• On QuotaExceededError, evicted only the regenerable query snapshot and
  retried the bounded write automatically without requiring a maintenance UI.
• Added a fallback that continues without persisted query data when WebKit
  storage is unavailable.

Regression Coverage

• Covered query allowlisting, size-budget enforcement, legacy migration,
  preservation of unrelated local data, and quota recovery.
• Confirmed the complete desktop test suite, production frontend build,
  TypeScript checks, and Tauri crate checks pass before publishing.

Validation Before Publishing

• Run desktop type checks: yarn workspace @dcc/desktop typecheck
• Run the complete desktop test suite: yarn workspace @dcc/desktop test
• Build the production desktop frontend: yarn workspace @dcc/desktop build
• Check the Tauri crate: cargo check --manifest-path src-tauri/Cargo.toml
• Confirm release metadata is 0.1.25 in package.json,
  sidecar/package.json, sidecar/src/index.mjs, src-tauri/Cargo.toml, and
  src-tauri/tauri.conf.json.

Dev Command Center v0.1.24

v0.1.24 Release Notes

Highlights

• Restored the final merge-conflict completion step after the last conflicted
  file is resolved.
• Made Git review actions clearer with a persistent changes indicator and a
  working branch-name copy action with localized feedback.
• Prevented Codex account-usage requests from hanging when the app-server keeps
  sending unrelated notifications.

Merge Conflict Completion

• Kept validation configuration available throughout an active merge so the
  completion screen is ready as soon as all conflicts are resolved.
• Simplified the merge-ready surface to keep the final validation and commit
  action focused and reliable.
• Added regression coverage confirming that the repository remains in the
  merge operation with no unresolved conflicts before the merge commit is
  completed.

Git Workbench Polish

• Kept the Git changes hint visible while there are changes waiting for review
  and the inspector remains collapsed.
• Replaced the inactive branch-details menu item with a functional action that
  copies the current branch name.
• Added success and error notifications for branch-name copying in English and
  Portuguese.

Codex Usage Reliability

• Applied one request-wide timeout to Codex account-usage calls so unrelated
  app-server notifications cannot extend the request indefinitely.
• Added bounded process shutdown and kill-on-drop behavior to avoid leaving a
  Codex app-server process running after a completed or timed-out request.
• Added a regression test that continuously emits notifications and verifies
  that the account-usage request still times out on schedule.

Validation Before Publishing

• Run desktop type checks: yarn workspace @dcc/desktop typecheck
• Run the complete desktop test suite: yarn workspace @dcc/desktop test
• Build the production desktop frontend: yarn workspace @dcc/desktop build
• Check the Tauri crate: cargo check --manifest-path src-tauri/Cargo.toml
• Confirm release metadata is 0.1.24 in package.json,
  sidecar/package.json, sidecar/src/index.mjs, src-tauri/Cargo.toml, and
  src-tauri/tauri.conf.json.

Dev Command Center v0.1.23

v0.1.23 Release Notes

Highlights

• Resolve Git merge conflicts entirely inside Dev Command Center, without
  leaving the workbench for a browser or external editor.
• Configure versioned project automation for workspace setup, manual fixes,
  and safety checks before completing merges or pushing changes.
• Keep the conflict workflow focused and responsive with friendly workspace
  labels, localized timestamps, and a dedicated full-width resolution surface.

Built-In Git Conflict Resolution

• Added a structured conflict resolver backed by the Git index instead of
  parsing conflict markers as the source of truth.
• Added per-hunk and whole-file actions to accept the current branch, accept
  the incoming branch, or accept both sides in a deterministic order.
• Added an editable result surface, support for modify/delete conflicts, and
  safe handling for binary, oversized, and non-UTF-8 files.
• Added a reviewable agent-assisted resolution flow. Agent suggestions are
  applied only to the editor buffer and never staged or committed silently.
• Added merge abort, final validation, merge commit, and push as one coherent
  in-app workflow.

Project Automation

• Added .dcc.toml tasks with check and fix modes, optional relative
  working directories, and per-task timeouts.
• Added optional before_merge and before_push hooks. Fix tasks remain
  manual-only and cannot run automatically.
• Preserved workspace setup behavior and backward compatibility with the
  existing scripts.validate configuration.
• Added a project automation editor under Settings > Git with full command
  output, exit codes, durations, and clear Git-tracking status.
• Project automation runs only for explicit actions; no background polling or
  periodic command execution was introduced.

Safety And Localization

• Added configuration hashing and workspace fingerprints to stop merge or push
  completion when commands, tracked files, or the Git index change during
  validation.
• Added path confinement for task working directories and compare-and-swap
  protection for conflict edits.
• Added complete Portuguese and English localization for the conflict and
  automation experiences.
• Fixed composer message timestamps so relative time follows the active DCC
  language instead of always falling back to English.

Validation Before Publishing

• Run desktop type checks: yarn workspace @dcc/desktop typecheck
• Run the complete desktop test suite: yarn workspace @dcc/desktop test
• Build the production desktop frontend: yarn workspace @dcc/desktop build
• Check the Tauri crate: cargo check --manifest-path src-tauri/Cargo.toml
• Confirm release metadata is 0.1.23 in package.json,
  sidecar/package.json, sidecar/src/index.mjs, src-tauri/Cargo.toml, and
  src-tauri/tauri.conf.json.

Dev Command Center v0.1.22

Release description

 ## Highlights

 Dev Command Center v0.1.22 introduces real account usage information for Codex and Claude while keeping the Composer clean and showing alerts only when user action may be required.

 ## Account Usage

 - Added an “Account usage” section to the existing provider/model menu.
 - Added a detailed usage view under Settings → Providers.
 - Codex reads structured rate-limit windows directly from the app-server.
 - Claude consumes structured rate-limit events from the Agent SDK and updates usage after provider activity.
 - Percentages are always labeled explicitly, such as “20% remaining”.
 - Providers without a reliable structured data source remain hidden from account usage surfaces.

 ## Composer Alerts

 - Yellow warning when 20% or less remains.
 - Red warning when 5% or less remains, or when the limit has been reached.
 - No permanent usage indicator is shown beside Send while account usage is normal.
 - Removed the artificial context estimate based on turn and checkpoint counts.

 ## Interface Improvements

 - Preserved the calmer Composer layout introduced by the recent UI refactor.
 - Replaced the internal “T3-style runtime” reference with the neutral “Isolated runtime” label.
 - Added clear loading, error, and waiting-for-Claude-activity states.

 ## Validation

 - 178 desktop tests passed.
 - TypeScript validation passed.
 - Production desktop build completed successfully.
 - Tauri backend and Rust provider integrations verified.

Dev Command Center v0.1.21

Dev Command Center v0.1.21

This release simplifies and improves the reliability of the Git change review experience.

Highlights

• Removed the redundant edited-files card displayed after assistant responses.
• Made the Git indicator in the workbench header the primary entry point for reviewing changes.
• Preserved changed-file counts and added/deleted line totals.
• The discovery animation now appears only when real Git changes exist and the Inspector is closed.
• Clean workspaces no longer consume the one-time discovery hint.
• Preserved the Inspector’s subtle entrance animation.
• Kept delegation review flows connected to the Inspector.

Why This Changed

The previous card depended on tool metadata reported by each provider. Codex, Claude, and Grok do not always include reliable file paths, which could prevent the
card from appearing or produce inconsistent information.

The interface now relies on the actual Git state as the authoritative source for changes awaiting review.

Validation

• Typecheck passed.
• 175 automated tests passed.
• Production build completed successfully.
• cargo check completed successfully.