- Is this just a wiki with extra steps?
- A wiki waits for somebody to write the page. Steptree writes it from one run-through, with the goal and the judgement calls, and a person approves it. When a screen changes, record the job again and you have a new draft in minutes. And your AI reads it, so the answer to “how do we do this here?” comes from it.
- Who can see an SOP?
- SOPs belong to teams, and access follows team membership. A public link is a choice somebody makes for one SOP. Every workspace's library is separated inside the database itself, not by application code remembering to check.
- Can I read my library in the AI tools I already use?
- Yes, on every plan. Steptree publishes your procedures, skills and recordings over MCP. Claude Code, Codex, Cursor and GitHub Copilot in VS Code each have a setup guide. You mint the token yourself, scoped read-only or read-write, tied to your own membership and expiring on a date you set. Reading your own documents makes no AI call, so it costs nothing and is not gated.
- What format are SOPs stored in?
- Rich documents in the app, which you edit like any other document. Any one can be compiled to SKILL.md: YAML frontmatter and markdown, which downloads as a plain file other AI tools already read.
- Can I write an SOP by hand?
- Yes. Start from a blank SOP and write it in the editor; a blank skill works the same way. Recording is the fast way in, not the only one.
- What happens to my library if I stop paying?
- Nothing is deleted when a paid plan ends. The workspace moves to Free and keeps every SOP, which you can still open, edit and share, and your AI can still read over MCP. Every skill you compiled still downloads as a SKILL.md file. Each person can also download a copy of their own data from Settings, including the SOPs they created. There is no PDF or Word export.