CodeHerderSearch⌘KRequest access →

What shipped: October 2026

Every change you can see in October 2026, one section for each day, with the versions of that day.

October 202631 days

Changes on 2026-10-31

Versions: v15.47.21 to v15.55.25.

Breaking: ch quality optimization policy, ch quality optimization enable, ch quality optimization disable and ch quality analyzer are removed. Use ch improvement configure --capture on|off and --analyzer on|off to set the switches. Use ch improvement policy to read both switches and the analyzer limits. The old optimization policy and analyzer policy routes are gone too. Use the Improvement policy route. See Improvement.

Breaking: Six old flag spellings are removed. Use --from-file in place of --file on ch device credential create. Use --from-file in place of --token-file on ch device git-token create. Use --from-file in place of --spec-file on ch survey create, ch survey edit and ch survey template create. Use --search in place of --q on ch task list. Use --clear in place of --none on ch task set-parent. Use the bare --enabled or --disabled flag on ch observability alerts list in place of --enabled true or --enabled false.

Breaking: Only an owner of the top-level workspace can mint a SCIM token. CodeHerder now refuses every SCIM request from a token that a non-owner minted, and it revokes that token. If your token stops working, have an owner mint a new one. See SCIM.

Breaking: CodeHerder refuses a literal credential in a before-stage command, in a Dockerfile fragment, and in the environment of a stage or workflow override of an Evaluation. Remove the literal value from the spec. See Stage environments.

Breaking: CodeHerder refuses to move a workspace when the move would leave tasks on a workflow or stage that the new parent does not define. The refusal names the first tasks. Move or finish those tasks first. CodeHerder also refuses to remove a stage from a group while a task below it uses that stage. See Workspaces.

Breaking: CodeHerder refuses to mint or rotate a device token on a microVM pool device. A pool holds no token of its own. Each VM gets its own launch token. See MicroVM runners.

  • ch session create now starts the session and prints the session id. In --json, sessionId and sandboxId are separate fields. Session commands also accept a sandbox id. ch session resume is the main name for the older ch sandbox activate, and both work. See Dev sessions.
  • Evaluations: ch evaluation tree prints the evaluation tree of a workflow. ch evaluation preview prints the stages, changes and attempt count of each setup. ch evaluation report --stages adds a comparison for each stage. ch evaluation create asks you to confirm spend, as run does. The detail page shows the configuration, changes and figures of each stage. The attempt terminal shows its last working screen at once. A report hides launch-config arguments and environment values. See Evaluations.
  • Stage library: The stage form has a change note with a visible length limit. Stage version history has a Revert action. See Version history.
  • Costs: The Cost per completion chart is now in USD per completion and has its own chart. See Costs.
  • Members: Revoking all access of a person now also ends their Slack links and their inbound endpoints. See Members and teams.
  • Messages: Archiving a message retires its pending direct-message notifications. See Messages.
  • Jira: CodeHerder hides secrets in the free text that it sends to Jira. See Jira.
  • ch wiki import keeps the path of each page. Before, an exported nested page moved to the root. ch --local now matches the server on several refusals, on the order of repository matches, and on a change note over its limit. See Local tasks.
  • Web app: The Teams list shows the owning workspace. A wiki page shows its Level and Path in the Details panel. Many layout fixes for tables, forms, focus rings and narrow windows.

Changes on 2026-10-30

Versions: v15.46.44 to v15.47.20.

Breaking: An Evaluation setup no longer takes harness, model, effort, launchConfig, stagePrompts or workflow. The definition now names one workflow at the top. A setup is that workflow plus overrides. CodeHerder refuses a definition that sends an old key and names the field. Move each old key into an override. For example, use launchConfig: {model: ...} on a stage override, and use prompt in place of stagePrompts. A grid takes overrides in axes in place of harnesses, models, efforts and launchConfigs. See Evaluations.

Breaking: An Evaluation setup no longer has its own credential. Attempts use the credential channel of the stage. Remove the credential key from your setups.

Breaking: An Improvement candidate of mechanism launch_config can no longer start an Evaluation, so a policy cannot enable it. Remove that mechanism from your policy. See Improvement.

  • Evaluations: A definition now freezes the whole workflow you name, with its agents and the pick for each stage. A setup can override any node of that workflow: a stage, its prompt, its agent or a launch config. The report now breaks results down by stage. The attempts feed names the pool entries that served each attempt. A refused override names the models you may use, and the web app has a Check action. An attempt now ends as throttled after a long provider backoff. Spend counts once per attempt. See Evaluations.
  • Inbound webhooks: The endpoints list has a State column and sortable headers. A Description is now a text area. See Inbound webhooks.
  • Improvement: A candidate shows its state as a badge beside its title. See Improvement.
  • Change size: A merged repository now keeps the change size that the git host reports. The badge and each repository show it. See Change shape.
  • Merge waits: A merge wait now settles as approved when a reviewer approves, or when the host reports the request ready. A merge wait no longer deadlocks a parent and its child. CodeHerder refuses a free-text blocker that names an open merge request of the task. Use ch task blockers create --on-merge-request. See Waiting for a merge.
  • Tasks: A task no longer returns to a stage that you removed. A status change after an administrative stage remap now runs its cascade. A stored workflow now follows the live stage library when you read it.
  • ch --local flags a closed merge request as the server does. It refuses a dependency on the ancestor of a task. It fans out mentions in comments and blocker reasons. It fills names for sessions, wiki pages, blockers and sandboxes. A task blocked on a merge request that merged now continues. See Local tasks.
  • Plan and SSO settings have an “On this page” band. A repository has a pencil that opens its commit identity editor. A detail page hides read panels while you edit and keeps record panels. See Repositories.
  • CodeHerder refuses a custom tool URL in a stage environment when it carries a token. It refuses re-run bodies and any query on GitHub release calls. See Stage environments.
  • Slack events of one route now keep their order after a retry.
  • A device that reports metrics now renews its sandbox leases.
  • Many fixes in the web app for tables, forms, panels, focus and layout on phones and narrow windows.

Changes on 2026-10-29

Versions: v15.40.2 to v15.46.43.

Breaking: ch evaluation watch is removed. The attempt Watch page and the live progress feed in the web app are gone too. Use ch session attach <session-id> to read a running attempt. Take the session ID from ch evaluation attempts. Only the person an attempt runs as can attach.

Breaking: The route GET /v1/evaluation-attempts/{id} is removed. Read attempts with ch evaluation attempts or the Evaluation report. Stop calling the route in scripts.

  • Evaluations: Assessment notes on a pair now explain why one setup did better than the other. An attempt counts screen redraws as progress, and its report quotes the last screen. An attempt that waits for a release stays alive, and the page says why placement holds it. See Evaluations.
  • Jira: Comments now show in the order they were created. When Jira refuses a request with a 400, you now see its message. A stored Jira token now shows as Hidden. The unused issue unlink route is removed. See Jira.
  • Slack: Deleting a Slack connection now removes the Slack user links of that connection. See Slack.
  • A merge wait now releases its blocker when a job fails anywhere in the pipeline tree, including child pipelines.
  • A role change on an agent outside your scope now answers 404. Deleting another member’s link now checks your rank. See Members and teams.
  • ch gives a local Codex session its brief through developer instructions.
  • ch --local parks a repeated release that made no progress as awaiting input, as the server does. ch refuses a pinned build sha256 that is not hexadecimal.
  • A workflow brief tells the agent to run verify --execute for a check that has a command.
  • The Model routing page now sorts by the Would-have column. A new schedule preselects a default workflow.
  • Several fixes in the web app for layout on phones and narrow windows.

