CodeHerderSearch⌘KRequest access →

What shipped: November 2026

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

November 202619 days

Changes on 2026-11-19

Versions: v15.128.25 to v15.128.44.

  • Workflows: The diff on a workflow proposal now shows every change, not only stages, fields and gates. It also lists edited and reordered stages, changed transitions, auto-staffing of unassigned work, the label, the workflow environment and other workflow settings. A “Privileged changes” line names a change to auto-staffing or to the access of a stage. Review it before you approve. ch workflow proposals show and ch workspace workflow preview-adopt-shared print the same lines. See Workflow proposals.
  • Workflows: A comment that arrives after a merge wait wakes and before the next wait starts is no longer lost. The next wait wakes on it. See Waiting for a merge.
  • Surveys: Two edits to the same survey at the same time no longer lose one of them. CodeHerder applies each edit to the latest version of the survey. If the survey keeps changing during a save, the save fails with 409 concurrent_modification. Save again. See Surveys.
  • Repos: Restoring an archived repo always checks the repo limit of your plan. It also runs the webhook setup when the restore succeeds, even if another change happened at the same time.
  • Integrations: When two writes race, a stored secret no longer stays attached to an endpoint that the other write changed.
  • Security: GET /v1/me/integration-sites now lists only the workspaces where you are an active member and that pass your single sign-on rules. Inside a session, it also stays in the scope of that session.
  • Security: GET /v1/me/invitations and its count now refuse every session credential.
  • Security: The list of your own API keys now stays inside the workspace scope of the calling session.
  • Docs: The Plugins, Waiting for a merge, Support bundle and Core concepts pages now match the product. See Plugins, Support bundle and Core concepts.

Changes on 2026-11-18

Versions: v15.128.1 to v15.128.24.

  • Workflows: A merge wait now wakes the task when the merge queue of your git host removes the request without a merge. On GitHub, this is the merge queue. On GitLab, this is a merge train that turns auto-merge off on the same head. CodeHerder waits until the removal is 2 minutes old. The settle reason is dequeued. A wait also settles when a request leaves the queue a second time after CodeHerder missed the enqueue event. See Blockers.
  • Workflows: A task parked from an externally_merged stage now wakes on a new comment or review on its request. The settle reason is commented. A bot under a drop rule, CodeHerder’s own identity and an approval do not count. CodeHerder waits until the newest comment is 90 seconds old, so one review gives one wake. The next brief lists the comments. A comment wake and the externally_merged prompt now also tell the agent to act under its stage instructions. They no longer say “fix and push” or “reply”. See Waiting for a merge.
  • Workflows: A question from a merge stage now closes when every awaited request has merged. The task then advances. Other blockers stay open.
  • Evaluations: A finished attempt now removes its run directory, also when a container wrote files as another user. The disk budget counts leftover run directories as space it can free, and the device server sweeps them at start. A refusal for lack of disk space no longer trips the breaker. The score phase for a merge request now has a time budget, so an attempt always ends and reports. The scorer no longer retries a command that cannot start. See Evaluations.
  • Agents: A shell command of a mini-swe-agent session now gets 2 minutes, not the mini default of 30 seconds. A command past the limit is killed with its process group, and the agent gets a timeout result. The system prompt states the limit. Set the new device setting CH_MINI_COMMAND_TIMEOUT to change it. See Harnesses.
  • Agents: CodeHerder no longer creates the default agents twice when two child workspaces start at the same time.
  • Security: GET /v1/resolve with a slug or a name now stays inside the scope of the calling session.
  • Sessions: A session no longer loses the last output of its process before the process exits.
  • Container stages: The NO_PROXY setting of a container stage no longer contains [::1]. Python httpx clients can now read it.
  • Docs: The self-hosted licence expiry, audit export outage, update guide and unsaved drafts pages now match the product. See Self-hosted licence, Audit integrity and Unsaved drafts.

Changes on 2026-11-17

Versions: v15.126.191 to v15.128.0.

  • Workflows: The merge stage has a new externally_merged setting. Set it on the stage instance when a person or an outside process merges the request. The agent then keeps the request ready and parks on it. It does not run a merge command. The stage needs awaits_external_merge, and its prompt needs the merge-mode placeholder. An agent cannot set it when it composes a workflow. A merge, a close, a conflict or red CI still ends the wait. A green pipeline or an approval does not. ch workspace workflow show and ch stage show now show the setting. See Waiting for a merge.
  • Evaluations: A mini Evaluation attempt now gets the device’s mini gateway address, as a normal mini session does. An Evaluation now freezes the plain mini version, so CodeHerder finds the matching mini release. See Evaluations.
  • Integrations: The Datadog RUM routes now have a read or write class. Before, each RUM call counted as destructive and CodeHerder refused it. Every RUM delete and retention-filter write stays destructive. The integration relay now decodes a gzip or deflate request body before the approval check. The approval now shows the arguments of such a write. The relay refuses any other encoding with 400 invalid_input. See Integrations.
  • Agents: A mini session on a task now starts at once with the task brief. It takes its title from the brief heading. It no longer waits for the idle reminder.
  • Subscriptions: A failed policy sync now shows the fixed detail sync_failed. It no longer shows the raw error text. See Subscriptions.
  • Web app: The caption on a blocker now names the marketplace approval. The markdown preview of an attachment now has a better layout.
  • Reliability: CodeHerder now saves the events for a merge reference, a forced merge and a first federated sign-in together with the change. A refused device-token mint now keeps its instance pin. The automatic retry of a loop budget and its release now happen in one step. If the release fails, the next check tries again.
  • Performance: The environment status and the task comment reads now load faster.
  • Docs: The GitHub App, subscriptions, surveys and writing style pages now match the product. See GitHub App, Surveys and Writing style.

