What Claude Code can do
The exact set of actions unpitch exposes to Claude Code, and why the list is closed.
Claude Code can do eleven things in your workspace and nothing else. The list is closed on purpose: adding to it takes a product decision and its own security review, so an agent cannot discover a capability that was never meant to exist.
Reading
See your workspace. Which workspace the connection is bound to, what your plan includes, how many credits you hold, and how much room is left in the current spend window. Ask for it when you want to know what a run will cost before starting one.
Search your business context. A small, relevant set of excerpts from your Knowledge Base, each carrying where it came from. Not a dump — it answers a question rather than handing over the file.
List and open documents. A page of documents with their titles, types and revisions, and the full content of any one of them.
List your personas. The buyer segments you can simulate against, and whether each one is supported by research evidence.
Check on a run. The status of a Quality Check or Simulation, and its result once it finishes.
Writing
Create a document. One typed document saved in your workspace, exactly as if you had created it in the editor.
Update a document. A revision-checked edit. If the document changed in the browser since Claude Code last read it, the edit is refused with a conflict instead of overwriting your newer work.
Those two are the only things Claude Code writes.
Running
Quality Check. Starts on an exact revision and returns a run you can poll. If your included allowance covers it, it just runs.
Simulation. Two steps, deliberately. Claude Code first asks for a quote — a five-minute, non-spending price for that exact document revision and persona. Nothing is charged until the quote is confirmed, and confirming is a separate action you approve in the client.
See Credits and limits for what each one costs and what stops a run.
Why it stops there
There is no general-purpose action — no arbitrary query, no prompt passthrough, no "run this workflow". Claude Code already writes well; what it lacks is your business context and an honest reader. Those are the two things unpitch supplies, and the boundary is where the value is.