Changes on 2026-10-28

Versions: v15.22.2 to v15.40.1.

Breaking: ch quality calibration is removed. The judge calibration routes, the CH_CALIBRATION_* server settings and the calibration section of the Quality page are gone too. The stage judge stays. Remove the settings from your server environment and stop calling the routes.

Breaking: --device is removed from ch evaluation create and ch evaluation run. The New Evaluation page has no device picker. Placement now picks the device. Use placement requirements to steer an evaluation.

Breaking: CodeHerder now refuses an untimed blocker whose reason names a time, such as “in 30m” or “at 01:15Z”. Use --until or --for to set the wait. Use --no-time to file the blocker untimed on purpose.

  • Improvement is a new section. A policy document sets the rules. Candidates can be accepted, declined, applied and rolled back. Each candidate has an Evaluation and a state history. See Improvement.
  • An Evaluation report now opens with a plain-English headline. An agent writes an assessment. It shows on the page and in ch evaluation report. Guardrails are a new setup dimension. Attempts use normal placement. The score of a merge request has a clearer name. See Evaluations.
  • A task now parks with an awaiting-input blocker after two releases in a row that made no progress. A parent starts its current stage when its last child finishes. Timed blockers release on a 15-second sweep. A merge wait settles on each green run and ignores child pipelines. Verifications run at the stage that a blocked task was parked from.
  • ch start on your own device now runs as you, with your own login.
  • A repository has an allow_release_actions setting. Set it in the API, with ch repo edit or on the repository page. A post-merge stage can then run release actions on that repository. Examples are a workflow dispatch and a tag push. A repository also has an allow_duplicate_url opt-out. See Repositories.
  • An admin can disable and re-enable a user in the web app. You can grant a direct role over an inherited one. See Members and teams.
  • Lineage shows tasks only by default. A Tasks only | All toggle switches the view. The URL takes ?scope=tasks or ?scope=all. See Task lineage.
  • Only a human admin sees webhook URLs and launch environment values unredacted. CodeHerder refuses a repository URL that holds a token. It refuses more environment keys that can run code, such as GIT_CONFIG_PARAMETERS and Cargo keys. An isolated session refuses all input.
  • A Sort options button replaces the Sort by menu. Row actions use one layout: an inline action and a More menu. Hub pages show link cards.
  • Stage Docker now works on Rancher Desktop (Lima). Stages start faster.
  • Several fixes in the web app for layout.

Changes on 2026-10-27

Versions: v15.13.15 to v15.22.1.

Breaking: ch device-server now fails at start when you pass --docker-executor or set CH_DOCKER_EXECUTOR. Before, it only warned. Use --isolation isolated or set CH_ISOLATION=isolated. The deprecated_start_flags device health check is gone.

Breaking: The trial-batches API is removed. Scripts that call the /trial-batches routes now fail. Use Evaluations to compare setups. The Trials pages in the web app now redirect to Evaluations.

Breaking: A microVM pool field spareCount is now warmFloor. The API refuses spareCount as an unknown field. ch device edit takes --warm-floor in place of the old spare flag. Update any script that edits a pool.

Breaking: The CH_DS_MICROVM_IDLE_RETIRE device setting is gone. A microVM no longer exits when idle. The server now suspends idle microVMs. Remove the setting from your device environment, and use idle_suspend_after on the pool.

  • Evaluations show live progress for each attempt. An admin can open a read-only Watch terminal on a running attempt. The report names the reason a valid attempt failed. All attempts start at once by default. CodeHerder retries an attempt that infrastructure lost, and does not mark it invalid. A device uploads device-server.log and you can download the artifact. The hidden check also runs on a merge. See Evaluations.
  • MicroVM pools have a warm floor of parked VMs. You can set idle_suspend_after and the maximum task duration from the API, from ch and from the web app. You can retire the idle suspended VMs of a pool on demand. Each launch shows its phase. Pool pages show the cost of the warm floor and of idle hours at real prices. A pool delete first pushes kept sandboxes. See MicroVM runners.
  • A stage can tick and defer acceptance items.
  • A writable stage pushes its work in progress every 30 minutes and before its microVM ends.
  • A failed required CI job now wakes the session. A task that waits on a merge request shows when the request is ready to merge. Agents can resolve mirrored GitHub and GitLab threads.
  • A pooled Codex credential now reaches the stage container.
  • The web app has landing pages for each section, and header links replace the tab strips. The Velocity view has an hourly option. You edit a stage prompt in the markdown editor. Stage names in report tables link to the stage library. Integration pages have an On this page rail. The Claude integration card shows a status badge.
  • An account email change must stay in the verified SSO domain. A session credential can no longer approve a request that widens access. Only a human can revoke the API key of another member. Mentions now reach agents whose home is in an ancestor group.
  • A skill description has a length cap. A survey title, prompt and choices have caps too.
  • A new Changelog support doc lists changes by day. Run ch support show changelog.
  • Several fixes in the web app for layout, numbers and empty states.

Changes on 2026-10-26

Versions: v15.0.20 to v15.13.14.

  • Evaluations can now report for each setup with paired intervals. Use ch evaluation run and ch evaluation report. You can upload a ch build for a setup and list the builds. A hidden check scores each attempt. A blind judge rates the quality of the merge request. See Evaluations.
  • Proof stages are new. A checklist item can have a proof stage. You can defer a proof stage forward, and the web app shows the deferral history. New ch task acceptance verbs manage proof stages and deferral. A task cannot leave the due stage until its proof is done.
  • Write rules for integrations now work for each operation and each target. A write approval has an always-allow option. A Jira issue that an agent creates links to its calling task. See Integrations.
  • CodeHerder now classifies failed CI jobs. Agents retry failures that come from infrastructure. See CI triage.
  • An outbound webhook can rotate its signing secret. See Webhooks.
  • You can set a placement priority for each device.
  • An agent can add a reason to a pending egress request.
  • MicroVM pools suspend idle VMs and resume them on demand. A pool has a slots_per_vm setting. CodeHerder retires a VM before its 8 hour limit and moves kept work first. On a Spot notice, a device parks each live sandbox with a WIP commit and a push. See MicroVM runners.
  • The stage image now ships a pinned Codex CLI. A device deletes the folder of a finished task only when all of it is in git.
  • A git host rate limit now makes CodeHerder wait and not block. A repo URL in the org-scoped scp form is now stored as https.
  • Several fixes. Name and label fields have length caps for inbound rules, guardrail notes, and workflow labels. A merged task that was blocked now shows its merge wait. An erase that leaves a workspace with no owner is refused.

Changes on 2026-10-25

Versions: v13.82.4 to v15.0.19.