Changes on 2026-11-16

Versions: v15.126.164 to v15.126.190.

  • Security: A device can now reach the Evaluation and case-validation routes only for a workspace it is linked to. A dev session can now read the repo commit list only for sandboxes inside its own scope. See Devices and Evaluations.
  • Workflows: The built-in merge stage now holds the task until every awaited request has merged. The merge agent still stages the merge and parks on the request. When the last request merges, CodeHerder advances the task with no new session. A refused advance names each request that is still awaited. To turn this off, shadow the merge stage with a workspace stage. See Waiting for a merge.
  • Webhooks: A CodeHerder event delivery now runs once, even when the sender signs each retry again. CodeHerder claims the event by its signed id for 6 hours. A retry after a 5xx answer runs the action again. See Inbound webhooks.
  • Reliability: CodeHerder no longer loses the event for a new agent question. It now saves the question and its event together. It also keeps the SSO credential expiry event and the device offline alert. The park events for a loop budget and the spawn breaker are now saved with the park itself.
  • Integrations: The Datadog error-tracking routes now count as read access.
  • Docs: The GitLab webhooks guide now matches the product. See GitLab webhooks. The reopen round cap and the merge-request list now read as shipped. See Reviewing work. The scheduled tasks guide now covers --field-file and the run-as owner. See Scheduled tasks. The PR status page now explains when the badge shows unknown. See PR status.

Changes on 2026-11-15

Versions: v15.126.130 to v15.126.163.

  • Breaking: Disabling an SSO connection now revokes its SCIM token and records sso.scim_token_revoked. Before, re-enabling the connection brought the old token back. If you re-enable a connection, mint a new SCIM token and update your identity provider. See SCIM and Single sign-on.
  • Security: A device that is unlinked, or whose owner left the workspace, can no longer read session guardrails or workspace knowledge. It can no longer send session reports, transcript chunks or session edges. See Devices and Guardrails.
  • Security: The workspace invitation list now refuses a non-human caller and a session credential. Create and revoke already did this.
  • Sessions: Only an admin can read the executions and the standing instruction of a session that is not a Work session. See Session transcripts.
  • Tasks: CodeHerder no longer loses the task.stalled event. If CodeHerder cannot record it, a later sweep tries again. Searching the task list with ?q= is also faster.
  • Agents: Copying an agent now keeps a disabled source disabled. It trims the role and checks the membership rules of a new agent.
  • Performance: Cost views and subscription lists load faster.
  • ch --local: CodeHerder now records session.renamed when you rename a session. It records subscription.changed when you write a rule. A dev session can no longer write egress rules. A task stall check now tests again whether the task is still stale. A status change of a child task, or a comment on a task, now clears the stalled mark on its ancestors. See Local sessions.
  • Web app: The hash on the device environments page now wraps and no longer clips.
  • Docs: Clear filters also resets the sort. See Sorting lists. The GitLab social token page now states the token for each mint mode. The codebase size page now matches the app. The directions to reports now match the report side navigation.

Changes on 2026-11-14

Versions: v15.126.82 to v15.126.129.

  • Breaking: ch task edit --subtree-budget 0 no longer clears the subtree spend cap. It now fails with an error. To remove the cap, use ch task edit --clear-subtree-budget. --subtree-budget now accepts only a positive dollar amount, for example 25 or $12.50. See Spend limits.
  • Spend limits: The API now refuses a negative amount on every spend-limit field with 400 invalid_input. Send 0 to clear a limit. This rule applies to the task budget, the subtree budget, the workspace budget, the daily and monthly spend caps, the agent daily cap and the task total cap. Before, the API stored a negative amount, but that amount set no limit.
  • Sessions: CodeHerder now records a session.renamed event when a person renames a session that has no task, or clears its name. A session credential now reads only the sessions of its own sandbox through the task transcript route. A human work session no longer sees approve and reject actions that it cannot use. A repeated session start no longer counts against the spawn breaker. See Session transcripts.
  • Plugins: A human work session can no longer approve a plugin install, or approve or skip a plugin offer. Do these approvals from a normal sign-in or token, not from a work session. The role rule did not change. See Plugins.
  • Security: Revoke all and deprovision now also clear the cached sign-in results of the member.
  • Audit and webhooks: CodeHerder now records agent.config_revealed when you create an agent config, not only when you read one. The team.member_role_changed event fires only when the role of a team member really changes. The last_delivery_at time of a webhook no longer moves back when delivery results arrive out of order. See Webhooks.
  • Repos: When you change the git URL of a repo, CodeHerder resets its activity sweep and starts again for the new URL. A sweep that is in progress can no longer write the data of the old URL onto the moved repo.
  • Evaluations: Each qualification check now gets the attempt wall budget as its time limit, and never less than 600 seconds. A qualification check that overruns its limit now gives a final unqualified result. The attempt no longer retries it without end. The microVM of an attempt now lives long enough for qualification, the attempt and an overrun. An invalid verdict from an unqualified attempt now names its reason. A hidden check that times out keeps the tail of its output. The warmed check home now keeps the Go build cache. A case validation that runs now survives a device auto-update and a tunnel reconnect. See Evaluations.
  • Devices: A disk-short image build now retries when a cache clean-up makes room. An --ephemeral device uses a smaller hard disk floor of 5 GiB or 10%, whichever is larger. A device that refuses a spawn as busy now gets a back-off of 1 to 15 minutes, not a new spawn every few seconds. See Devices.
  • ch --local: Creating an egress blocker follows the same rules as the server. Task create now checks the fields first, as the server does, so a bad field is reported before the session task cap. A local sandbox run now ends with the stop reason that the server uses. See Local sessions.
  • Self-hosting: A new guide explains how CodeHerder counts and paces requests to the git host, and why work pauses on a 429. The sample compose.yaml now sets CH_BASE_URL and CH_APP_BASE_URL, so the server boots in the container. The device server guides now cover the server address and the start-up errors. See Git host request budget and Running the device server as a service.
  • Web app: Tables on the Tasks, Completed tasks, Wiki health, device environments and integration calls pages now fit narrow screens better. Long values wrap.

