On this page

In the twelve days since our last note, we shipped to production more than 100 times. Here are the highlights.

πŸ€– Agents: run your software lifecycle with autonomous agents#

DevStride can now orchestrate fully autonomous software delivery. AI agents plan, build, review, test and release your work from start to finish, and you can watch every step. The new Agents entry in the side menu is where you follow them.

  • Live status on the Fleet: every agent session that is running now, what it is working on, and whether it is Working, Waiting on a person, Stalled or Stopped. Any member's Claude Code sessions appear, and you can rename a session from the page.
  • Stepwise workflows: Workflows draws the workflow each agent follows as phases and steps, with a marker on the step each agent is on. Open a run to see every step's result, evidence and links, such as its pull request and commit.
  • Past runs: check afterwards whether each run did every step its workflow requires, marked Complete, Incomplete or Cannot tell.
  • Agent logging: the Log records every change in a session's health and who was told. Whoever launched an agent hears once if it stalls or stops while it holds work.
  • A step timeline on every work item, at the top of its Agent Sessions tab.
  • No two agents build the same thing: each story is claimed by one agent, and a crashed session's work is freed within about three minutes.

Step reports are short summaries, never transcripts, and secrets are removed before anything is stored. Connecting a tool is easier too: Connect AI is now a five-step guided flow for all eight supported tools. The DevStride Claude Code plugin shipped 32 releases, from 3.46 to 4.7; step reporting needs 4.1 or later.

πŸ“š Agents Overview Β· Connect AI & the MCP Server Β· The Delivery Loop Β· Plugin updates

πŸ“š Documentation that writes and publishes itself#

When you deliver with the DevStride Claude Code plugin, your documentation keeps up on its own: at every release, the plugin works out what shipped and updates the pages that describe it. Your Knowledge Base can then publish those pages as a public documentation site, so what you ship is documented and online without a separate docs project.

DevStride's own documentation already works this way. devstride.docs.devstride.com is built and published from our Knowledge Base and updated at every release, and the old docs address forwards there.

  • Your own documentation sites: admins can turn any top-level Knowledge Base section into a public site, one per product, and switch it on, rebuild it or delete it themselves.
  • A real docs site: each site has a branded home page, a navigation tree, breadcrumbs, instant search, previous and next links, and redirects so old links keep working.
  • Ask AI can give visitors short answers drawn only from your published pages, with links to them. It is off until you switch it on.
  • Write once, publish twice: share one article onto more than one site and still edit it in one place.

πŸ“š Documentation Sites Β· Documentation hooks

πŸ“ Specs, prototypes and reviews with your clients#

A spec can now go from first idea to signed-off delivery in one place, with your client involved at every step.

  1. Your client drafts the spec on the Specs page of your customer portal, in the categories you open to them.
  2. They attach a working prototype: an example link, a code link, or an uploaded file or zip. Newer versions are kept with a dated history.
  3. DevStride drafts the spec from the prototype. One click reads the prototype and writes a first draft for your team to review, covering purpose, users, screens, data, rules and open questions.
  4. You review it together in the spec's comment threads, moving it through your own stages. A change to a published spec can wait for the client's approval.
  5. The client watches it get built. Every spec shows the progress of its linked work, and the portal shows your client a progress bar and "x of y done".
  6. It stays true to what shipped. Spec checks compare finished work with the spec, track each difference, and tell your client by email. When work is done, send it for client review, and optional reminders chase reviewers who have not answered.

Specs can also carry your own custom fields, and the Specifications table can show prototype links and save views.

πŸ“š Client Spec Drafts Β· Prototypes and Spec Fields Β· Specs and Work Items Β· Spec Checks Β· Client Reviews

❓ Questions in comments#

A question that holds work up no longer gets lost in a thread. Mark the comment that starts a thread as a question and give it an optional need an answer by date. It shows a Question Β· need by badge, and the people on the work are told it was asked: the item's assignee, its creator, the people taking part in it and its watchers. It stays open until the asker or the assignee marks it Answered. Questions work on work items and on Knowledge Base articles.

The new Weekly Look-ahead report in Analyze shows, week by week up to a deadline, the work that is due and the questions to answer, so busy weeks stand out early.

πŸ“š Questions in Comments Β· Weekly Look-ahead

🚫 "Is not" in every filter#