Breaking: The older name for agent access to integrations is gone from the CLI, the API, plugins and server settings. Everything now uses the name integration. Use ch integration for the old command. Use the /integration-access, /integration-calls, /integration-requests and /me/integration-grants API routes. Rename the plugin file to integrations.yaml and its top key to integrations. Rename the old server settings to the CH_INTEGRATIONS_* names.

  • Evaluations are new. You define an Evaluation in YAML or JSON and run it with ch evaluation run. Each attempt runs sealed on a device, on the Docker executor or a microVM. A setup can pin a ch build. The web app has Evaluations list and detail pages. See Evaluations.
  • A microVM pool now shows as one device, and each microVM is an instance of it. One VM serves many sessions with cleanup after each run. A suspended spare resumes when a task is created.
  • One managed-settings approval now covers a workspace and a payload. The dialog shows the commands it will run.
  • An invitee can decline a workspace invitation.
  • A direct add of a member is limited to the verified SSO domains of the account. A role change that leaves a workspace with no owner is refused.
  • Task events and git host webhooks now reach the live session of a local task.
  • CH_SANDBOX_REPO_CLONES is now on by default. Each sandbox gets its own repo clones.
  • The side rail now groups items under Optimisation, People, Docs, and Help. Agent access and personal accounts are now on each integration page. Every device kind shows one sessions cell and one online dot.
  • A merge wait on the own merge request of a task now settles on a green pipeline. The Environment page names workflows and stages by label.

Changes on 2026-10-24

Versions: v13.73.3 to v13.82.3.

  • A task that waits on a merge request now resumes when the request merges or closes. If a pipeline fails or the request needs action, the task wakes so an agent can fix it. See Waiting for a merge.
  • A parent task now waits for its open children with no blocker. When the last child finishes, the parent closes itself. The blocked banner shows when the blocker releases by itself. A question blocker or a closed pull request blocker now shows one banner. See Blockers.
  • A task clears egress, question, and dependency blockers only through the object that caused them. A woken task gets the CI result of the finished head in its brief.
  • CodeHerder shows Claude’s managed-settings dialog and stores the approval for each workspace. See Claude managed settings.
  • ch shows a waiting-for-input note when a local harness waits on a dialog. ch task start --check names the real local worktree path.
  • Agents can create Jira issues with a parent, priority, assignee, custom fields, and links.
  • CodeHerder mints GitLab sandbox tokens for the group service account of a connection. It paces GitLab requests for each identity and group.
  • MicroVM pools can keep warm spares. The web app shows spares and their estimated monthly cost. A pool can take its share of ordinary work. See MicroVM runners.
  • A refusal now lists every required survey at once. A task keeps its tool cache between stages.
  • Markdown renders a bare UUID as a linked record title. The web app has a reports landing page. Boolean filters look the same everywhere, and create and edit forms have one sticky footer.
  • You can no longer edit a comment that CodeHerder posted to a git host.

Changes on 2026-10-23

Versions: v13.55.5 to v13.73.2.

Breaking: The device server no longer accepts --docker, --docker-image or --instance-name, or their environment variables. --docker-executor is a deprecated alias for --isolation isolated. A device started with one of them exits with an error that names the replacement. Start the device with --isolation isolated instead. See Agent isolation.

  • A workspace admin can upload guardrails, which are short scripts that check what an agent does in a stage. A command guardrail runs before a named command. If the script exits with code 2, the command does not run. A report guardrail runs at hand-off and can send the work back. Guardrails work the same on every harness. Edit them in Settings > Guardrails. Each edit makes a new version. Each session page lists the guardrails it loaded. See Guardrails.
  • Every agent question now blocks its task until a person answers. To give information that needs no answer, an agent posts a comment. See Agent input.
  • Secret consent is now given for each receiving session. You can add or remove consent, and CodeHerder warns you before it expires. See Device secrets.
  • Cursor now has native session support. It has session history and --resume for a chat. CodeHerder now shows session history for OpenCode and Pi. It classifies provider errors for Cursor, Codex, Pi, and OpenCode. See Harnesses.
  • Agent access to integrations now loads into Claude Code, Codex, Cursor, OpenCode, and Pi stages. Plugin MCP servers match integration kinds. You can connect a personal Jira account with Atlassian OAuth. Settings has new Integrations and Connected accounts pages with call activity. The Jira page shows the connection, rules, comment sync, stage mapping, and activity. See Integrations.
  • Workflows, agents, and commands now reach every harness as skill shims. The standalone judge runs on every harness.
  • A workspace, workflow, or stage can require an isolated device. Set the policy in Settings. MicroVM pool devices show in the web app and in ch. See Agent isolation and MicroVM runners.
  • Devices pause git on a GitLab 429 and resume after the reset. Instance pages show the GitLab request budget. Idle mirrors refresh on a timer.
  • CodeHerder no longer posts its own status check on pull requests.
  • A repeat red main run now wakes the tracking task. A long red run escalates.
  • A device refuses or rolls back an update when the new build does not start. Git host toggles are grouped on Settings General.
  • Only a person can make a direct message steer another session. An inbound webhook cannot have a person as acting member.

Changes on 2026-10-22

Versions: v13.45.0 to v13.55.4.

  • You can connect a Jira Cloud site and keep Jira issues and CodeHerder tasks in step. When an issue enters the status you choose, CodeHerder creates one linked task. When a task changes stage, the Jira issue moves to the status you mapped. Comments sync both ways with no echoes. A service-account token connects the whole site. Each comment names its author. See Jira.
  • Agents can now use connected services. A session gets the integration set that was decided at spawn. Read calls run. For a write call you choose to ask or allow. CodeHerder records every call. Jira and Datadog have agent access. A member can connect a personal Jira token. See Integrations.
  • New ch verbs manage agent access and list calls. A group setting applies to its workspaces, and the nearest setting wins.
  • GitLab webhooks are now registered by default and repaired when they break. Each failure names the cause and the fix. See GitLab webhooks.
  • A task can block on egress requests. The blocker resolves when every request has a decision.
  • CodeHerder now records every pull request or merge request that an agent opens. Await-merge has a cooldown for each ref.
  • The task list and board cards now show the task creator.
  • Devices show their isolation level and backend. The device server has a new --isolation flag. --docker-executor and --docker are deprecated. A device that is not isolated refuses a Dockerfile fragment. You can register a microVM pool from a stack with the registration token. See Agent isolation.
  • Stages now reach git hosts over plain https through a TLS terminating proxy. A git host 429 is now treated as backpressure.
  • Re-invites send a sign-in email again. Expired invites stay visible. The accept response names the role.
  • Only a human admin can write Jira settings, webhooks, Slack routes, and workflow overrides. Only a human can edit a task comment.

Changes on 2026-10-21

Versions: v13.35.34 to v13.44.19.

  • Provider pages under Integrations now hold the whole setup. The GitHub page has all GitHub setup. The Slack page shows the connection, routes, and recent deliveries. The GitLab page shows what the connection powers. See Integrations.
  • A failed image build can now open a build egress request. The web app and ch show build egress requests and build rules. Workspace build rules go into the image lock. Admins can get a Slack notice for a build request. See Egress approvals.
  • Plan-only infrastructure work no longer passes merge and verify as deployed.
  • Every Claude launch now gets a settings layer that CodeHerder owns. CodeHerder refuses a repo that commits disableAllHooks. See Claude managed settings.
  • You can attach a missing repo to a task. Before, the task had to change scope. The refusal now names the fix.
  • Group Tasks and Sessions rows now show the workspace that owns them.
  • Tokens that the git proxy mints for GitHub now cover the whole installation. So gh works in multi-repo stages. The proxy also follows redirects for Actions artifact and log downloads.
  • Task placement reports now name repo auth failures.
  • Several fixes. Creating a duplicate stage or workflow at the same time now returns a conflict. The Team detail page names and links the owner. ch rotate-token tells you a running device server needs no restart.