Changes on 2026-11-13

Versions: v15.126.45 to v15.126.81.

  • Sessions: Only an admin can now tail or attach to a session that is not a Work session. The session list hides those actions from other members. A starter who loses the admin role loses an open attach. The Sessions page shows cost on rows that have no task. See Session transcripts.
  • Tasks: When a sub-task shows activity, its parents are no longer marked stalled. CodeHerder also re-checks a task just before it marks the task stalled. A task that got activity in that moment stays active.
  • Sessions, reliability: CodeHerder no longer marks a run lost when its device reported after the sweep read the state. It also spares a run whose sandbox lease was renewed after the scan.
  • Workflows: A person can now edit the acceptance checklist of a parked task. After the task resumes, the agent can tick the items. Before, its updates failed with 403.
  • Plugins: A plugin’s agent role now sends a member role change event when the approvals change. A direct role change on a plugin’s agent now fails with plugin_principal_role_locked. Change the approval instead. A schedule that you remove and add again now keeps its last fire time. See Plugins.
  • Security: CodeHerder now keeps a revoked app consent for Claude or ChatGPT in the revocation journal as its own entry. A restore replays it, so a revoked consent stays revoked.
  • Evaluations: The warm-up now caches the Go toolchains that a check script fetches. An offline check finds a toolchain that go.mod does not name. The docs explain how to pin attempts to devices with requiredDeviceCapabilities, how a device qualifies at attempt time, and the case roles. See Evaluations.
  • Sandbox: The sandbox image has a rebuilt git with the upstream fix for CVE-2026-105437. See Stage environments.
  • Connected apps: The docs explain Require SSO for Claude and ChatGPT. A workspace that needs SSO still shows its name in the list, marked as needing SSO. See Connect to Claude or ChatGPT and MCP tools.
  • Slack: The docs cover DMs of your task threads, the “Task finished:” reply and every ch slack command. See Slack.
  • Network access: An update to the egress auto-request setting that keeps the same value no longer takes a revision. It also no longer sends egress.settings_changed. See Network access approvals.
  • ch --local: It stamps a question answer with the same reason as the server. A budget park note carries the same human ask as on the server. A closed merge request no longer resets the merge-check failure count or clears the failure note. See Local sessions.
  • Web app: The Completed tasks page now reserves space for its three breakdown panels while it loads.

Changes on 2026-11-12

Versions: v15.126.21 to v15.126.44.

  • Webhooks: The seeded default agent roster now sends an agent.created event. See Webhooks.
  • Blockers: The bulk resolve action in an inbound webhook now follows the same rule as a single resolve. A caller that is not a human cannot close a note that asks a person. See Inbound webhooks and Blockers.
  • Sessions: A member can no longer read evaluation or assessment transcripts through the session history. CodeHerder records each history read in the audit log. See Session transcripts.
  • Evaluations: The cost of an attempt counts once in history and in spend. See Evaluations.
  • Plugins: A role change on an install takes effect at once. See Plugins.
  • Sandbox preview: The preview proxy limits its backlog, so a slow viewer cannot grow it without bound.
  • Devices: When you unlink a device from a workspace, the device can no longer send commit, change and discovered-repo reports to it. When a task ends, CodeHerder now saves the work of a standalone clone with a detached HEAD and removes its folder. Before, the folder stayed. See Devices.
  • Repos: The docs now explain how to move a synced repo back to local. See Connect a local repo. The base branch row shows a “Repo default” label. See Base branch.
  • Search: The docs describe the hint, no-match, error, clear and recent states. See Search.
  • ch --local: It uses the same checklist baseline as the server. It refuses to resolve a blocker that asks a person, as the server does. See Local sessions.
  • Web app: Table columns fit better on the Sessions, Surveys, Blockers, Jira rules, integration calls, plugin requests, wiki bundle and account devices pages.

Changes on 2026-11-11

Versions: v15.124.21 to v15.126.20.

  • Sandbox preview: A sandbox can serve its running app at its own URL. Preview hosts are isolated from each other. One preview cannot reach another.
  • mini-swe-agent: Evaluations, the seeded roster and local smoke runs now use mini-swe-agent. It runs tasks only. A dev session cannot launch it without a task, and the New dev session picker hides it. It resumes the conversation from the previous trajectory. It never titles a session from its instructions or launch line. See Dev sessions.
  • Repo activity: CodeHerder keeps merge request history for all time. You can read it over a range. The Change origin report has a range picker and shows the state of the history. The Repos list shows the split between CodeHerder and external changes. See Repo activity.
  • Devices: Health checks that pass fold behind one counted line. A failed check that blocks only one target now reads as degraded, not unhealthy. See Devices.
  • Spend limits: The docs describe the spend cap on a parent task and its subtree. A re-parent that drops a subtree cap needs the spend-limit writer. See Spend limits.
  • Require SSO: Message archive and restore follow Require SSO. A member’s key list and another member’s tasks and keys are narrowed to what you can reach. Launch evidence on GET /sessions/{id} follows the same gate as the launch input. The Slack channel list follows the same gate as the routes that write. A webhook URL shows unmasked only to a caller who can write it. See SSO.
  • Blockers: A caller that is not a human can no longer resolve a note that carries an ask. See Blockers.
  • Plugins: A schedule reads its expression from the live manifest. See Plugins.
  • ch --local: It follows the server’s stall lifecycle. It fans out @-mentions in a message. It refuses a verification in the same order as the server. See Local sessions.
  • Web app: The empty Recorded changes panel is now hidden.