Long lists are easier to cut down when you can say what you don't want. Every list filter can now exclude values: "Status is not Done, Cancelled" or "Team is not Platform". Flip the Is not switch at the bottom of the picker, or press I. It works on custom fields too, where you can also include items with no value. Date and time-spent filters gain not in range, and Parent is not under leaves out a whole branch. In Advanced Filters, a group can be set to None of. Exclusions save with your views and travel in shared links.

πŸ“š Finding & Filtering Items Β· Finding & Filtering Tickets

πŸ”Ž Search finds comments, custom fields and attachments#

Cmd/Ctrl+K now looks deeper. It finds an item when your words appear only in one of its comments or replies, in a custom field value (a customer reference, or a dropdown choice like "Platinum tier"), in a ticket's customer description, or in the name of a file attached to it. Each result says where it matched and highlights the words. A comment match opens the item at that comment, and an attachment match opens its Assets tab. You only ever find items you can open.

πŸ“š Search & Recent Places

πŸ“ˆ Progress from the lowest-level work#

Progress can now count the work that actually gets done, however deep it sits. Take a Feature with three Epics, each with three Stories. Two Stories are done under every Epic, so no Epic is finished yet. Counting direct children, the Feature shows 0%. With Progress from Lowest-Level Work switched on, it shows 67%, because 6 of its 9 Stories are done.

Find the switch in the Options menu on the Gantt, Manage Items, a board's Table view and the Map. It also appears in the Progress window and the item drawer's progress donut. It works for item count, points and hours, and is saved with your view.

πŸ“š Items options Β· Gantt Charts Toolbar

✨ And plenty more#

Service Desk#

  • Request forms per company: offer a form on chosen companies' portals only.
  • Add requesters from the Requesters tab, and find closed tickets with the inbox's Open only switch.
  • Link a ticket to the roadmap work it asked for, and the customer can be told when that work ships.
  • Your own support mailboxes can be listed so mail from them is treated as staff mail, not as a customer.
  • Delivery status on replies: each emailed reply shows whether the customer's mail server accepted it, delayed it or refused it.
  • Release held email one message at a time or several at once.
  • Forwarded mail gets through: mail your customers forward from Microsoft 365 or Google Workspace is no longer held by mistake.
  • Answer from your inbox: replying to a ticket notification email adds your reply to the ticket.
  • Share new ticket files with the customer by default with a new organization setting.
  • Client reviews: an automation can run when work is sent for review or has waited a set number of days. The review list shows who each review went to and how long it has waited.
  • Converted tickets open on the Internal description, so nobody works from the customer's wording by accident.
  • Late DNS still verifies: a sending domain whose DNS records were added late can now verify.

Planning, boards and reports#

  • Faster large boards: large boards and roadmaps stay quick on long sessions and use far less memory.
  • Edge scrolling everywhere: every drag-and-drop list scrolls when you drag near its top or bottom, and Manage Columns can move several columns at once.
  • Shareable Gantt links: Gantt addresses name the open chart and view, so links can be shared, and Back returns to the chart you came from.
  • Hierarchy context: the items hierarchy can show filter matches under their parents, with non-matching parents dimmed for context.
  • Weeks layout: User Time Tracking adds a Weeks layout that highlights weeks with too few or too many hours.
  • Grouped exports: exports can be grouped with a heading per group and can carry "Rolls up to" columns.
  • Burndown: choose the rate the projection uses and compare two finish dates.
  • Automations: an automation can change the status of the parent item.
  • Templates: sub-tasks can be dragged into order or sorted A to Z.
  • Bulk edit: change the status of items that are on no board.
  • Saved views stay saved: views no longer show unsaved changes when nothing changed.

Look and feel#

  • Glow UI: every theme is easier to read, and solid buttons, badges and icons share one gradient and a soft glow on hover.
  • Portal sign-in: the customer portal's sign-in page has a new split layout carrying your logo and brand colour.
  • Change your own password from Settings β†’ Profile. Passwords can now contain spaces, accents and symbols.

Fixes#

  • Advanced Filters: views with Advanced Filters no longer show items that don't match them.
  • Gantt filters: they now apply to every level of the chart.
  • Time Allocation Matrix: exports open in Excel again, and rows sort A to Z.
  • Decimal hours: typing 1.5 saves 1h 30m.
  • Moving items between boards: a moved item keeps a sensible status.
  • Date-range filters: the first and last days stay in the range in every time zone.
  • Azure DevOps: two-way sync stays in agreement when an Azure DevOps rule changes a field or refuses a move.
Powered by DevStride