Changes on 2026-10-20

Versions: v13.27.21 to v13.35.33.

  • A stage gate message in Slack now has Approve and Reject buttons. CodeHerder applies the same checks as the web app. Slack updates the message to show who decided. You get a private reply if you may not decide. The buttons show after the server operator turns on Slack interactivity. See Slack.
  • An agent question in Slack now has a button that opens a form. Type your answer and send it. The agent reads it and continues.
  • You can link and unlink your Slack account from the Me page. You can also link it with Sign in with Slack.
  • Integrations in the web app is now a list of providers. Each provider has its own page for setup and status. Connected accounts have their own page. See Integrations.
  • A parked task now wakes when CI or a review arrives on its merge request. A merge-hold stage can send the task back. See Waiting for a merge.
  • Stages now support PHP and Composer, with a GitLab registry and a Packagist cache. See PHP stages.
  • A task now shows when its blocker releases by itself. A task leaving the blocked state now runs one cascade.
  • Workflows mark a stage instance as stale when the library has a newer version. See Stage library.
  • A personal device now needs owner consent when a change widens its access and when you restore it. A group can manage GitHub App installs and explains sibling installs.
  • Several fixes. The ch stage show and edit round trip now works. Deleting a field that needs a repo now clears the merge ref. Judge verdicts are hidden from task-bound sessions.

Changes on 2026-10-19

Versions: v13.18.2 to v13.27.20.

  • Slack delivery works. CodeHerder now sends matching events to Slack through a durable queue. Each workspace can have its own Slack routes. CodeHerder handles an uninstall and a token revocation. Self-hosters can now use Slack. PagerDuty is no longer an integration. See Slack and Slack app.
  • A plugin source can sync a pinned marketplace plugin into the catalog. Catalog agents and commands now reach Claude sessions. The session page lists synced plugin items and their outcomes. A device can opt out with CH_SYNCED_CATALOG. New ch verbs manage plugin sources. See Plugin sources.
  • The dashboard Cost panel now charts the average cost of each completed task. Total spend uses the same chart on a second axis. See Costs.
  • The dashboard has a workspace URL link chip with the favicon and page title.
  • MCP has new read tools for task children, questions, and blockers, and a type filter. Public OAuth clients can use loopback redirect URIs. See MCP tools.
  • The ch terminal UI has new session details, repos, and task info screens. Documents show as styled blocks with markdown, and you can select text in them.
  • ch now resolves SSH host aliases before it matches a checkout origin. --event and --events parse the same way on every verb.
  • Session records keep the names of skills, sub-agents, scripts, and files in tool calls. The git proxy relays GitLab npm registry reads.
  • Only a human admin can use forceMergeConfirm. Task reopen now applies the uncomposed exit check. An admin re-invite sends the temporary password again. The Register repo dialog keeps its draft.

Changes on 2026-10-18

Versions: v13.12.10 to v13.18.1.

  • The ch terminal UI has restyled menus, settings, buttons, footer hints, harness picker, and project setup screens. Session and task actions now sit in the tab header. The session list updates from live events.
  • ch now records the token use and cost of each local session.
  • New ch eval commands take a snapshot and report paired differences with their uncertainty. You can run one offline eval attempt in a fresh local instance.
  • ch has an opt-in HTTP request trace. Use --trace-http or set CH_TRACE_HTTP.
  • The API can tail and long-poll the comments of a task.
  • Both webhook lists can filter by availability. The schedule detail page now shows the type and the outcome of the last run.
  • Stages now install bun packages through the device pull cache. See Package downloads.
  • The local runtime now has a bound. It names the command that frees a slot, and a stopped session releases its slot. A discarded worktree frees its slot.
  • A device variable now follows the personal-device consent rule. Local wiki writes keep the scope and agent pairing.
  • Several fixes. A request that the client cancels now returns 499 and not a server error. Status gates now run when a workflow composition advances a task. The read watermark in messages now passes an old unread message.

Changes on 2026-10-17

Versions: v13.8.2 to v13.12.9.

  • CodeHerder now posts a status check on the pull request or merge request of a task. The public status badge has a brand design. See PR status.
  • The server now mints GitHub App and GitLab project tokens for each sandbox workspace. You can connect a GitHub App install that you started on github.com. CodeHerder reads merge state through the App when it covers the repo. See GitHub App.
  • uv and PyPI clients now download through the device pull cache. See Package downloads.
  • Better GitLab handling. CodeHerder ignores repeated and stale deliveries, maps requested changes correctly, and no longer treats a recheck status as a conflict. It posts task status as skipped until the task is done.
  • ch start shows the reason when the server refuses a start. ch start --check also checks --arg values.
  • Credentials are now refused in custom tool download URLs, wiki links, branding links, and merge request URLs. CodeHerder removes credentials from comments that it posts to a git host. Only a person can write git host credentials.
  • CodeHerder now audits alert rule writes. Role grants on invitations and SCIM now fail closed when the audit write fails.
  • When Claude refuses to resume a conversation, the stage now starts a fresh conversation once.
  • Judge sandboxes no longer show to a working session. Open blocker notes close when a task reaches a terminal stage.

Changes on 2026-10-16

Versions: v13.3.6 to v13.8.1.

  • Stages now download npm, PyPI, Go module, and Playwright files through a pull-through cache on the device. The cache serves public content only. Stock Playwright and Puppeteer now work in the stage image. See Package downloads.
  • Docker-executor stages get their own run-scoped Docker endpoint with a per-run network. Devices tell the server when they support stage Docker. CodeHerder removes the Docker objects of a run that crashed.
  • You can filter the task list by one or more creators. A parent task now shows the cost of its whole subtree. The Costs page accepts custom and calendar date ranges. See Costs.
  • A repo can show an opt-in public pull request status badge. See PR status.
  • Subscriptions now show why a delivery waited and for how long. CodeHerder also finds and repairs missing conflict notifications. See Subscriptions.
  • Egress requests: a target has one pending request. A decision from the workspace closes the others for that target.
  • Field limits now apply to the remaining fields.
  • Security fixes. Session credentials can no longer test, delete, or redeliver a webhook, write inbound webhook rules, or upload attachments. Only a person can create or rename a team. Env keys for registries, download hosts, and browser binaries are refused. The stage image ships a patched Chromium.
  • ch task live now shows open questions that do not block the task. ch removes credentials from the origin URL when it joins a task. An agent can no longer empty a checklist field.

Changes on 2026-10-15