Changes on 2026-11-10

Versions: v15.115.2 to v15.124.20.

  • Plugins: Plugin hooks, offers, the loop guard and the slot API now run. The gateway offers plugin actions as MCP tools. An install keeps its name. A manifest rename needs approval. You can offer an install on an account root of workspace kind. A plugin with no auth gets a connection offer. The install page reads “New plugin install”. Plugin action refusals have their own error codes. See Plugins.
  • Evaluations: You can pin an Evaluation to device capabilities. The pin is a hard gate. CodeHerder admits check containers by the disk room they need. See Evaluations.
  • Terminal console: The mouse pointer changes shape over controls. You can click the answers in Needs you. See Terminal console.
  • Reports: The Trend follows the page window. Report pages no longer show a date range for each section. Report tables grow to their full height. See Repo activity.
  • Repo activity: CodeHerder stores the times a merge request opened and merged. A new Change origin report has an Origin filter. See Repo activity.
  • Spend limits: The docs now describe the workspace daily and monthly spend caps. Settings points to them. See Spend limits.
  • My work: The Show team toggle moves into the Needs you panel header. See My work.
  • ch: ch session rename refuses an agent that has no run, as the server does.
  • Security: A plugin can post a comment only in the workspace of its run. The sync-operations accept action refuses the key of an agent member. Costs hide the title of a parent in another workspace. A change to the role, bucket or secret of a pool device is now audited.
  • Sandbox: A failed package fetch names the file and the URL.
  • Web app: Many tables fit their content better.

Changes on 2026-11-09

Versions: v15.101.57 to v15.115.1.

Breaking: ch quality setups no longer takes --section. Run ch quality stage-signals --section setups in its place. See Stage signals.

  • Task dependencies: Each dependency can release on done, planned or mr_opened. A workflow stage can set a planned or merge milestone. A new workspace setting, Stacked dependencies, turns on stacking (ch workspace edit --stacked-dependencies on|off). ch workspace stacking-check warns about repo settings that work against stacking, such as a required squash merge. A stacked task starts on the branch of its upstream merge request. Its merge waits until the upstream merges. See Task dependencies.
  • Stage overlays: You can write overlays with the API, with ch stage overlay and in an editor in the web app. The API, ch and the app show the compiled stage prompt. Workflows, stages, skills and launch configs carry a managed-by marker. See Stage overlays.
  • Slack: Each task gets one card in its channel, with its events in a thread. A terminal stage posts a finish reply. A reply in the thread becomes a comment or an answer, and Require SSO applies. You can read the text of a question or blocker and unblock a task from Slack. Answer buttons show by default. The closest human gets a direct message of the task thread. Each Slack link has a “Slack DMs” setting (ch slack links edit <id> --dm-threads on|off). Admins see a prompt to reinstall the app. The provider page shows your own Slack link. See Slack and Slack app.
  • Questions: Any human member of a workspace can answer an ordinary agent question. Approval of an integration write still needs an operator or an admin. An answer records its channel (web, Slack, CLI, MCP or API) and shows it. See Agent input.
  • Terminal console: A Needs you tab and a right sidebar list the items for the open workspace. You can answer, choose an ask option, approve or reject egress, and act on settings, marketplace and merge requests. The list stays fresh. See The Needs you sidebar.
  • Web app: My work moves to /work. /profile holds account settings, connected apps and Slack accounts, and /me redirects there. Docs and Install CLI are top-level at /docs and /install-cli, and the old URLs redirect. Needs you is the fourth Home panel. Evaluation cases and suites are subpages of Evaluations. The side rail shows counts. Live status moves left of search, and the app groups the account menus. A workspace can no longer use the slugs work, devices, invitations, instance, docs or install-cli. See My work.
  • Webhooks: A group subscription can receive the events of every workspace beneath it. Add --include-descendants to turn it on. See Watching a whole group.
  • Stages: The code and merge stages now wait on the merge request while CI runs. A resumed session gets the outcome of the wait. See Waiting for a merge.
  • Evaluations: A setup records the compiled stage prompt. CodeHerder qualifies the reference solution of a case before it spends anything. It prices an attempt as a whole task run. Only a human admin can create or promote a case. See Evaluations.
  • Integrations: The API refuses to create an oauth2 integration, such as Slack, with POST /v1/workspaces/{id}/integrations. It also refuses a secret on update. Connect Slack with the OAuth flow in the web app.
  • Security: Archived workspaces no longer show in Needs you. list_activity with scope me follows Require SSO.

Changes on 2026-11-08

