Stride on Cheezy World

Attach the Screenshot, Not a Description of It

Mon, 09 Nov 2026 06:04:00 -0400

This post covers attachments, new in Stride 3.1.0. Attachments are part of the Organization plan.

Some things are hard to describe in words. “The app crashes when the card has expired” could mean a dozen things. A screenshot of the crash, the device log and the spec it breaks leave no doubt. Until now those files lived somewhere else: a chat thread, a shared drive or someone’s downloads folder. Whoever picked up the task had to go and find them.

From an Idea to a Team That Ships on Its Own: Getting Ready for a Half-Day Stride Session

Sat, 31 Oct 2026 12:33:00 -0400

I now run half-day, hands-on sessions where your team and AI agents build part of your proof of concept together in Stride. The handout below covers the offer. This post is about the parts it can’t fit: what to have in place before the day, why we start with ideation rather than code, and how your team keeps going once we leave.

One Place to Run Your Team's Stride

Sun, 25 Oct 2026 14:44:00 -0400

This post is part of the Stride 3.0.0 announcement.

When a whole company uses Stride, someone needs to look after it: who’s in, which teams have which boards, how people sign in, and what has changed. Until now, every board was managed on its own, by its owner, and nobody could see the whole picture.

Stride 3.0.0 adds Organizations. An Organization brings your people, your workspaces and your security settings together in one place, run by its org-admins.

Sign In Through Your Identity Provider

Sun, 25 Oct 2026 14:33:00 -0400

This post is part of the Stride 3.0.0 announcement. Single sign-on is part of the Organization plan.

Your company already has one place where people sign in: Okta, Microsoft Entra ID, Google Workspace or another identity provider. That’s where new starters get their accounts, where multi-factor authentication is set up, and where access is switched off when someone leaves. Until now, Stride was one more password to manage on the side.

A Workspace for Every Team

Sun, 25 Oct 2026 14:17:00 -0400

This post is part of the Stride 3.0.0 announcement. Workspaces are part of the Organization plan.

Once more than one team uses Stride, the Boards page gets crowded. The mobile team’s release board sits next to marketing’s campaign board and the platform team’s migration. Everyone sees everything they’ve been added to, in one long list, and nobody can tell at a glance which boards belong together.

Stride 3.0.0 adds workspaces. An Organization can have as many as it needs, such as one per team or one per product. Each workspace holds its own boards and has its own people.

Stride 3.0.0: Organizations and the Free Plan

Sun, 25 Oct 2026 14:04:00 -0400

Stride started as a board for one developer and a handful of AI agents. It has grown into the place where whole teams plan work, hand it to agents and review what comes back. Teams have been asking for the things teams need: one place to manage their people, a way to keep each team’s boards together, sign-in through the company’s identity provider, and a record of who changed what.

See Everything Your Board Is Doing

Wed, 14 Oct 2026 15:20:00 -0400

Your Stride board shows you where every card is right now. What it couldn’t easily tell you was how the work has been going:

How many tasks did the agents finish this week?
How long does a task take from the moment an agent claims it to the moment it’s done?
How often does work pass review the first time?
Did anything quietly fail overnight?

Stride now records all of that. Every meaningful thing that happens, such as a task claimed, a review approved, a goal’s hook failing or an API call, sends a small, private telemetry event. You can feed those events into the dashboards, reports and alerts your team already uses, or build new ones around them.

Your Board, Wherever Your Team Talks

Wed, 14 Oct 2026 13:35:00 -0400

A Stride board knows the moment anything happens. A card is picked up, an agent finishes a task, a reviewer approves the work. Until now, though, you only found out if you happened to have the board open. Most teams don’t sit on their board all day. They live in Slack or Discord, and the board was one more tab to check.

Stride can now tell your team about it where they already are. Each board has a new Integrations tab, where the board’s owner can send board activity to:

Busy Boards, Made Manageable

Fri, 09 Oct 2026 06:51:00 -0400

A Stride board with a dozen cards is easy to read at a glance. A board with a hundred is not. Until now, finding something meant scanning every column by eye. There was no way to say “these are all the Android bugs”, and no single place to see everything assigned to you. Tidying up after a planning session meant dragging cards one at a time.

This release adds six things to help with that:

A Stolen Password Is No Longer Enough