Versions: v13.2.28 to v13.3.5.

  • Field character limits now show in the UI and apply everywhere you write a field. See Field limits.
  • You can now allow an egress request after the fact, even when it was denied or has expired. See Egress approvals.
  • A device can now trust approved repos and plugin marketplaces in a narrow scope. Linking a personal device now needs consent from its owner. See Device trust.
  • A schedule now runs the task creation checks each time it fires.
  • Only a person can reopen a task, and the web app offers Reopen only to people who may use it. Archiving a repo that has hooks needs the right permission, and CodeHerder records who did it.
  • Security fixes. Dev-session credentials can no longer change task status, blockers, approvals, verification, parents, or dependencies. Session credentials can no longer accept an invitation. Webhook errors no longer show resolved IP addresses to tenants. A workspace export now includes only the direct messages that the exporting admin can read.
  • Container Claude sessions move to another credential when the current one runs out.
  • Self-update uses the compressed CLI copy when the server offers one.
  • Sign-in with OAuth for MCP is stricter. An unauthenticated /authorize call no longer makes an OAuth client permanent. Callback failures show a clear page.
  • Local ch fixes. Activity feeds and repo lists honour paging and archive filters. Local comments show actor names. A local launch refuses to start with an active blocker.

Changes on 2026-10-14

Versions: v12.67.6 to v13.2.27.

Breaking: The API no longer reads the agentId, taskId, workspaceId and repoId query parameters. A request that sends one of them now gets an unfiltered list. Use agent, task, workspace and repo instead.

  • You can start a ch session from a parent folder that holds several repos. You choose the folder the session starts in. The session sees every reachable repo and clones a missing one when it needs it. See Project folder.
  • Hybrid repos work offline. ch queues task creates, task edits, and edits to workflows, rubrics, and skills, and sends them when you connect. ch auth login offers hybrid, and you can join a hybrid repo from a second clone. You can also move a hybrid repo back to local.
  • New ch commands pull and push workflows, rubrics, and skills with a three-way view of the differences. The workflow page now shows what changed between two workflow versions.
  • The ch terminal UI has framed tabs and sidebar. Harness tabs and remote sessions follow the ch theme. The console tab header lists the repos of the session.
  • Device GitHub App tokens now carry CI read, pull request write, and issue write permissions. Read-only stages can comment and review through the git proxy. A device warns you when it stops minting GitHub App tokens. A repo can opt in to workflows: write on writable tokens. See Git tokens on a device.
  • A device now frees stale build caches and reports the state of its data disk.
  • The server no longer limits the number of repos on a task or sandbox. CodeHerder now finds host events that it missed and shows the integration health of each repo.
  • Webhook and hook routes that mint secrets now refuse session credentials. A session credential can no longer change a member email address.
  • Several fixes. CodeHerder recovers runs stuck in the starting state after a server update. It recovers tasks whose pull request closed in a merge holding stage. ch honours the createdBy=me filter for agents. Table layouts in the web app have better spacing.

Changes on 2026-10-13

Versions: v12.54.0 to v12.67.5.

Breaking: A blocker note can no longer link a task. The --blocked-on flag is gone from ch task block and ch task blockers create, and the API refuses blockedOnTaskId. To wait on another task, run ch task depends-on <taskId> <upstreamTaskId>. Open blocker notes that point at a task become dependency edges. See Blockers.

Breaking: The preview-only ch publish verb is gone. Use ch transfer start to preview the same selection.

  • Connect a GitHub App to a workspace with ch githost app install or from the web app. CodeHerder checks that the installer is an account admin. GitLab projects get a webhook when you connect a repo. See GitHub App and GitLab webhooks.
  • Pull request and merge request comments now appear as task comments. A task comment can post back to the PR or MR. Admins can set rules on the Integrations page to hide bot comments.
  • A task that waits for merge requests shows the live merged, closed or reopened state. A one-time repair fixes older tasks. Sessions can subscribe to host events and to question and input events.
  • The Tasks list and the task page show unmet dependencies.
  • You can manage passkeys and an authenticator app from your profile page. You can also change your password there.
  • The ch terminal UI has light, dark and system themes. The sidebar can collapse and you can drag it. Each tab shows a working, idle or blocked state, and keys and themes can be set from env files.
  • Local mode serves workflow compose, workflow and stage writes, ch msg send, inbox and ch skill. It delivers messages to live local sessions. Existing local data moves to the new file store once, with a check. See Local tasks.
  • You can promote local workflows, rubrics and skills to a cloud workspace as new versions. You see a reviewed diff first. You can also join a promoted workspace from a second clone.
  • ch auth login in an offline repo asks if you want local or cloud. ch init writes detected check commands. ch repo workspaces --url lists the workspaces that hold a repo.
  • A stage that cannot write gets a read-only checkout of a live repo attach. The harness picker shows slow or degraded harnesses.
  • Several fixes to access rules. Only a human admin can move, archive, restore or delete a workspace, and only an admin can restore a repo. A username-only token in a git URL is refused.

Changes on 2026-10-12

Versions: v12.45.4 to v12.53.51.

Breaking: A workflow can no longer declare an llm-judge verification. CodeHerder removed existing entries and their route_to settings, and a write that adds one is refused. A judge verdict no longer routes a task. To pick the rubric for a stage, run ch quality judging rubrics set <stage> <rubric>.

Breaking: On a self-hosted server, the server binary now exits with code 2 when its first word is not a known subcommand. Check that your start scripts pass no stray argument. The CH_JUDGE_ARMING_CORPORA_PER_PASS and CH_JUDGE_ARMING_REFRESH_INTERVAL settings are gone. Remove them from your config.

  • Judging has its own stage-to-rubric map. Use ch quality judging rubrics list, set and unset to manage it. Plan, code and review stages use their built-in rubrics by default.
  • Self-host operators get two new server subcommands. migrate applies pending database migrations and exits. schema-check fails when the database holds migrations that the binary does not know, so you can tell if a rollback is safe.
  • Local mode provisions a sandbox per task and reuses it for rework. It parks a stage at the resume cap and parks a reject loop at the shared cap. Native local stages keep a persistent tool cache. See Local tasks.
  • ch member invite now creates a pending invitation. New ch member deprovision and ch member reactivate verbs manage member access. See Members and teams.
  • A task that waits for a human merge shows the pull request state from the host and offers a next step. A task is flagged when all awaited PRs have merged. See Waiting for a merge.
  • The task page and the workflow page show a workflow graph with stage progress. Stages show their write policy and their effective environment.
  • A create-task rule on an inbound webhook can set the task repo or no checkout. See Inbound webhooks.
  • Dockerfile fragments for stage environments refuse ADD, ONBUILD, COPY --from and heredocs. System packages install in place on a --docker device. Devices report disk use and warn before the disk budget blocks a build. See Stage environments.
  • Cursor and OpenCode are seeded as agents. A harness that cannot run a task is refused.
  • Web app polish: lists show a default sort, mostly newest first. Admins can list archived wiki pages. The Subscriptions panel keeps its delivery state in the URL.
  • Several fixes to access rules. A session credential can no longer mint SCIM tokens or inbound endpoints. Deprovision and revoke-all also revoke agent keys and MCP consents.
  • Repo create needs a human owner or admin. A stage assignee can no longer change the task repo set or operate its sandbox.
  • Several fixes to merge tracking, alert incidents, workspace stats and ch self-update.

Changes on 2026-10-11

Versions: v12.29.393 to v12.45.3.

Breaking: Devices now keep one disk budget for environments and caches. The device server no longer reads CH_CACHE_BUDGET_MB, CH_TOOLCACHE_MIN_FREE_MB or CH_TOOLCACHE_TRIM_DRY_RUN. Remove them from your device configuration. To change the free-space floor, set CH_DEVICE_DISK_FLOOR_MB. See Self-hosted device disk growth.

