list_env_vars
Read-only
List a project’s environment variables (direct config — no setup agent).
Includes vars requested by auto-detect (pending) and vars with stored values.
Values are masked unless show_values=true; use has_stored_value to tell a
masked value apart from an unset pending var. Use this to see what env the
project needs, then set_env_var to fill it in.
UUID
required
Project UUID.
boolean
default:"False"
Reveal actual values instead of masking them.
set_env_var
Create or update a project environment variable directly (upserts by name).
This is the direct-config path: the user’s own AI sets env from the local
repo/.env it already has, rather than puppeteering Autonomy’s setup agent.
Pass is_secret=true for credentials — API keys, tokens, passwords, connection
strings that carry a password. When importing a whole .env, classify per
variable rather than marking everything: plaintext config stays revealable and
editable, which is what you want for NODE_ENV or PORT.
UUID
required
Project UUID.
string
required
Env var name (letters, digits, underscore; must not start with a digit).
string
required
Value to store for the variable.
string
Optional human description of what the variable is for.
boolean
default:"False"
Store as a write-once secret: the value is never returned by the API again and never inlined into a later prompt. One-way — a variable cannot be un-secreted.
delete_env_var
Delete a project environment variable by name.
Removes both the stored value and any auto-detect ‘pending’ request for it.
Use list_env_vars to see current names first.
UUID
required
Project UUID.
string
required
Name of the env var to delete.
get_setup_config
Read-only
Get the workspace’s setup commands (install / validate / dev) and their status.
UUID
required
Project UUID.
UUID
required
Workspace UUID.
update_setup_config
Set the workspace’s install / validate / dev commands for setup.
UUID
required
Project UUID.
UUID
required
Workspace UUID.
string
required
Install command, e.g. ‘npm install’.
string
required
Validate command, e.g. ‘npx tsc —noEmit’.
string
default:""
Dev server command, e.g. ‘npm run dev’. Optional.
string
default:""
Dev server URL, e.g. ‘http://localhost:5173’. Optional.
get_setup_preview_status
Live status of the workspace dev server (is it listening, preview URL).
Starts the dev server when neither it nor the preview proxy is listening.
UUID
required
Project UUID.
UUID
required
Workspace UUID.
run_setup_validation
Validate the project’s configured setup in a fresh sandbox.
Runs the workspace’s saved install + validate commands (set via
update_setup_config) on a clean sandbox to confirm they work. Runs in the
background (install takes minutes) — returns immediately with state=running;
poll get_setup_validation_status until state is completed/error. Only the
saved commands run — no arbitrary execution.
UUID
required
Project UUID.
UUID
required
Workspace UUID.
get_setup_validation_status
Read-only
Poll the result of run_setup_validation.
Returns state (idle/running/completed/error) and, when completed,
success + install_success + validate_success + per-step results. Read the
steps’ output to see why install/validate failed.
UUID
required
Project UUID.
UUID
required
Workspace UUID.
int
default:"0"
Character offset into the response for paging large payloads; use next_offset from the previous call.
open_setup_chat
Open (create-or-get) the workspace’s setup chat task.
Project initialization creates this task itself when auto-detect needs a
human decision - an init stuck INITIALIZING / NEEDS_ACTION is usually
waiting on a card here. Returns its task_id: read the pending card with
get_task_messages (look for a PENDING setup card and its
deferred_tool_call_id), then reply with reply_setup_approval or
send_setup_message. Requires an admin-level user.
UUID
required
Project UUID.
UUID
required
Workspace UUID.
send_setup_message
Send a message to the project’s setup chat (the agent-driven setup path).
The setup agent detects install/validate/dev commands and env vars by
working in the sandbox; it pauses on confirm cards - see open_setup_chat
for the read/reply loop. Requires an admin-level user.
UUID
required
Project UUID.
UUID
required
Workspace UUID.
string
required
Plain chat message to the setup agent.
reply_setup_approval
Answer a pending setup-chat card (approve/reject a save, or answer a
question) - the setup counterpart of approve_task_tool_call.
Use for the save_setup_commands / save_project_files / manage_env_vars
confirm cards and ask_user_question cards that pause project setup -
including the one project initialization itself waits on. Only accept on
the user’s behalf when they’ve seen what is being approved. Requires an
admin-level user.
UUID
required
Project UUID.
UUID
required
Workspace UUID.
string
required
deferred_tool_call_id of the PENDING setup card (from get_task_messages on the setup task).
string
required
Approve or reject the card.
string
default:""
Free-form answer for a question card.
object
Env var values a question card asked you to fill in.
string
default:""
Why, when decision=‘reject’.