Plugin updates
Every release of the DevStride Claude Code plugin, newest first, and what each one changes for your team.
On this page
- November 2026
- 4.1.0 — 2026-11-17
- 3.62.0 — 2026-11-13
- 3.61.1 — 2026-11-13
- 3.61.0 — 2026-11-13
- 3.60.0 — 2026-11-13
- 3.50.0 — 2026-11-10
- 3.49.0 — 2026-11-09
- 3.48.0 — 2026-11-09
- 3.47.0 — 2026-11-09
- 3.46.0 — 2026-11-09
- 3.45.0 — 2026-11-09
- 3.44.3 — 2026-11-08
- 3.44.2 — 2026-11-08
- 3.44.1 — 2026-11-08
- 3.44.0 — 2026-11-08
- 3.43.0 — 2026-11-08
- 3.42.0 — 2026-11-08
- 3.41.0 — 2026-11-08
- 3.40.0 — 2026-11-08
- 3.39.0 — 2026-11-08
- 3.38.0 — 2026-11-08
- 3.37.0 — 2026-11-07
- 3.36.0 — 2026-11-07
- 3.35.0 — 2026-11-07
- 3.34.0 — 2026-11-07
- 3.33.0 — 2026-11-07
- 3.32.0 — 2026-11-07
- 3.31.0 — 2026-11-05
- 3.30.0 — 2026-11-05
- 3.29.0 — 2026-11-04
- 3.28.0 — 2026-11-04
- 3.27.0 — 2026-11-04
- 3.26.0 — 2026-11-04
- 3.25.0 — 2026-11-04
- 3.24.0 — 2026-11-04
- 3.23.1 — 2026-11-03
- 3.23.0 — 2026-11-03
- 3.22.0 — 2026-11-03
- 3.21.0 — 2026-11-03
- 3.20.0 — 2026-11-02
- 3.19.0 — 2026-11-02
- 3.18.1 — 2026-11-02
- 3.18.0 — 2026-11-01
- October 2026
- September 2026
- August 2026
- 3.2.0 — 2026-08-29
- 3.1.1 — 2026-08-29
- 3.1.0 — 2026-08-29
- 3.0.0 — 2026-08-29
- 2.8.0 — 2026-08-28
- 2.6.0 — 2026-08-28
- 2.5.0 — 2026-08-27
- 2.4.0 — 2026-08-27
- 2.3.0 — 2026-08-27
- 2.2.0 — 2026-08-27
- 2.1.0 — 2026-08-27
- 2.0.0 — 2026-08-26
- 1.2.0 — 2026-08-26
- 1.1.0 — 2026-08-26
- 1.0.0 — 2026-08-26
- 0.10.0 — 2026-08-25
- 0.9.0 — 2026-08-18
- 0.8.1 — 2026-08-18
- 0.8.0 — 2026-08-18
- 0.7.0 — 2026-08-18
- 0.6.0 — 2026-08-17
- 0.5.0 — 2026-08-17
- 0.4.3 — 2026-08-17
- 0.4.2 — 2026-08-17
- 0.4.1 — 2026-08-17
- 0.4.0 — 2026-08-17
- 0.3.4 — 2026-08-17
- 0.3.3 — 2026-08-17
- 0.3.2 — 2026-08-17
- 0.3.1 — 2026-08-17
- 0.3.0 — 2026-08-17
- 0.2.0 — 2026-08-17
- 0.1.0 — 2026-08-17
This page lists every release of the devstride Claude Code plugin, newest first, in plain terms: what you can now do, and what changed that you would notice. Releases that need you to act carry a warning.
To update, run /devstride:update, then /reload-plugins. To have Claude Code update the plugin for you, or to update by hand, see Staying in sync.
The full technical changelog is in CHANGELOG.md in the plugin's repository.
November 2026#
4.1.0 — 2026-11-17#
- Each step of the Build workflow is reported to DevStride's Agents module, on by default.
build-itemsays at each step which step it is on and how the last one ended: a one-line result, a few lines of evidence and its links, never session text, a prompt or a file's contents. Where DevStride cannot take a report, the plugin stops sending for that run without saying anything, and the work carries on exactly as before. - Switch it off for a repository with
"workflows": nullin.claude/ds-config.json, or for one machine withDEVSTRIDE_WORKFLOWS=0. A repository with its own store can name a report command instead. See Workflow step reports. - The Build workflow now ships as a written list of four phases and thirteen named steps. It describes what
build-itemalready does; nothing about how the loop runs changes.
3.62.0 — 2026-11-13#
- Setup asks which board each kind of item goes on.
/devstride:setup boards(a full/devstride:setuprun asks too, when no rules are set) reads your organization's work types and boards and asks where each leaf type and your release unit go: one long-lived board, or a folder of dated cycle boards, where the loop uses the board whose dates cover the day the work starts. Work that belongs elsewhere, by team, tag, a custom field's value or the part of the plan it sits under, is one more rule ahead of the rest. The answer is saved as an ordered list inboardPlacement.rules, first match wins, only after you type yes to the plan it shows./devstride:setup boards personalkeeps your own exceptions in a file outside the repository, read before the team's. - Work is placed when it starts.
build-itemputs each item it picks up, and that item's release unit, on the board the rules name before it moves the item's status.create-storyandcreate-defecttake a one-off's board from the rules instead of asking. An item already on another board stays there, nothing is ever taken off a board, and a board that cannot be found is one line in the progress table, never a stop. /devstride:doctor agentschecks the rules without writing anything: boards or folders that are gone, a cycle folder with no board for today or for the next cycle, names your organization does not have, kinds of item no rule covers, rules an earlier catch-all always beats, and personal rules in effect or ignored.- With no
boardPlacementblock nothing changes. See Board placement.
3.61.1 — 2026-11-13#
- Fixed: a session whose person presses Esc while the model is still thinking, before any reply text appears, now shows as waiting for its person within seconds. Before, it kept reporting as working and a health check could later mark it stalled.
3.61.0 — 2026-11-13#
- New
release.clearance.scopevalue,"merge-and-deploy": a release holds clearance only while it merges into production and deploys. Releases queue first cut, first merged: the next release is cut the moment the one ahead merges, built on top of it, and checked, reviewed and tested while the one ahead deploys. If production moves before it merges (the release ahead was reverted, a hotfix landed), it is rebuilt and tested again. It hands clearance back as soon as its deploy is confirmed and runs its post-deploy check first, so the release behind can merge as soon as this one is healthy. It needsrelease.releaseBranchPattern. See Release clearance. - New
preShipChecks[].rerunAtMerge: a release-only check whose result can lapse while a release waits, such as a sign-in, runs again just before the merge undermerge-and-deploy. - New
releaseTrain.reviewEveryLanding: every one-off gets its own Claude and local CLI review, sized to the change, before it lands on the release train, proven by adevstride/landing-reviewedstatus on GitHub. The train's pull request then lists those reviews as its Review evidence and needs only CI, plus a short review of anything without one. See Release train. - With
release.autoStart.enabled,build-itemnow looks for a release to start at every story boundary and when its loop starts, and a release that levels the train after its deploy starts the next release itself when work is waiting. - A repository with no post-deploy check never holds the next release: under
cut-to-deployandmerge-and-deploythe release posts a successfulrelease/post-deploystatus saying no check is configured. - The release backstop, under
cut-to-deployandmerge-and-deploy, no longer counts an open release pull request or held clearance as a release in progress; only therelease-trainclaim does.
3.60.0 — 2026-11-13#
- Fixed: stories, defects and epics created under a plan no longer land on the Active Agents board beside it.
plan,insert-story,insert-defect,rebalance,create-storyandcreate-defectnever copy a board from the parent: a planned or inserted item gets a board only when you name one, and a one-off is offered every board except the Active Agents board, which only the build loop fills, with plans. Items already on the board are not moved;/devstride:doctor agentsstill lists the ones it finds there.
3.50.0 — 2026-11-10#
- Link planned work to the Service Desk ticket it came from. Pass
--ticket <ticket number>(several separated by commas) to/devstride:plan,/devstride:create-story,/devstride:create-defect,/devstride:insert-storyor/devstride:insert-defect. The skill checks each number is a Service Desk ticket, then links it to the item it creates;/devstride:planlinks the item it plans under once you confirm the plan's shape. A number that isn't a ticket is named and skipped, and a ticket is never mistaken for the parent item. /devstride:comprehend-planlists the tickets linked to a plan, with each ticket's status and the item it is linked to.- Until your DevStride workspace supports the originating-ticket link, the skills say so once and carry on without it.
3.49.0 — 2026-11-09#
- The default delivery profile is now
extended(it wasstandard). This only affects a repository whose.claude/ds-config.jsonhas noprofilekey. Its next plan is cut into larger stories, about a day of release-unit work each. One-off items, and plans without aDelivery profile:marker, build and review atextended's sizes. Safety checks and review floors don't change. An explicitprofile, a plan'sDelivery profile:marker and plans already sliced are untouched. - Plans get soft shape targets: how many stories an epic and how many epics a capability usually hold at each profile (
prototype2–4 and 2–4,standard3–8 and 3–7,extended2–5 and 3–7)./devstride:planquotes them when it proposes stories, and asks once before keeping an epic above its range. Its final review and/devstride:rebalancereport how the plan's shape compares. Nothing blocks a plan for missing a range. - Setup offers
extendedfirst. Doctor reports a missing key asprofile: extended — key absent, shipped default.
No profile key? Your default changed
If your repository's
.claude/ds-config.jsonhas noprofilekey and you want to keep the previous, finer grain, add"profile": "standard"before your next plan.
3.48.0 — 2026-11-09#
- The status line names the session. A new Session segment (☻) on the second line, right after the plugin version, shows this session's name, so terminals side by side say which agent is which. It uses the name Claude Code reports (a session started with
--nameor renamed), else the first line of your repository's ownsession.nameCommand, run from the repository root withCLAUDE_CODE_SESSION_IDset. The command's answer is cached for about 10 seconds, so a new session's first draw can lack the segment for a moment. Hide it withstatusLine.hiddenSegments: ["session"]. - The release clearance records the holder's session name, and
statusshows it as "held by <user> on <machine> (session <name>)". It is for display only: who holds the clearance is decided as before. - Installed status lines are brought up to date at your next session start.
3.47.0 — 2026-11-09#
- The merge gate now reads your pull request's checks last, just before it gives its verdict. GitHub does not re-check required checks when an approver merges with admin rights, so a check that turned red while the gate was still reading other settings could be missed. That window drops from about two seconds to a single request. It is smaller, not gone: only GitHub enforcing the checks at merge time (auto-merge or a merge queue) closes it fully.
- If the pull request changes while the gate is reading it (a new push, a review asking for changes, a different merge state), the gate reads everything again, and refuses with "run the gate again once it settles" if it keeps changing. Nothing to do.
3.46.0 — 2026-11-09#
- Honest estimates of when work will be live. Before work has landed on the release train (for an epic, before its release pull request merges), the plugin never gives a clock time or a duration; it tells you which steps remain. Once work has landed,
estimate.py quotegives a range with a confidence, for example "live between 12:45 PM and 4:45 PM CST, 8 in 10 chance". The range is measured from your repository's own last 14 days of history, so it includes the waits for the next release, test reruns and your go-ahead. With too little history it gives no range rather than a guess. - Every quote is recorded on the item as a comment, and when the release is confirmed live each quote is scored as inside the range, early or late. Run
estimate.py backtestto replay the method over recent history and see how many quotes would have been right; the target is 8 in 10. - New setting
release.estimates.deployMinutes(default 0): the minutes from the production merge until the change is live, added to every range.
3.45.0 — 2026-11-09#
- New, off by default: a release backstop for work that has waited too long on the release train. Releases still start whenever work is ready; this only catches work left waiting, for example overnight or when no session is running. Set
release.backstop.maxWaitMinutes(15 to 1440, default 120) andrelease.backstop.mode. Run/devstride:release backstopon a schedule. It starts a release only when the oldest waiting work is older than the limit, no release is in progress and no release hold applies, and at most once per window across all your machines. - Start with
mode: shadow, which records what it would have started and changes nothing. Switch toliveonce those records look right. The backstop needs aclaimsblock with agetcommand;/devstride:doctorreports one that is missing.
3.44.3 — 2026-11-08#
- Fixed: with release clearance, a release no longer fails at its hand-back or heartbeat when the session's own keeper updates the clearance at the same moment. The plugin now waits a few seconds and retries before reporting a conflict.
3.44.2 — 2026-11-08#
- Internal reliability and maintenance changes; nothing to do.
3.44.1 — 2026-11-08#
- Fixed: a local review engine (
review.localCommandorreview.localAssistCommand) can no longer hang silently waiting for input. Before, a stuck review looked like a slow one.
3.44.0 — 2026-11-08#
- Session presence reports now say when the session last did anything (
PRESENCE_ACTIVE_AT), so your presence command can tell a hung session from a busy one.
3.43.0 — 2026-11-08#
- Story claims, release clearance and presence reports now name the machine and the session the same way everywhere. The machine is
DEVSTRIDE_MACHINE_NAMEwhen set, otherwise the hostname without.local, in lower case. - If your own tooling matches machine names from presence reports or clearance records, expect their spelling to change once.
3.42.0 — 2026-11-08#
- Every running session can report itself, not only those holding a claim. Name a command in the new
presenceblock (presence.command, optionalpresence.intervalMinutes, default 5) and the plugin runs it at session start, on prompts, while Claude waits for you, at session end and on an interval. Without the block nothing changes.
3.41.0 — 2026-11-08#
- Before it merges,
build-itemchecks the final diff for changes that could cost money, remove something callers still use, cut off someone's access or break a published interface. When it finds one, it posts a DevStride comment that @-mentions the item's creator. It is a notice, not a gate. - Configure it with the new
consequenceNoticesblock (enabled,notify,categories)./devstride:doctorchecks it.
3.40.0 — 2026-11-08#
- When a story ships differently from its description,
build-itemnow records the as-built description through DevStride, which also updates every linked Knowledge Base spec, or marks it out of sync. The original description is still kept in a comment.
3.39.0 — 2026-11-08#
- A settled review now leaves a
devstride/reviewedcommit status on GitHub. An epic may carry migrations or deploy configuration onto the release train only when its merged head carries that proof; a branch name alone no longer counts.
Proof must come from an admin
Only a status posted by an account with admin permission on the repository counts. Epics merged from 2026-11-10 (UTC) without proof are checked file by file like any other commit. Update every session before then, and run reviews from an admin account if your epics carry migrations or deploy configuration.
3.38.0 — 2026-11-08#
- One merge gate for every merge: the loop merges only when every required check is green on the exact reviewed commit, with no open review threads or change requests. An admin merge can no longer skip a red check, a conflict, an out-of-date branch or a missing approval.
- A review in which no engine returned a result (a crash, timeout or empty output) now fails instead of settling. One-offs reviewed locally before this release are reviewed again before they land.
3.37.0 — 2026-11-07#
- The owner's written standing yes can now cover full releases (
release.fullRelease). A release at its reviewed head with every gate green merges and deploys without an in-the-moment yes, provided every migration it adds or changes is in the owner'sapprovedMigrationslist. Anything else still asks.
3.36.0 — 2026-11-07#
- Release holds: put
Release hold: not before <date>orRelease hold: after <item> is livein an item's description to keep its work off the release path. Dates userelease.holdTimeZone(default UTC).
3.35.0 — 2026-11-07#
- Run a full local review on its own with
/devstride:review local-full <base>. A one-off over the small-fix limit lands on the release train only when such a review is recorded at exactly its head, and your own landing tooling can run the same check.
3.34.0 — 2026-11-07#
- With
releaseTrain.smallFixesset, a one-off that is not a small fix gets a full local review (Claude plus your CLI engine) before it lands on the release train, instead of waiting for the release's pull request. It adds no CI runs.
3.33.0 — 2026-11-07#
- With release clearance, the time a release waits for the owner's go-ahead is now its own phase (
final), so the stuck alarm no longer counts that wait. - Fixed: a story merged onto an epic, plan or train branch is no longer marked Done before it reaches the base branch.
3.32.0 — 2026-11-07#
- A one-off merged onto the release train now moves to the merged status (
Reviewby default), so the board shows it is waiting for a release. It becomes Done when the release ships it. - Fixed: a release no longer fails trying to start from a train branch that is not on origin. A renamed train is named, with the commands that finish the rename.
3.31.0 — 2026-11-05#
- Fixed: renaming
releaseTrain.branchno longer creates a second, empty train beside the old one. The loop keeps using the existing train and tells you how to finish the rename.
3.30.0 — 2026-11-05#
- Opt-in plan-scope releases: a
Release scope: planline on a plan root collects each epic on a plan integration branch (planIntegrationBranches.pattern) and releases the whole plan together once nothing is left.
3.29.0 — 2026-11-04#
release.autoStart.enabled(with aclaimsblock) lets a train landing or a finished release start the next release automatically, with exactly one session winning.release.lightRelease.standingYesmerges a light release on the owner's standing yes when it is identical to its reviewed tree. Both default to off.
3.28.0 — 2026-11-04#
- A release-only pre-ship check with
runAt: "train"runs on the release-train snapshot before the train merges, and is not repeated later on the same snapshot.
3.27.0 — 2026-11-04#
release.clearance.scope: "cut-to-deploy"holds release clearance only from the cut to a confirmed deploy, so the next release can start sooner. The post-deploy result is posted as arelease/post-deploycommit status, and the next release will not merge until it is green./devstride:release post-deploy onlyfinishes a post-deploy check whose session stopped.
3.26.0 — 2026-11-04#
- The status line is now two lines labelled with symbols: where you are, then what is in flight. It redraws every 30 seconds.
- A running session now hears about a newer plugin: Claude tells you to run
/reload-plugins, or asks whether to run/devstride:update. Turn it off withplugin.updateCheck: false.
3.25.0 — 2026-11-04#
/devstride:setup agentscreates an Active Agents board, tag and shared view in DevStride after your typed yes, and writes theactiveAgentsblock.build-itemthen places each plan root it works on that board and runs yourstartandendcommands./devstride:doctor agentschecks the setup.
3.24.0 — 2026-11-04#
create-story deferred <item#>parks a postponed follow-up in the same container under the plan root as deferred bugs. Deferred items are dated after the plan, and the closing report lists what is still open there.- The default container title is now
Deferred; containers namedDeferred defectsare still found. List other old titles indefects.deferredContainerLegacyTitles.
Everyone on the repository needs 3.24.0
Older versions ignore
defects.deferredContainerLegacyTitlesand look only forDeferred defects. If you set either container key, or rely on the new default, make sure everyone working in the repository is on 3.24.0 or later.
3.23.1 — 2026-11-03#
- Internal reliability and maintenance changes; nothing to do.
3.23.0 — 2026-11-03#
releaseTrain.smallFixes(maxFiles,maxChangedLines): a small one-off on the release train skips its separate review pass. The train's pull request stays the batch's one full review and one CI run.releaseTrain.lateArrivals: "restart"absorbs a one-off that lands while the train's pull request is under review, and reviews the whole snapshot again.
3.22.0 — 2026-11-03#
- The support train is now the release train: the config key is
releaseTrain(supportTrainis still read), and snapshot branches are namedrelease-train-<date>. - A reviewed epic can now carry migrations and infrastructure on the train; only unreviewed work is held to the exclusion paths. New optional keys:
release.migrationRenumberandrelease.devDeployVerification.
Check git and branch rules before updating
This release needs git 2.38 or newer. If your branch rules only admit
*/*/support-train-*, add*/*/release-train-*before you update.
3.21.0 — 2026-11-03#
- Story claims: with a
claimsblock ({ "provider": "devstride" }, or your own commands),build-itemclaims each story before starting it, so two agents on two machines never build the same one. A story another agent holds is skipped. release.clearance.provider: "devstride"keeps release clearance in DevStride instead of a git ref./devstride:doctorchecks both.
3.20.0 — 2026-11-02#
- Ten step skills: each hook the release loop calls (
update-docs,pre-ship,post-deploy,classify-release,pre-merge-checkand others) can be run again on its own by name after a failure. - New optional keys:
docs.knowledgeBaseSyncSkill,release.classifySkill,release.preMergeSkill, andpool.checkoutwithpool.checkin(set both or neither). pre-shipaccepts--skip <name>(an explicit waiver) and--only <names>.
Clearance holder variable renamed
The release clearance holder variable is now
CLEARANCE_HOLDER_TOKEN;DEVSTRIDE_LEASE_TOKENstill works. If your repository has its own tooling that works out the clearance holder, such as a merge guard, update it to read the new name first.
3.19.0 — 2026-11-02#
.claude/ds-config.jsonnow has a published JSON Schema./devstride:doctorand setup check your config against it and warn about unknown keys with the key you probably meant. Add a top-level"$schema"for editor completion, and list your own tools' key prefixes inrepoLocalKeys.
3.18.1 — 2026-11-02#
- Internal reliability and maintenance changes; nothing to do.
3.18.0 — 2026-11-01#
/devstride:doctorno longer blocks a/devstride:build-itemin the same session, and finishes every section even when the plugin is behind. Its seven-day CI audit is now opt-in (/devstride:doctor ci --audit).- Fixed: the session-start hook no longer leaves
.claude/statusline.shmodified when your branch already carries the newer copy, and no longer leaves a.bakfile in the work tree. The update check no longer fails withinstalled-payload-mismatch.
Update once by hand from 3.17.0
A machine on 3.17.0 must update once with the native commands:
claude plugin marketplace update devstride, thenclaude plugin update devstride@devstride --scope <scope>(use the id and scopeclaude plugin listshows), then restart sessions.
October 2026#
3.17.0 — 2026-10-31#
- The status line shows when a session runs an older plugin than it could: in red with
/reload-pluginswhen a newer copy is installed, in yellow with/devstride:updatewhen a newer release is published. Hide it with thepluginkey instatusLine.hiddenSegments.
3.16.0 — 2026-10-31#
- With release clearance, a release hands clearance back as soon as the next release could safely start, once the post-deploy check passes. Documentation and release notes finish afterwards, and any work still owed shows in the clearance status.
- Stuck-phase alarm:
release.clearance.phaseBudgetMinutesflags a release whose phase runs past its budget. - A post-deploy check can add a
close-outmode for longer work that nothing else waits on.
3.15.1 — 2026-10-30#
- Fixed: skills use DevStride's current "status" and "workstream" names instead of the retired "lane" and "folder" aliases.
3.15.0 — 2026-10-30#
release.deployApproval: a command that approves a production deploy waiting behind a protected environment or manual gate, so the owner's yes to the release also approves its deploy.
3.14.0 — 2026-10-30#
review.localEffort(initial,followUp,safety) sets the local CLI engine's reasoning effort for each kind of review round.- A one-off that lands on the train after the release took its snapshot can be absorbed into that release on the owner's instruction, with its own full review.
3.13.0 — 2026-10-29#
- Opt-in release economies:
release.productionReviewskips a second full review when the production pull request's tree matches what was already reviewed, checking only high-risk paths.onlyWhenTouchedruns a release-only pre-ship check only when the release touches its paths.release.syncWorkflowwaits for your own production-to-source sync workflow. - Fixed: status-line cached values now expire correctly on Linux machines with the newer
stat.
3.12.0 — 2026-10-19#
- The
enterprisedelivery profile is retired. Three profiles remain:prototype,standardandextended.
enterprise now falls back to standard
A
profileofenterprise, in config or in a plan root'sDelivery profile:line, now runs asstandard. To keep the old rigor, setprofileOverrides(fixFloor: "all-confirmed",storyVerify: "full",maxLocalReviewRounds: 2,understandReaders: 6) plusreview.pollTimeoutMinutes: 20. Run/devstride:rebalance <root> standard(orextended) to rewrite a plan's marker.
3.11.0 — 2026-10-18#
- Release clearance: with
release.clearance({ "provider": "github" }, or your own commands), only one release runs at a time across every machine and person. Others wait and are told who holds it. Hotfixes are never blocked. - The status line gains a Release segment, and
setup cican add arelease-towercheck that orders release pull requests.
3.10.0 — 2026-10-06#
- An epic's stories are marked Done when the epic is released, not when they merge onto its integration branch. Until then they sit in a merged status (
epicIntegrationBranches.mergedStatusName, defaultReview). - A story named by number is never built twice, and a release nobody closed out is finished by the next run.
- Minor review findings are dismissed with a reason instead of being filed as deferred work.
3.9.0 — 2026-10-02#
- Where an item lands (its epic's branch, the train or the base branch) is decided by one script that your own tooling can run and test against.
- Fixed: an epic integration branch created under an older naming is found again, instead of a second one being cut.
3.8.0 — 2026-10-01#
release.releaseBranchPatterncuts each release as its own protected branch, so the source keeps taking merges while the release is reviewed.supportTrain.branchlets one-off work ride a long-lived train branch and ship in batches.- A cloud reviewer can be asked once, at the final head, with
requestPolicy: "final-head".
The release freeze is gone
ci.freezeBaseWhileReleasePrReadyis now ignored. A merge beneath a ready release pull request moves its head and triggers another review round before the owner is asked. Setrelease.releaseBranchPatternto keep merges away from a release in flight.
September 2026#
3.7.0 — 2026-09-28#
- A cloud reviewer can be limited to pull requests into chosen branches with
baseBranches, for example["main"]for a reviewer you pay for per use.
3.6.0 — 2026-09-27#
- New
extendeddelivery profile for coarser, multi-hour stories, with the same safety floors asstandard. - Every loop skill now reads as a goal, its rules and its hard floors instead of a numbered script. What each one guarantees is unchanged; nothing to do.
3.5.1 — 2026-09-11#
- Fixed:
/devstride:updateruns as written, including for project installs across checkouts and worktrees. Project scope is now the recommended install.
Update once by hand from 3.1.0–3.5.0
On 3.1.0 to 3.5.0,
/devstride:updatecan stop withplugin-root-missing. Update once withclaude plugin marketplace update devstride, thenclaude plugin update <id> --scope <scope>(fromclaude plugin list), then reload.
3.5.0 — 2026-09-11#
- Setup and doctor check that your local review engine runs read-only, and fail a command missing its sandbox flag with the exact fix.
codex reviewis now a second supported Codex engine. - Planning and delivery commands can no longer be mixed in one session. Use
--same-session, or setsession.jobClassGate: false, to allow it. - Deferred defects are filed in a container beside the plan (
defects.deferredContainerTitle), andepicIntegrationBranches.autoReleaseaccepts"ask".
3.4.2 — 2026-09-08#
- Recaps of finished work now describe what a person experiences, in plain language, rather than how the code does it.
3.4.1 — 2026-09-03#
- Fixed:
releaseno longer skips the deploy confirmation when a post-deploy check is configured.
3.4.0 — 2026-09-02#
review.mandatoryLensesforces your own review lens onto your own risk paths: each entry names path globs and the question a reviewer must answer for every changed hunk.
3.3.0 — 2026-09-02#
build-itemandreleasefetch first and check what others have landed before acting.- New
release.postDeployCheckSkill: a local skill that checks production after a deploy and can stop a release for a rollback decision.localEnvironment.fetchOnSessionStarttells you at session start when your branch is behind.
August 2026#
3.2.0 — 2026-08-29#
- The local review engine works with any CLI that meets its contract, such as Grok, Gemini, DeepSeek or a local open-weight model. Setup always offers to name another; Codex stays the default.
3.1.1 — 2026-08-29#
- Fixed: status-line values no longer render invisibly on themes where bright black matches the background.
3.1.0 — 2026-08-29#
- New
/devstride:updateupdates the installation in use and verifies it./reload-pluginsusually activates the new version without a restart.
3.0.0 — 2026-08-29#
- Planning and building follow one engineering-economy rule (reuse before building, nothing speculative), with model effort sized to each task. Optional
review.localAssistCommandasks for a second opinion on hard calls. - Routine stories get a bounded risk check, and full adversarial review runs at merge boundaries. CI runs once, last, on the final reviewed head.
review.localReReviewScope now applies to every reviewer
review.localReReviewScopenow sets the follow-up scope for Claude, the local CLI and cloud reviewers alike. If you set it to"full", every reviewer now re-reviews the whole diff.
2.8.0 — 2026-08-28#
/devstride:doctornow offers to fix what it found, after the full report, with one question for the batch.- The session-start hook keeps the repository's status line current; opt out with
statusLine.autoUpdate: false. Record segments that do not apply instatusLine.hiddenSegments.
2.6.0 — 2026-08-28#
- A
stageblock (resolve,productionStages) tells the loop which deployment stage a checkout points at.releasenames it at the production gate, andbranch-hotfixstops before touching a production stage's database. setupcan write the repository a status line.
2.5.0 — 2026-08-27#
- Internal reliability and maintenance changes; nothing to do.
2.4.0 — 2026-08-27#
- Cheaper reviews: a follow-up local review round reads only the fixes (
review.localReReviewScope), and the wait for a cloud reviewer is learned per reviewer (review.adaptiveReviewerWait).
2.3.0 — 2026-08-27#
localEnvironment.recreateModeandlocalEnvironment.instanceNametellbranch-hotfixhow yourrecreatecommand behaves, so a hotfix always ends in a working local instance.
2.2.0 — 2026-08-27#
localEnvironment.recreateletsbranch-hotfixrebuild a local instance from the production base instead of leaving its schema ahead of the code. It stops and asks when there is no safe path.
2.1.0 — 2026-08-27#
- Fixed: doctor and setup now say when a CI "skip identical tree" step is present but cannot fire.
2.0.0 — 2026-08-26#
ci.expectedRunsPerPullRequestnow counts runs per workflow, not across all workflows.- Fixed: the loop recovers from a GitHub stall in which a pull request marked ready starts no CI run.
Check ci.expectedRunsPerPullRequest
If you raised
ci.expectedRunsPerPullRequestto tolerate the old total across workflows, set it back to the runs you expect from each workflow (almost always1).
1.2.0 — 2026-08-26#
- The plugin tells you at session start when a newer version exists. New
pluginblock:updateCheck,autoUpdateandpin. - New
localEnvironmentblock describes how your repository stands up an isolated local instance.
1.1.0 — 2026-08-26#
- New
/devstride:ci-auditmeasures executed CI runs and minutes.setup cioffers CI-cost changes to your workflows and applies only the ones you accept.
1.0.0 — 2026-08-26#
releasenow hands documentation to a local skill in your repository (docs.updateSkill) after the deploy is confirmed. Release notes are opt-in with--release-notes.
Migrate your docs settings
release.docsRepois deprecated andreleaseNotesWhenis retired. Run/devstride:setup docsto migrate.
0.10.0 — 2026-08-25#
- Delivery profiles (
prototype,standard,enterprise) set how much rigor the loop spends on each item, through the newprofileandprofileOverrideskeys. New/devstride:rebalance <root> <profile>re-slices a live plan to another profile.
Default rigor is now standard
A repository with no
profilenow runsstandard, lighter than the single level used before. At the time,"profile": "enterprise"kept the old behaviour; that profile was retired in 3.12.0.
0.9.0 — 2026-08-18#
- Setup and doctor suggest branch roles from the branches that exist on origin (
main,developand similar). - Prompts say "parent item" instead of "container".
0.8.1 — 2026-08-18#
- Internal reliability and maintenance changes; nothing to do.
0.8.0 — 2026-08-18#
- A
dsmarketplace entry lets you install asds@devstride; commands stay/devstride:<skill>. Install one entry or the other, never both. - Fixed: CI draft-gate checks no longer fail repositories whose hold works.
0.7.0 — 2026-08-18#
- New
/devstride:setupinspects your repository, proposes.claude/ds-config.jsonwith the evidence for each value, asks only what it could not settle, then validates the result by running it.
0.6.0 — 2026-08-17#
- New
/devstride:doctor: a read-only check of every loop prerequisite, with the fix for each problem it finds.
0.5.0 — 2026-08-17#
- These config keys now take effect:
itemTagFormat,review.localReviewerName,epicIntegrationBranches.slugRuleandepicIntegrationBranches.releaseTarget.
0.4.3 — 2026-08-17#
- Internal reliability and maintenance changes; nothing to do.
0.4.2 — 2026-08-17#
- Fixed:
ultracode-buildnow readsverify.testSingleto run the touched test suite.
0.4.1 — 2026-08-17#
- Internal reliability and maintenance changes; nothing to do.
0.4.0 — 2026-08-17#
- Fixed six loop defects: pre-ship checks run before a pull request is marked ready,
pushincludes new files, inserted stories are wired into the plan, andrationalize-ganttstops on a dependency cycle.
0.3.4 — 2026-08-17#
- Documentation fixes: the pinning and unpinning recipes now reinstall the plugin, and per-marketplace auto-update is documented.
0.3.3 — 2026-08-17#
- Pinning is simpler: append
@<tag>to the marketplace source.
0.3.2 — 2026-08-17#
- Documentation fix: updating takes
claude plugin marketplace update devstrideandclaude plugin update devstride@devstride, then a restart.
0.3.1 — 2026-08-17#
- Added the changelog and documentation on versioning, updates and pinning.
0.3.0 — 2026-08-17#
- The DevStride MCP server is bundled with the plugin. You sign in once through the browser, and no credential is stored.
Sign in after installing
Run
/mcpafter installing to connect. Until you do, the server adds no tools and nothing prompts you. Signing in grants read and write access to the organization you choose, at your level in the app.
0.2.0 — 2026-08-17#
- The first fifteen delivery-loop skills, run as
/devstride:<name>: planning (plan,comprehend-plan,insert-story,insert-defect,rationalize-gantt) and delivery (build-item,ultracode-build,review,pr,push,branch-feature,branch-hotfix,create-story,create-defect,release).
0.1.0 — 2026-08-17#
- Initial release of the plugin package, with no skills yet.