Breaking: A device server that runs as root with CH_AGENT_USER set now stops at startup. Run the device server as a non-root user. See Agent isolation.

Breaking: An integration edit that changes the host, base URL or site now needs a new secret in the same request. Update scripts that change these fields to send the secret too.

  • Stage environments: a workspace now has an Environment settings page. It shows the layers, lets you add a tool, previews a change and keeps history with revert. See Stage environments.
  • Workflow and stage layers have their own environment history and revert. Group layers fold into every child workspace. A stage environment can add system packages. Each stage shows its effective toolchain.
  • Devices build environment images and stages run in them. A status matrix shows build state with logs and Rebuild. New ch env verbs include status, log, rebuild, releases, lock, diff and system.
  • npm, pip and Go tools resolve into a locked set. The resolver checks cosign and SLSA signatures. An optional Trivy scan of device-built images is report-only. The scheduler places a stage on a device that matches the workspace toolchain lock.
  • ch start shows a launch options panel on its harness tiles. Right-click a tile or press o to skip permission prompts or add extra flags. Workspace workflows are available as Claude Code workflows in dev sessions.
  • When a member who does not own a schedule edits it, that member becomes the owner. Later runs file tasks as the new owner. Schedule changes are now audited. See Scheduled tasks.
  • Outbound webhooks have a detail page with Test, Edit, Enable or Disable, and deliveries. Stage, survey template and alert rule creates open their own page. After a create, you land on the new item. See Webhooks.
  • Web app updates. Skill detail opens read-first with an Edit button. Device detail shows an enabled badge and a toggle. Task and member pickers search the server.
  • Operators can read the workspace deletion record with ch instance workspace-deletions.
  • Several fixes to network access. The proxy now checks the TLS server name on CONNECT. The toolchain cache refuses writes through planted symlinks.
  • Several fixes to access. Only the owner can weaken a personal device’s settings. Message reads require workspace access. An invitation checks the inviter rank when it is accepted. A session of a device that reconnects to another replica is kept.

Changes on 2026-10-10

Versions: v12.29.286 to v12.29.392.

  • You can edit an alert rule from its detail page. The metric stays locked. See Alerts.
  • A schedule detail page opens read-first. Select Edit to open the schedule editor. See Scheduled tasks.
  • Ctrl+Enter or Cmd+Enter submits every multi-line form field. After you archive a workspace, the web app offers Undo.
  • Both integration kinds show Disconnect in the page header. The Conversations panel shows a count chip like Inbox and Sent.
  • Several security fixes. OIDC endpoints must use https. OAuth redirect URIs refuse every loopback spelling, and the OAuth client name follows the display-name rule. An OAuth authorize error before sign-in shows on its own page and never redirects. Workspace, device and CLI names refuse control characters.
  • Only the uploader or a workspace admin can delete an attachment. The accepted role of an invitation is the role stored when it is accepted. The owner-role ceiling is checked when a role changes. A device token mint fails after the device is archived.
  • An edited comment no longer leaves its old text in the comment notification. An MCP consent is revoked when its grant is replayed as revoked.
  • More actions are audited. New events cover skill selection, optimization policy, integration enable changes, comment edits and archive actions.
  • Several fixes to the web app. Lists keep loaded rows when the next page fails, and show one Try again. Create is disabled with a reason when a required option list is empty or failed to load. Copy agent is disabled with a reason when nothing can be copied.
  • Local mode matches the server for more routes, for example a reused attachment id now answers 409.

Changes on 2026-10-09

Versions: v12.29.162 to v12.29.285.

Breaking: The workflow write API and the SSO connection update API now refuse unknown keys with a 400 error. Before, the server ignored a misspelled key and returned success. Check your scripts and API calls. Remove unknown keys and use the exact key names.

  • A device now checks that it has a git credential for every listed repo before an agent starts. If it does not, the device refuses the start. CodeHerder tries other devices and parks the task with a reason when all refuse. See Git tokens on a device.
  • The Unattributable records report shows workspace names and has a workspace picker. The Workflows list shows each workflow’s type key under its name. The Install CLI page marks the platform it detects.
  • The Costs page shows a routing loss in the Model routing Savings column. The Tasks filter bar stays on one row when stages fail to load. The New task form stays when workflows fail or are empty.
  • A webhook that never delivered now shows “No deliveries yet”. The API reports this state as no_deliveries. The audit log now records webhook auto-disable and re-enable, and the re-enable on an OAuth integration reconnect.
  • A login page shows a retryable notice when the auth config fails to load. A task-list item in Markdown toggles its checkbox when you click its text.
  • Several fixes to access rules. A human must mint or revoke agent keys. Revoking an API key needs the same rights as minting it. A judge verdict filed under another verification is refused. A session credential is refused on workspace export. An invitation is sent only to the invitee.
  • A live terminal attach re-checks your operate rights on each reauth. A user who loses that right is disconnected. Deprovisioning a member stops live runs that use the member’s revoked keys. Every API key revoke is now audited.
  • Personal data in event payloads is redacted. This covers run location and device host details.
  • Every committed status change now runs the full status cascade. Questions answered on a blocker also resolve it with the right authority.
  • An agent dev session pinned to a device must now pass the placement checks. Onboarding readiness ignores disabled devices. Schedule and inbound webhook edits use the same validation as create.
  • Several layout fixes at phone width on task detail, settings, branding and egress pages.

Changes on 2026-10-08

Versions: v12.29.49 to v12.29.161.

  • The Messages page has a Reply action under the conversation thread.
  • The Quality report, Review debt and Setup comparison pages have an On this page rail. The wiki editor Preview now resolves wiki links. A link to a page that does not exist yet shows a hint that it resolves when you save.
  • ch workflow compose has new --reason and --reason-file flags. A bare instances array without a reason is refused before any request is sent. ch workspace set-parent reports the server’s 409 reason. ch githost auth-check hides the credentials in the remote URL.
  • Several security fixes. Device hostnames no longer leak through the display-name fallback. Secret values are hidden in device setting events and in the copyable agents list. The live session tail redacts secrets.
  • A human must link or unlink a device from a workspace. Copying an agent config with launch args needs admin rights on the source. SCIM refuses profile writes to an owner. When an SSO connection is disabled, a concurrent enable no longer turns it back on.
  • A microVM runner now serves one session only. It stops taking new work when that session starts. It shuts down when the run ends. See MicroVM runners.
  • A workflow edit that removes a stage can no longer move live tasks into a terminal stage. A blocker park now revokes the stage key. A finished trial batch stays finished when you cancel it.
  • The question panel of a task refreshes on input-need events. Cost events reach the right session row. A dev session that stops on an unreachable device shows the stop reason.
  • Web polish: a bare fence in Markdown renders as plain text. Message rows keep their divider at phone width. The Setups table keeps at least three rows.

Changes on 2026-10-07

Versions: v12.25.77 to v12.29.48.

Breaking: The stage before_script key moved to environment.before_stage. Stored stages moved automatically. A write that still uses before_script now fails with invalid_input, and this includes stage documents in a repo. Change your API calls, scripts and repo stage files to use environment.before_stage. See Stage environments.