Versions: v15.101.3 to v15.101.56.

  • Needs you: A pending harness marketplace approval is one Needs you item for an admin, with Approve and Reject. The task page shows the marketplace blocker as an approval card. Block and notice text now points to the buttons on the block or to ch marketplace-approval. See My work.
  • Who acts next: A review wait names the requested reviewers of the pull request or merge request. A viewer who is a listed reviewer sees “You”. On GitHub, the author gets no item. See Who acts next.
  • Blockers: A free-text blocker that names a merge request as “PR N”, “MR N”, “pull request N” or “merge request N” is refused. Use --on-merge-request in its place. See Blockers.
  • Single sign-on: Workspace lists show only identity fields for a workspace that needs SSO, and they mark it “SSO required”. This covers GET /v1/workspaces, the list_workspaces tool, ch workspace list and the web app. The API field is ssoRequired: true, and the CLI status is sso_required. Rows keep kind and parent. Home shows a refused account as one row. The SSO prompt shows only for the account you open. Cross-workspace reads follow Require SSO. See Single sign-on.
  • Jira: jira_create_issue and jira_update_issue redact secrets in labels, free-text custom fields and string-array custom fields. See Agent tools.
  • Devices: Revoking a token on a microVM pool device gets a 409 device_pool_token_refused error. A change to an agent’s device requirements restaffs waiting work at once. A microVM pool instance can download a workspace’s knowledge only when it has a live session there itself. A sibling instance gets a 404 error.
  • Evaluations: An analyst run on a microVM pool device no longer sticks in provision and then fails. This includes the evaluation assessment. The run now binds to one pool instance. When no instance is free, the run stays pending with capacity_constraint. It spends no attempt and no daily start. See The agent-written assessment.
  • Egress: Revoking an egress rule or grant now has the same checks as create. A human work session cannot revoke. A group workspace gets a 409 group_cannot_own_work error.
  • API: A repeated delete of a schedule or an agent config gets a 404 error and makes one event. A repeated watch adds no duplicate activity row. A dev session pages workspace lists without losing next_cursor. A pending environment lock confirm answers 500 when a lookup fails.
  • Wiki: An accepted wiki improvement now gets the same checks as every other wiki write. A body with a credential, a clipped preview, an oversize body or a bad kind is refused with memory_front_matter_invalid. Before, it got a 500 error or was stored. See Workspace wiki.
  • Attachments: A session can delete an embedded image that it uploaded. See Attachments.
  • ch --local: ch --local task blockers --stale now filters. The subscription list query and the persona wiki write for a never-run roster agent now match the server.
  • Security: Log redaction now holds PEM blocks and credential keywords across stream chunks. Writes by the agent user are contained more strictly.
  • Web app: Many table layout and fit fixes.

Changes on 2026-11-07

Versions: v15.91.22 to v15.101.2.

Breaking: My work moved to /me. The workspace route /<slug>/-/me is gone, and it has no redirect. Update your bookmarks to /me. The account sidebar links to it and shows the Needs you badge. See My work.

Breaking: ch agent ask and POST /v1/agents/{id}/questions now refuse a question with no brief. They also refuse an option with no consequence. ch --local refuses both too. A script that files a question must add a brief and a consequence for each option. See Asking a human.

Breaking: The device response no longer has acknowledgedSecretsExpiresAt and acknowledgedSecretsConsentNotice. A server-stored secret no longer needs device acknowledgement or a 90-day consent. A local @secret: reference still needs device permission. A client that read the two fields must stop reading them. See Device secrets.

  • Needs you: A block for a person can carry a structured ask. Use --ask-file with ch task block, ch task blockers create or ch session refuse. ch task blockers choose picks an option. ch task blockers ask <blockerId> --ask-file <path> adds an ask to an open note that has none. Needs you shows only items a person can act on, with one button for each option. An engine park that needs a person now has Resume and Cancel. A timed ask still shows, with “Auto-releases at”. A merge wait held for a review shows a review item. A parent that waits for its children is no longer a stall. The Blockers page marks notes that are stale after 7 days. See Asking a human.
  • Harnesses: mini-swe-agent is a new harness (mini). Devices fetch it. It supports integrations, skills, repo instructions, session events, transcripts and cost. See What mini-swe-agent does differently.
  • Integrations: A write rule can name a workflow and a stage. A Jira deny rule can name one issue with ch integration policy set. Existing rules do not change. The write-rules panel now shows. A Jira write that names an issue by numeric id or by an old key is refused. See Agent access.
  • Jira: New integration tools jira_update_issue and jira_get_edit_fields. New commands ch jira mappings set and ch jira mappings delete. The mapping API takes expectedRevision. A stale revision gets a 409 concurrent_modification error. See Agent tools and Map stages.
  • Profile: A new account-level /profile page. The Profile row in the user menu opens it on every page.
  • Merge: A task that waits for a merge now acts on GitLab conflicts and on failed merge-train pipelines.
  • Devices: The device no longer writes session tokens into the macOS login keychain, and it removes old items. A kept sandbox checks the device requirements again. If a device refuses a task, another device takes it.
  • Schedules: --field now seeds checklist fields correctly. The new --field-file <key>=<path|-> reads a value from a file. The API checks checklist seeds. After ch human revoke-all, a cron fire is refused and the schedule is disabled. See Scheduled tasks.
  • Tasks: A parent move that makes a task wait on its own ancestor gets a 409 waits_on_ancestor error.
  • API: reject and decline on an improvement candidate in the wrong state get a 409 improvement_state_conflict error. PATCH of an archived agent gets a 404 error.
  • CLI: ch session create stops at once when the sandbox is completing.
  • ch --local: The stall verdict, the merge request provenance check and the session rename error now match the server.
  • Evaluations: An attempt whose stage gets no session for 10 minutes now ends as idle_no_session, with the cause named.
  • My work: A work root with no subtasks hides the tree toggle and the bar.

Changes on 2026-11-06

Versions: v15.87.13 to v15.91.21.

Breaking: ch task live is removed, with no alias. Use ch task show <taskId> to see a running task, and ch task show <taskId> --follow to keep reading until it ends. ch task show --json keeps the task in data. The sessions, events, open questions and active blockers are now top-level fields next to data. A script that read .data.sessions from ch task live --json must read .sessions from ch task show --json.

Breaking: Answer a question with ch task questions answer <taskId>. To answer without a terminal, use --from-file <path|-> in place of --answer-file. --question <id> still picks one question when a task has several. ch task questions <taskId> still lists the questions. See When an agent needs your input.

