steps
about pricing contact

Sign out?

Sign out of this browser only.

Make this suite public?

Anyone on the internet can view it.

Confirm

Are you sure?

Add workflow

Starts as a draft.

New version

Stays a draft until you activate it.

Move workflow to another suite

Versions stay with the workflow.

Delete

Are you sure? This cannot be undone.

New suite

Private until you publish it. Add workflows next.

Join the waitlist

Sign in

New here? Sign up

Need help signing in? Tell us the email on the account.

Sign up

Already have an account? Sign in

Questions before you join? Tell us what you want to set up.

About

Agents move with speed. Your team stays in control. Steps holds the workflows your team wrote, so the AI you already use doesn’t start from scratch.

How it works

People guide. Your AI follows.

One shared workflow for your team and the AI agents you already use. When judgment is needed, people carry on from the same step.

1 · HUMANS GUIDE Guide the work Define what should happen 2 · UNDER CONTROL Follow your guidance Process you can see and own 3 · SEE & CONTINUE See the next step Same workflow for people and agents Take over when judgment is needed
People guideThey define what should happen on critical work.
Agents followThey stay on the workflow people set.
You can take overThe next step stays visible.

Same workflow

See the next step.

People and agents share the workflow. If an agent stalls, continue from the same step.

steps · Incident response workflow

Incident response

Step 2 of 7 · Decision point

Choose your path

No - P3/P4 low severity
Mitigate & resolveFix or rollback, then post-mortem

Opportunity

Agents can take on critical work

Agents can carry out critical work, not only drafts, when they follow a workflow your team wrote.

People still decide the steps, and everyone can see them.

Unassisted work Agent-assisted work Agents can take on critical work
Agents can take on critical work when people set the workflow.

Constraint

No shared workflow, no real control

If the next step is hidden, people can’t take over when an agent stalls.

A shared workflow is how you continue.

Humans expect control No visibility Agents run blind No guided workflow Takeover fails Unclear next step
Without a shared workflow, takeover is guesswork.

Where Steps fits

AI-native workflows your team writes and your AI follows

Workflows in one place, with context at every step and the next step visible. People take over when judgment is needed, then hand back.

1. Document

Write the workflow so it can be followed and checked.

2. Interact

Branches, discussions and edits keep the same workflow current.

3. Share

One current workflow for your team and its AI.

STEPS WORKFLOWS What should happen Human-guided. Visible. Yours. Humans guide Agents follow Document → interact → share Shared workflow for humans and agents
People author the workflow. Agents follow it. Either side can continue.

One place

Past experience lives in the discussion

The team’s steps stay in one place, and the discussion on a step holds what happened last time: the gotchas and the exceptions. Your AI reads that discussion with the published step. People, and your AI with Can edit, add to the discussion when something is worth noting, not on every run.

Everyone contributes

The whole team can write the workflow

Not only a few people writing prompts. Anyone can record how the work actually runs, on video, in a voice note via your AI, or in the discussion on a step.

Ops Support Engineering More staff… HUMAN Guided process for agent control Your AI follows
Anyone on the team can write how the work runs.

Your stack

Works with the AI you already use

Keep Claude Code, Cursor, Codex or your own setup. Steps doesn’t run your AI. It’s where your team says what should happen.

SOURCE OF TRUTH steps workflows Prioritized context YOUR ORCHESTRATOR Existing or custom-built Runtime, tools, implementation Consume guided steps context Higher-level guidance + your stack
steps says what should happen. Your orchestrator runs it.

Developers

Find the workflow in the context flood

Notes, skills, and plugins compete for attention. A Steps workflow is the one you want followed.

AGENTS.md CLAUDE.md skills/ plugins prompts .cursorrules more context… STEPS WORKFLOW Prioritized workflow What gets work done Context flood Easy to find & follow
A workflow is easier to find than a pile of context files.

Why a workflow

Keep agents moving when automations break

Current automations break.

A brittle script or a one-shot prompt falls over when something changes, or an edge case appears.

A workflow holds the process.

It is an orchestration of small, reusable skills, and the way your team processes the work: the order, the checks, and the decisions.

Write it for the code.

Write the steps for how code is written and structured in this repo, and the order of things to check before changing an API or opening a pull request. Your AI reads the published workflow and follows it.

Agents

Don’t make your AI invent the process.

Cursor, Claude Code, Codex, VS Code, any MCP client or your own orchestrator can read the workflows your team already wrote, and, with your permission, change them, including the current published version.

They follow that workflow instead of inventing one.

YOUR AGENT Cursor · Claude Code · Codex or your orchestrator Your access token Read · edit Same workflow people see STEPS WORKFLOW Human-guided workflow 1. Find — search 2. Confirm — concise details 3. Export — follow steps Agents accelerate the work. You keep the control plane.
The agent reads and updates the same workflow.

What you get

Start from the process

Your AI starts from the process your team defined.

Keep it current

When a decision changes, update the workflow so everyone keeps following the same one.

Stay in control

You still write, publish and share.

Hook in

A token, then find, confirm, and follow

Steps doesn’t run your AI. It guides it. Create a token in Settings, and your assistant looks up the workflow, checks it’s the right one, and follows the steps.

1 · TOKEN Create a token in Settings 2 · AGENT Point it at steps read & author 3 · WORK Ship the workflow people can follow Connect once. Every time your agent opens a workflow, it starts from how your team works.
One token. The agent can read and update workflows.

Connect your AI

Hook up the agent you already use, or open a workflow to see what it will follow.

FAQ

Questions

Short answers. Open a question for the detail.