Use Flow in Your Agent

Copy one prompt into Claude Code, Codex, OpenCode, Cursor, or any other coding agent that can fetch a URL. There is nothing to install.

Read https://flow.thymelabs.io/docs/skills/thyme-flow/SKILL.md and follow it to work with Thyme Flow in this project. If you support skills, save that file as a skill named thyme-flow so you can reuse it. Then check that the thyme CLI is installed and which deployment it points at, and tell me what you need me to approve.

The prompt points the agent at the Flow skill: one Markdown file that explains the thyme CLI, from choosing a deployment and signing in to managing functions, executables, profiles, secrets, storage, and logs. An agent that supports skills keeps a copy for later sessions. Any other agent follows the file for the current session, so paste the prompt again when you start a new one.

You can read the skill file before handing it to an agent.

What the agent can do

Area	Covered by the skill
Deployment	Check the resolved API URL with `thyme api-url` and ask before assuming one.
Sign-in	Start a pairing login, show you the code, and wait for your approval.
Tasks	Scaffold with `thyme init` and `thyme new`, write `defineTask`, and run locally with `thyme run`.
Permissions	Write `permissions.json` for the calls a release makes.
Functions	Upload immutable versions with `thyme upload` and find their IDs.
Executables	Create, simulate, run, pause, resume, reschedule, and switch versions.
Secrets and storage	Create and bind write-only secrets; read and replace executable storage.
Monitoring	List executions and read their logs.

All of it runs through the documented CLI and management commands. The skill adds no API of its own.

What still needs you

Login approval. An agent has no browser session. It runs thyme login --browserless, or thyme login --management --browserless for workspace management, and shows you a URL and pairing code. See authentication.
Wallet signatures. Creating a Safe or Roles profile and widening its allowed calls are signed by the owner in Console → Profiles. An API key cannot grant on-chain permissions.
Spending decisions. The skill tells the agent to ask before a real run, a resume, or a deletion, and to prefer a cloud simulation first. thyme executables run can submit transactions and use gas.

Keep credentials out of the conversation

The CLI stores credentials in ~/.thyme/config.json. The skill tells the agent not to print that file, tokens, webhook URLs, or secret values. To avoid storing a login on the machine, export THYME_AUTH_TOKEN yourself before starting the agent; see CI use.

Pass secret values through environment variables you set, so they never appear in the agent's transcript:

thyme secrets create --project PROJECT_ID --key PRICE_API_KEY --value "$PRICE_API_KEY"

Other machine-readable docs

Agents can also read this site directly. llms.txt lists every page, llms-full.txt contains them all, and the management API is described by the OpenAPI document.