Breaking: A member now changes the primary email address one way only. PATCH /v1/me with email now gives a 400 invalid_input error. POST /v1/me/email-changes/{id}/confirm is removed and gives a 404 error. GET and PATCH /v1/me no longer return pendingEmailChange. The Email row on the profile page is read-only. A script or client that set email through PATCH /v1/me must add the address with POST /v1/me/emails (or ch me emails add), confirm the code, then make it primary. See Email addresses.

  • Messages: ch msg reply <messageId> answers a message. It sends the reply to the sending session, human or agent, and links it to the message. ch msg show now prints a ready-to-run ch msg reply command for every message a member sent. See Messages and your inbox. ch msg send --reply-to <messageId> --from-file <path> with no recipient now takes the same path. Use only the --from-file form, because an inline body reads its first word as the recipient.
  • Sessions: The task page and the session page show the stored transcript for workspaces that turned on stored transcripts. See Read a transcript in the web app.
  • Marketplaces: An approved plugin marketplace now installs its enabled plugins into the session. This also works on a device that confines git, such as the Docker runner or an agent user.
  • Workflows: A task that enters a merge-hold stage after its merge requests already merged now advances. It no longer waits for ever.
  • Devices: After a device server restarts, Docker sessions on the tcp transport, such as Colima, get their git and model relays back.
  • Single sign-on: A SCIM email change and a deprovision now take effect at once for sign-in and Require SSO. One sign-in subject now maps to one member.
  • Self-hosting: The operator command codeherder merge-human-accounts merges a duplicate human account. It is a dry run by default. --apply needs --snapshot <id>.
  • My work: Cancel on a decision card asks for a reason when the workflow needs a comment.
  • Evaluations: A failed hidden check keeps the end of its output as the human-only artifact hidden-check.log. Only a human admin can read an answer key through the evaluation and report routes. A cut evidence line no longer fails the run.
  • Integrations: A comment edit or delete on the host now reaches every mirrored copy, with no cap.
  • ch --local: Several refusals now match the server. They cover stage and workflow content, a question with a run id from another task, a free-text blocker that names an open merge request, and the reopen reason.
  • Security: A git URL that does not parse now counts as holding a secret, so CodeHerder does not store it raw.
  • Web app: The plan badge on a settings card now has space from the card title.

Changes on 2026-11-05

Versions: v15.82.0 to v15.87.12.

Breaking: ch task create and ch task edit no longer take --join-policy. The task setting joinPolicy is retired, and the API ignores it. Every parent now follows one rule. A parent waits for its open children, and it closes when none are open. A parent no longer refuses to close because a child ended in a custom failure stage. If a script passes --join-policy, remove the flag. If you relied on that refusal, check the children’s outcomes before you close the parent.

  • Single sign-on: A workspace can require SSO. A connection has three new settings: Require SSO, the SSO session window (1 to 168 hours, default 24), and SSO-only sign-in. Owners and admins edit them in the Sign-in policy section of the SSO settings. The app asks you to confirm each risky change. With Require SSO on, a member needs a fresh SSO session to use the account. Without one, a request gets a 403 sso_required error and the web app asks the member to sign in with SSO. The rule covers requests, live updates, search, and the lists and feeds that span workspaces. It also covers the device session list. Agents, device tokens and service credentials are exempt. An owner of the account root can still reach the SSO settings to repair the connection. See Single sign-on (SAML and OIDC).
  • Single sign-on: With SSO-only sign-in on, a person whose verified email is on a domain of that connection must sign in through SSO. Any other sign-in gets a 403 sso_sign_in_required error. The web app shows a prompt, and ch prints the ch login --sso hint. Owners of the account root are exempt. Run ch login --sso <provider> to sign in through a connection. ch and the MCP tools show the sign-in address when SSO is required. A revoke-all ends a member’s SSO session.
  • Single sign-on: A connection now trusts the email domains it verified. The identity provider’s own “email verified” flag no longer matters for those domains. A person who signs in through the connection links to the member who has that email. A first-time person joins the connection’s workspace as a member. The join follows the plan’s seat limit. A linked sign-in stops working when the connection no longer verifies the person’s domain. An erase, a deprovision or a reactivation now covers every linked sign-in. See Claiming and verifying a domain and Who can sign in through your connection.
  • Email addresses: A member can add secondary email addresses, up to 20 verified ones. An address belongs to one member across the whole install. Confirm an address with a code. You can make a secondary address your primary one, or remove it. The profile page has an Email addresses section. In the terminal, use ch me emails list|add|confirm|remove|make-primary. SSO sign-in matches a verified secondary address. An invitation reaches a member through any address they hold. See Email addresses.
  • Reports: Velocity, Review debt, Quality and Setup comparison use the same nine range options as Costs. They can look back up to 400 days. See Costs.
  • Workflows: The built-in plan prompt for epics and initiatives now splits work for width. It starts with a small contract task, cuts vertical slices, and keeps dependency chains shallow.
  • Agents: Copying an agent now checks its harness version pin. An out-of-range pin is refused when you copy, not when a session starts.
  • Devices: A device update refuses maxConcurrentSessions above the pool limit, with a 400 error. A device asks the git host for the default branch when its mirror has no branch checked out. This fixes a failed fetch at session start.
  • Sessions: One rule gives the shown session name. A rename wins over a harness title if it is newer. A task-free conversation keeps its name when you resume it. A local session shows its harness title. Setting a standing instruction is refused for a contained session, as rename is.
  • ch --local: A reopen from cancelled or archived posts the stage comment, as the server does. A create that waits on an ancestor task is refused after the other checks.
  • Evaluations: An attempt now ends at a hard limit past its wall time budget, even while it still uses tokens. The manifest field budget.overrunSeconds sets the limit. The default is the wall budget, or two stall windows if that is longer. A virtual machine stays up under a running attempt, and an attempt ends at once when the server ended its launch.
  • MCP: get_task, list_task_children and list_tasks no longer fail when a task has gate violations.
  • Git: A late webhook no longer moves a branch head back to an older commit.
  • Security: The sandbox image moves to apt 3.0.4, which fixes CVE-2026-109518.
  • Web app: Several layout fixes.