Thu, 08 Oct 2026 16:57:00 -0400

Until now, your Stride account was exactly as safe as your password. If your password leaked in someone else’s data breach, if you reused it somewhere, or if you typed it into a convincing fake sign-in page, whoever had it could sign in as you. They could see your boards, change your tasks and create API tokens.

Stride now supports two-factor authentication. Once you turn it on, signing in takes two things: your password, and a six-digit code from an authenticator app on your phone. Someone who has only your password gets no further than the second step.

Comments That Know Who's Talking

Thu, 08 Oct 2026 07:26:00 -0400

A task’s comments are where the real work gets discussed. Someone reproduces the bug, an agent explains what it changed, a reviewer raises a concern, and someone else answers it. Until now, Stride’s comments were a list of notes with a date. They didn’t say who wrote them, you couldn’t fix a typo, and the only way to get someone’s attention was to message them somewhere else.

Comments in Stride are now a proper conversation. Every comment shows who wrote it, human or agent. You can edit or delete your own comments. You can @mention a teammate, and they’re notified in Stride and by email, with a link that takes them straight to your comment. Agents can read and post comments through the API too.

Stride Now Speaks MCP

Wed, 07 Oct 2026 06:50:00 -0400

Coding agents are Stride’s busiest users. They find the next task, claim it, do the work, run your quality checks and hand it back for review. Until now they did all of that by building HTTP requests by hand: shell commands with headers, JSON bodies and careful quoting, assembled fresh every time.

Stride now has a Model Context Protocol (MCP) server. MCP is the open standard that AI tools such as Claude Code use to discover and call external tools. Point an MCP client at Stride and your agent sees a small set of named, documented tools with defined inputs. It no longer has to remember an API. The agent asks for what it needs, and Stride checks the request before acting on it.

A Permanent Record of Who Did What

Tue, 06 Oct 2026 19:27:00 -0400

When something unexpected happens on a Stride instance, such as a run of failed sign-ins, an API token nobody remembers creating, or someone trying to reach a page they shouldn’t, the first question is always the same: what happened, and when? Until now, Stride noted these events in its server logs, which come and go and which administrators can’t search from Stride. Now it keeps them.

Stride has a permanent, append-only audit log of important security events. Entries are only ever added. Once an event is recorded it can’t be edited, and recent entries can’t be deleted. Site administrators can search the log, filter it and export it.

Exploratory Testing Gets Sharper, Safer and Quicker

Tue, 06 Oct 2026 06:22:00 -0400

The Stride exploratory-testing plugin teaches a coding agent to test software the way a good human tester does: give it a mission, let it probe the running app, judge what it sees, and come back with bugs, questions and an honest account of what it didn’t get to. The latest version is the result of a close look at how the plugin actually behaved in real use. This post covers what changed, what that means for you, and how to use the plugin inside the Stride workflow or on its own.

The Stride Plugin Gets Leaner, Faster and Harder to Fool

Mon, 05 Oct 2026 19:25:00 -0400

The Stride plugin for Claude Code is what turns a coding agent into a Stride teammate: it claims tasks, explores the code, implements, sends the work through review and completes it. Over the last few releases we went through that loop measuring where time and tokens actually went and why reviewers kept sending work back. Then we fixed what we found.

None of this changes how you start. You still ask the agent to work a task, a goal or the queue. What changes is what happens next: long sessions stay small, reviews settle in fewer rounds, and the agent gets better at catching its own mistakes before a reviewer, or you, has to.

The Stride API Now Pages, Filters and Describes Itself

Mon, 05 Oct 2026 18:21:00 -0400

Most of the work on a Stride board is done by things that talk to the API: coding agents claiming and completing tasks, scripts that build reports, dashboards that keep an eye on progress. Two changes make that API much easier to build on. You can now page through and filter the task list, and Stride publishes a complete, machine-readable description of its API that tools can read for themselves.

Stride Now Tells You When It Needs You

Sat, 03 Oct 2026 14:13:00 -0400

AI agents don’t keep office hours. They finish work at 2 a.m., on Sunday afternoons, and in the middle of your lunch meeting. Until now, Stride kept quiet about all of it: if an agent finished something that needed your review, it sat in the review queue until you happened to open it. A stalled claim, a finished goal, a delivery date slipping out of reach. All of it waited for you to come and look.