Breaking: A stage with a before_stage script now runs only on a device with an updated ch. An older device cannot take the stage, and the task waits with ch_update_required. Update ch on your devices. See Updating.

  • You can choose the launch config, harness, flags and permission bypass when you start a session. Use the web app, or ch start and ch session create with the new flags. A session that bypasses permission prompts shows a marker.
  • The workspace environment layer holds tools and a before_stage script, with versions and revert. Use ch env show, ch env set, ch env tools and ch env versions to manage it. See Stage environments.
  • New ch env search finds tools in the aqua registry.
  • A stage spec with an unknown key is refused with invalid_input. The error names the bad key.
  • A scheduled task now passes the task-create checks. A run-now fire creates the task as you. If the schedule creator is disabled or has no role, the schedule stops and shows an error.
  • The inbox shows the sender in bold on unread rows, with a solid unread bar. Secret fields have a reveal toggle, and the archive toast offers Undo. A tap opens a tooltip on touch screens.
  • Several security fixes. The git proxy refuses credential-minting sub-resources and case-variant GraphQL keys. A session exit tail is redacted.
  • A human must make every member and invitation change. An agent key can no longer do this.
  • The audit log now records manual webhook changes, API key mints and repo publication identity changes. It also records credentials revoked by device or agent archive. Deleting an SSO connection revokes its SCIM key.
  • Re-sending a pending invitation applies the new role. A user invited from the admin console can sign in when signup is closed. A device display name no longer shows a hidden hostname.
  • Dependency notes resolve when the upstream task finishes. The merge-ref cap is checked inside the write.

Changes on 2026-10-06

Versions: v12.23.16 to v12.25.76.

Breaking: Sessions no longer get the CH_RUN_ID and CH_TASK_SESSION_ID environment variables. A session now gets only CH_SESSION_ID and CH_SANDBOX_ID. Update hook scripts and other tools: read CH_SESSION_ID in place of CH_RUN_ID, and CH_SANDBOX_ID in place of CH_TASK_SESSION_ID. See Using the CLI.

  • A task can now have several merge requests. The task rows show the PR link, and a filter picks single-stage tasks. See Multi-repo tasks.
  • New ch asset download reads a public GitHub or GitLab release asset from a stage on an isolated device. The request sends no credential, and your egress rules still apply. See Package and browser downloads in containers.
  • New ch observability alerts incident reader, and ch task show shows one lifetime cost total. ch task result --discard checks that the task can be cancelled before it stops anything. It sends a cancel comment, which you can set with the new --reason flag.
  • Local mode now applies the server’s task, activity feed, dependency, parent and blocker rules, and it emits matching events. Local list routes page and filter like the server. ch --local is refused inside a session.
  • Plan caps now apply to device registration, device restore, repo restore and member reactivation. Webhook re-enable, test and redeliver need the webhooks entitlement.
  • Security fixes for keys and devices. A human must mint an agent API key on every route. Revoking a key revokes the login or MCP grant that owns it.
  • Only the owner can enable a personal device, and cleartext device tokens are refused on REST loops. Stage containers ignore git hooks planted in the shared repo mirror. The whsec_ webhook prefix is treated as a secret.
  • A parked task stops every live session. The owner gets a message when the reject-cycle cap parks a task. A linked agent question closes when its blocker resolves any way.
  • Sandboxes on a sleeping laptop stay alive when the laptop wakes. After three lost sandboxes on one device, a task moves to another device. The device tunnel reconnects fast after a server restart.
  • The --docker launcher keeps user tools and npmrc, and terminal history survives a device-server restart. The sandbox base adds pup, Docker Compose, Go 1.27.1 and a patched zlib. Old sandbox images are cleaned up.
  • In the web app, Ctrl+Enter or Cmd+Enter submits every Markdown form. A right-click or Alt+Enter on a stage chip selects only that stage. The session terminal colours have better contrast.
  • Self-host: each startup migration now waits a bounded time for table locks. Tune this with CH_MIGRATION_LOCK_TIMEOUT and CH_MIGRATION_LOCK_WAIT_BUDGET.
  • Inbound webhook endpoint updates are audited. Variable writes emit variable.* events. Several fixes to messages, wiki cache, cost attribution and workspace completed-task counts.

Changes on 2026-10-05

Versions: v12.19.6 to v12.23.15.

Breaking: The ch dev-session command is gone and exits with a hint. Use ch session in your scripts. ch session attach now accepts the sandbox id from ch session create or a session id.

Breaking: ch now refuses the old capability flag spellings --capability, --device-capability and --required-cap. Use --cap, --device-cap and --config-cap in your scripts.

  • A workspace can exclude a device it inherits. Use the Disable here action on the Devices page or ch device disable <ref> --workspace <ref>. See Devices.
  • New ch task questions reader. Cost tracking now works for Claude sessions started without --session-id.
  • A human Claude conversation continues after stop and resume. Session messages reach Claude natively inside a stage container.
  • The product version now shows the Core tag. ch update notices label versions as builds and name the Core product.
  • The ch terminal UI shows the key hint on the left and the tab state on the right.
  • The search popover has a Load more row for each result group.
  • A run bearer is confined to its own workspace, launch input and attachments. Agent task writes are scoped to the run’s own task. Only the owner can activate, attach or send input to an agentless session.
  • The git proxy now matches listed repos by validated host and path. It refuses repo paths that contain @, : or %.
  • The stage process limit is now 4096, and a run records a pid_limit exit cause. The unsent draft stays after a run exits. Stage containers run under docker-init.
  • Docker-mode stages now accept multi-line secrets, such as a GitHub App private key.
  • A task keeps its repo detach against stale sandbox reports. Sandbox restaffing is bounded after a no-progress self-release.
  • Web app polish. Board cards, filter bars and key-value rows are more consistent. Error toasts use one voice, and some offer Try again. Text zoom keeps a stable size.

Changes on 2026-10-04

Versions: v12.6.20 to v12.19.5.

Breaking: The API dropped old aliases that no supported ch release uses. DELETE /v1/devices/{id} is gone, and the session feeds ignore ?repo_id=. Sandbox responses no longer carry agentId or agentName. Update your scripts to call POST /v1/devices/{id}/archive, send ?repoId=, and read agentMemberId and agentMemberName.

  • Network access has more control. Eligible proxy denials become approvals with retry advice. Approvals show beside questions, and the web app manages workspace rules. Approved rules apply to running proxies with a bounded lease, and each proxy binds to its run. See Egress approvals.
  • The proxy now reports approvable denials automatically, also in local mode. The web app and ch show report times, the retry notice and the auto-report state. New ch egress commands request, approve and deny access, and list rules, grants and policy.
  • You can edit device settings from the device page. The page warns before a save that weakens a setting, and it shows drift and restart notices. See Device settings.
  • The product says “session” in place of “dev session”. New ch session create and ch session resume commands arrive. ch session tail now shows the transcript history from the device. See Session CLI.
  • The web form can launch a session as yourself or as a workspace agent. A local ch start session now acts with the role of the human who started it.
  • A stopped ch start session resumes in the same conversation. A manual activate resumes the stored transcript. Live sessions show per-edge progress and a stalled-edge status. An operator can stop a stalled session and keep its work and draft.
  • Skills can include script files, and a script with a shebang installs as executable. ch skill create and ch skill edit take --from-dir to upload a skill from a local directory. See Skills.
  • A repo can have its own publication identity. Agent commits in that repo then use this name and email. See Repositories.
  • The device image includes headless Chromium. A device pulls the promoted sandbox image by digest and trims Go caches under disk pressure. ch device-server --docker now runs the stage before_script by default.
  • Workflow fixes. Active stages stay while a task waits for dependencies. A Code task parks on missing input. Repeated rebases and CI runs are avoided.
  • Several security fixes. Agent callers can only act on their own run. The socket proxy and git proxy refuse duplicate JSON keys and unfinished GraphQL strings. Direct message bodies are redacted for callers who cannot read them.
  • Self-host operators can resend an expired temporary password with ch human resend-temp-password.
  • Web app polish. Focus rings, tables, tooltips and modals are more consistent. Mark-all-read and skill reset ask for confirmation. Timestamp tooltips show local time with the zone name. The reply composer opens from a message page.