Changes on 2026-11-04

Versions: v15.72.0 to v15.81.1.

Breaking: ch task status and the status dropdown no longer move a done, cancelled or archived task. A done task can still go to archived. This applies to every task type. A cancelled initiative or epic no longer offers Move to In progress. If a script moves a finished task with ch task status, change it to ch task reopen <taskId> <stage> --reason-file <f>. The refusal names this command. See Reopening a cancelled or completed task.

Breaking: The device setting CH_TRUST_HARNESS_MARKETPLACES is retired. A device ignores it, and a saved list trusts nothing. A workspace owner or admin now approves each plugin marketplace source under Integrations, Claude, Marketplaces. An admin can adopt a source that an old device list named. Update a device that runs an older version first, or it still refuses. See When a task says “Repo config not trusted”.

  • My work: Needs you lists the decisions on tasks you filed or watch, across your workspaces. You can answer a question, approve or reject an advance, decide a network access request or a settings change, and resolve a blocker in place. View opens a decision card beside the list. Shortcuts j, k, Enter, 1 to 9 and e move through the list. An admin can turn on Show team to see every open task in the workspaces they administer. In flight shows who must act next on each top-level task. Done this week lists work that finished in the last 7 days. See My work.
  • Tasks: The Tasks list shows who must act next on each task. ch task list --blocked lists blocked tasks. The stage select tooltip names who must act.
  • Reopen: A reopen into a working stage waits while an upstream task is open. Reopen at todo instead, or wait for the upstream task. See Reopening a task that has unfinished upstream tasks.
  • Single sign-on: A workspace can connect an OpenID Connect (OIDC) identity provider, such as an Amazon Cognito user pool. Every identity provider, SAML or OIDC, now shows its IdP identifiers. An OIDC connection has an Edit form. See Single sign-on (SAML and OIDC).
  • Marketplaces: A task that needs an unapproved plugin marketplace waits on a blocker. When an admin approves the source, every waiting task restarts on any device.
  • Sessions: You can rename a session in the web app, with ch session rename, and by a click on the session name on the TUI details screen. Every session that has no task now has one name.
  • Terminal console: The console opens your last tabs again when you next run ch. Unselected tabs have a faint outline. See Terminal console.
  • Integrations: You can enable a Slack route only when Slack is connected. Enabling a Jira intake rule again checks the Jira connection. Only a person can unlink a Slack account. A comment edit or delete on the host reaches every task that mirrors it.
  • Access: Only the session operator or a workspace admin can read a session transcript, its execution observations, and its launch guardrails and integrations. Another member cannot. A device health view shows only the workspace you view. CodeHerder removes credential shapes from a harness title that a device reports. ch wiki export refuses to write through a symlink in the destination.
  • ch --local: The local backend gives the brief a child-tasks section and the sandbox note. It sets stalledAt on tasks, groups pending egress requests by purpose, gives a task with no pinned workflow the stage facts of its type, and returns the full session in the stop reply.
  • Evaluations: A sealed attempt uses the mounted harness releases in its inner device server. A glab login that only advises about token storage now counts as clean.
  • Model credentials: The model relay no longer cuts a streamed request body short.

Changes on 2026-11-03

Versions: v15.69.5 to v15.71.64.

Breaking: ch asset download is removed. If a setup script calls it, declare the tool in the stage environment instead. A human workspace admin runs ch env tools add <owner/repo> <version> for a release tool, or ch env system add <package> for a Debian package. See Giving stages the tools they need and PHP stages.

  • Questions: An agent’s question can carry a plain-language brief for a reader with no context. Each option can say what happens if you pick it. ch task questions prints the brief and each consequence. See Agent input.
  • Blockers: A blocker that waits on a question shows the question text as its reason. See Blockers.
  • Tasks: ch task decisions lists the earlier human decisions on a task and its ancestors, newest first. It covers answered questions and approved or rejected stage advances. Each row names the task where you made the decision.
  • Terminal console: The console opens on All, which lists the active sessions of every workspace you can see. Each session shows the folder it works in. A session you cannot attach to no longer appears in the list. When there are more tabs than fit, a N more control lists them all. Drag a tab to move it. See Terminal console.
  • Members: Only an admin of the account root can lift an account-wide disable. Any other admin gets a 403 error and nothing changes. A SCIM reactivation that hits this limit now returns 403, not 500. See Members and teams and SCIM.
  • Attachments: An agent session can read the attachments of its task’s ancestor tasks. It cannot read those of sibling or child tasks, and it can write only to its own task. See Attachments.
  • ch: Evaluation attempt transcripts and device logs no longer print terminal control bytes. --json output stays unchanged.
  • Evaluations: The web app has library pages for evaluation cases, suites and trends. The case page shows the last pass rate and marks an unproven case. The Evaluation page shows the valid-attempt count under its name. See Evaluations.
  • Web app: The live dot shows only for tasks with a running session. A notification rule shows its full recipient list. The page-not-found screen names itself in the breadcrumb and the page title. The navigation flag for unfinished setup now reads “Needs setup”. A long code value in a fact list collapses, with a control to copy it.

Changes on 2026-11-02

