Skip to Content
TurboslideDocumentation
Agents in AgentsContents

Agents

Every command in Turboslide is an action that a program or an AI agent can run, over the command line, MCP, HTTP or an open page.

Turboslide keeps every operation in one table of actions. The menus, the command line, the MCP tools, the HTTP endpoints and the page API all come from that table. As a result, an agent can do anything that a person can do. Each action also checks its input in the same way on every transport.

The four transports

The action reference lists every action with its input fields and its name on each transport.

Rules every agent follows

  • Every action that changes a presentation takes baseRevision, the revision that the agent read. If the presentation changed after that revision, the action is refused with status 409 and the current document. Read the response, then try again once.
  • Every write returns the normalized result. Read the new state from that response. Do not rely on the state that you held before the write.
  • An unknown field is refused with unknown_field and a JSON pointer to the field.
  • A presentation file from a newer release of Turboslide can have a higher schemaVersion. Such a file fails validation with the issue upgrade_pending. A newer release can also add a field under the same schemaVersion. Turboslide keeps that field and writes it back unchanged.
  • On a studio, a write is recorded under the owner of the API key as agent:<tokenId>. There, --author on the command line and the x-turboslide-author header over HTTP only label the run. In a local folder, --author names the author.
  • A claim about a presentation names the revision at which it was checked.

Leases

slide.lease reserves a slide for ten minutes. While another author holds a slide, an agent's write to that slide is refused with 409 and the holder's name. A write that sets force goes through. A person's write to a leased slide goes through with a warning.

API keys

On a hosted studio such as turboslide.com, the HTTP actions and MCP need an API key. Send it as Authorization: Bearer <key>. To get a key, run turboslide login --to https://www.turboslide.com. The command prints a code. Approve the code at /device while you are signed in. The command line then stores the key. The key expires after 90 days. On your own computer, the routes respond on localhost without a key.

An API key acts for the person who approved it, with that person's access to each presentation. Its scopes limit it further. The scopes are read, comment, write, export, share and admin. A key without share reads the ids of other people as stand-ins, the same as a person who may not share. A stand-in is ref_ followed by 22 characters. Comment actions work with a key wherever its owner may comment. The API keys list in your profile shows each key and lets you revoke it.

Skills

Four skills teach an agent how to work with Turboslide. See Skills.