Changes on 2026-10-03

Versions: v12.6.7 to v12.6.19.

Breaking: ch device-server --docker now exits at start unless CH_TRUSTED_EXECUTION=1 is set. Before, it only logged a warning. On each device that runs --docker, set CH_TRUSTED_EXECUTION=1 in the device environment, or move the device to --docker-executor. See Self-hosted device isolation.

Breaking: With CH_ENV=production, the server now requires sslmode=verify-full for every database that is not on the same host. It refuses sslmode=require and sslmode=verify-ca. The server maintenance commands apply the same check. Add sslmode=verify-full and sslrootcert= with your database CA to each database DSN, and connect by host name. See Require verified TLS on every connection.

  • Subscription rules are new. A rule on a task or a session changes which workspace events reach an agent session. Use the Subscriptions section on a task or session page, or ch task subscriptions and ch session subscriptions. See Choosing what reaches an agent session.
  • CI, git, comment, mention and direct message notices now reach sessions through subscription rules. One session mute now covers all CI and git notices. A muted channel queues nothing for that session.
  • A rule can let a session answer an event, such as resolving a blocker. A session can have a standing instruction for these events. Use ch session instruction and ch event-response.
  • The Notification rules tab on Messages lists every rule in a workspace with recent deliveries. Operators can read the delivery backlog with ch instance subscriptions.
  • A task watch can now pick exact events, actors and stages. Use ch task watch with --event, --actor and --stage. See Watching tasks and notifications.
  • A self-hosted install can pin the AWS device template and region in the web app configuration. See Pin the AWS device template.
  • A task-bound session can now send a direct message to any task or session in its workspace. Agent briefs on a Docker executor device now show the checkout path inside the container.
  • Local launches keep live launch metadata across device reconnects. Immediate local launches of Codex use native delivery. ch lists sessions from the same backend it launches on.
  • At teardown, a device now keeps session work on the device when the remote repo history was replaced. It does not push that work.
  • The terminal input ignores mouse reports when it tracks drafts. It also recognises enhanced keyboard submit and release reports.
  • Agent processes no longer inherit ambient OTEL_* variables. The server reads the proxy-written forwarded address by hop count.
  • Web app polish. Every composer sends with Ctrl+Enter or Cmd+Enter and shows a hint. Identical toasts merge, and at most three show. The web app detects macOS correctly.

Changes on 2026-10-02

Versions: v11.1.17 to v11.1.72.

Breaking: A --docker-executor device with --stage-egress=false or CH_STAGE_ALLOW_ROOT_IMAGE=1 now refuses to start without operator consent. Set CH_TRUSTED_EXECUTION=1 in the device environment to keep either override. Otherwise remove the override. A device that runs ch device-server --docker without consent still starts, but it logs a warning. Set CH_TRUSTED_EXECUTION=1 there too, or move to --docker-executor. See Self-hosted device isolation.

  • CodeHerder is now under the MIT license. ch --licenses and codeherder --licenses print the license and the third-party notices. The sandbox image also ships the notices of its components.
  • ch task repos create now attaches the repo live when an agent runs it in its own session. It checks the repo out into the running sandbox and prints the checkout path. Use --no-wait to return before the device finishes. Elsewhere it only records the repo on the task.
  • Self-hosting has a hardened reference deployment. It includes a restricted systemd unit, drop-ins and a reverse proxy file. See Hardening a self-hosted server.
  • A new guide and script check a self-host server host. They cover units, file modes, the proxy, disk encryption, certificates and clock sync. See Verify a self-hosted host.
  • A resumed harness run now links to the session it continues. The session API shows the link and the first session of the conversation.
  • Agent commits now name the person who filed the original task as author. The agent is the committer. In an agent dev session, you are the author. See Whose name is on a commit.
  • A workflow save is refused when a merge or verify prompt names a stage that the stage cannot move to. Existing workflows still load.
  • A device that refuses agent isolation for a task now cools down for that task. CodeHerder places the task on another device. The task shows the reason when no device qualifies.
  • Members below admin no longer see device host names and IP addresses in events.
  • Task creation no longer requires the fields that a stage gate needs later. A writable stage in process mode keeps the GitHub and GitLab CLI sign-in. A refused git credential request now says why.
  • Web app polish. The task status select shows the stage colour again. Filter bars wrap, tables fit their panels, and links in text are underlined.

Changes on 2026-10-01

Versions: v10.58.0 to v11.1.16.

Breaking: CH_REQUIRE_ISOLATED_EXECUTION now uses the same isolation check as git credentials. A device with this setting now refuses unattended stages unless it runs --docker-executor or the microVM image. The --docker launcher and an agent user no longer pass. Move the device to --docker-executor or the microVM image. To accept the risk on a trusted host, set CH_TRUSTED_EXECUTION=1. See Self-hosted device isolation.

  • A task that you create with no repo now gets the workspace default repo. If the workspace has no default, it gets the only active repo. A code stage can then push. A task created with no checkout still gets no repo.
  • Device limits for sessions and sandboxes now hold under load. The server locks per device around the count and the bind. A start that loses the race waits, and the task shows the reason.
  • The socket proxy on a Docker executor device now ties each container, network and volume to its workspace. A stage sees and changes only the resources of its own workspace. The proxy refuses unsafe container settings, such as published ports, and volumes that belong to another workspace. Stage networks from older devices keep working after the update.
  • An agent that survives a device server update keeps its git credentials. The new device server serves the credential socket again at the same path.
  • Nested Docker inside a stage now starts reliably on cgroup v2 hosts. A Docker executor device also tests the real stage resource limits when it starts.
  • A restored database now replays revocations and erasures made after the recovery point. A journal outside the database stores identifiers and times only. An operator runs ch instance restore-fence replay, and promotion is refused until replay has run. Replay is safe to run more than once.
  • A production server refuses to start with unsafe trace export settings. It refuses a collector URL that is not https, CH_OTEL_TRACES_INSECURE, and a malformed CH_OTEL_TRACES_HEADERS entry. The error names the setting and never prints a header value.
  • Audit and execution traces share one attribute allowlist. Exported attributes never hold customer text. A new guide lists the export failure counters.
  • The task status select is now neutral, with a badge in the stage colour beside it. Filter bars, table headers and tooltips are more consistent across the web app.
  • The sandbox image moves to a newer Debian base with security fixes. The web app updates its HTML sanitiser.

See what's next.

This page is the record of what already shipped. File a task and it's your herd building the next entry.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close