Versions: v15.56.20 to v15.69.4.

Breaking: Devices no longer read CH_MAX_WORKTREES. If you set it, set CH_MAX_SESSION_WORKTREES instead. See Devices.

  • Evaluations: You can run an Evaluation on a versioned suite. You can store and publish versioned evaluation suites and cases. You can promote a done task to an evaluation case, and validate a case on an isolated device. You can prove a case solvable with its reference solution. CodeHerder records each case’s run history and regressions. A reference that already holds the hidden patch counts as patched. A case’s answer key stays hidden from reads by anyone who is not a human admin. See Evaluations.
  • Evaluations: A running attempt shows its live wall time, cost, stage sessions and device log state. The attempt and Evaluation pages show the frozen task. The attempt page has a live transcript grouped by stage. An attempt uploads its comments, host events and transcript while it runs. ch evaluation attempt transcript prints an attempt transcript, and --follow keeps it open. CodeHerder retries an attempt when its harness reports no version. A refused suite reference now returns a 400 error. An attempt counts one sandbox for each microVM slot and retries a busy refusal. A sealed attempt no longer shows an ask-the-user dialog from the harness. An attempt fetches Go modules before the hidden check. When the agent changed go.mod or go.sum and broke that fetch, the hidden check fails. See Evaluations.
  • Launch configs: The server now picks the harness, gh and glab versions for each spawn. The default is the newest stable release in range. You can pin one exact harness version with --harness-version <version> on ch agent config create and ch agent config edit, or with harnessVersion on the API. The server checks the pin when you write it, and again when an edit changes the harness. If no stored release matches the pin at spawn, the spawn is refused with harness_release_unresolved. See Agent environments.
  • Transcripts: ch task transcript prints a task transcript. A workspace can opt in to live capture of work-session transcripts, with a retention period. See Session transcripts.
  • Model credentials: The model credential relay is on by default. A run uses a stand-in for a pooled Claude OAuth token, an Anthropic key, Google Vertex tokens and AWS Bedrock keys. The real credential stays on the device. CodeHerder refuses and records a stand-in sent to a host that is not the provider. See AI credentials on a device.
  • Devices: The device collects the conversation titles of Cursor, OpenCode and Pi sessions. The TUI and the web app show harness conversation titles. A session records the launch bundle at spawn. ch --local session show prints it. Stage agents mount Claude Code, Codex, gh and glab from a binary cache on the device. See Devices.
  • ch: ch recovers a launch session from a stale stored token. A --follow command retries after a 499 error instead of ending. A local field write checks the merge reference it adopts.
  • Egress: Go module downloads follow proxy.golang.org redirects to its storage bucket. See Egress approvals.
  • Security: The server refuses more environment keys that can hijack an exec. It refuses duplicate JSON keys in integration relay bodies. A member who cannot read an agent’s questions now gets a 403 error. A webhook delivery that panics goes to the dead letter list at its attempt cap.
  • Blockers and messages: A blocker names its task once, and the command stays runnable. A blocker direct message shows its reason as wrapping prose. A stalled-children blocker gives its wait in plain units. Message previews no longer show a name ID. Activity excerpts of comments, blockers and questions are quoted plain text. See Blockers.
  • Web app: A page that you cannot create shows a back button. You can promote a task, validate a case and pick a suite in New Evaluation. Long session notes collapse behind a Show more toggle. Empty header-only panels fold into one row of chips. Task lists and tables show names, not raw IDs, and show “Unknown member” for a missing actor. Improvement runs list newest first. An integration that is not connected says what it does. The environments status matrix labels stages that come from the library. We also fixed layout, colour contrast, phone widths and empty states, and made filters, buttons, status pills and tables look the same.

Changes on 2026-11-01

Versions: v15.55.26 to v15.56.19.

  • Merge waits: CodeHerder now settles a merge wait as soon as it records that a merge request moved. Before, it settled at the next periodic check. A task that shows a merged-while-blocked flag has a third state, “the merge wait is resolving”. See Waiting for a merge.
  • Evaluations: You can stop a running attempt from its session page or with ch session stop. The attempt starts again at once, and the stop does not count as a loss. ch evaluation attempt show prints the live stage, the quiet time and the last progress of a running attempt. A failed attempt now keeps its evidence, transcripts and logs, and shows the device error. The attempt terminal fills the pane and shows earlier output. See Evaluations.
  • Evaluations: Attempts are more robust. An attempt waits for a usable credential when its AI subscription is spent. An attempt survives an update of the device server. CodeHerder ends an attempt only when it hears nothing from it for a while, not at a fixed time. An attempt that runs past its time budget keeps going while it still makes progress. See Evaluations.
  • Devices: ch no longer starts the device server from inside a sandbox. On macOS, ch starts the device server as a login service for your user. See Running the device server as a service.
  • ch --local: A refusal now carries the same Retry-After value as the server. A subscription is checked for a replay before its cap. A cap refusal records a member.cap_tripped event, as the server does. See Local tasks.
  • Wiki: Archiving a page that is already archived is refused. The refusal no longer uses a write from your budget.
  • Web app: Deleting an account-wide item asks you to type its name. This covers an SSO connection, a GitHub installation and an integration. An error message now names the action that failed. HTML file attachments open in the preview. See Attachments. The acceptance checklist editor has a proof stage picker for each item. Toggle buttons show a pressed state. A stored background failure shows in one standard form, with its time. A live task shows as a green ring dot, and the list rail is gone. The Live item in the top bar reads as a status, and refresh has its own control. Budget text calls the money limit a spend cap. Many layout and contrast fixes.
  • Stages: A stage no longer stalls on the Claude folder-trust dialog.

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