Built-in tools

Every operation the OS answers for a task itself, with its inputs, effects, gates, retry safety and errors.

Generated from the built-in tools registry. Do not edit by hand.

A task calls two kinds of tool. Vendor tools come from the MCP servers an enterprise binds on the Tools page: GitHub, Slack, Sentry and the rest. Built-in tools are answered by the OS itself: os.*, workspace.*, memory.* and web.*, the CEO chat’s own tools, and the verbs of a Computer-Use binding.

This reference lists every built-in tool. It is generated from the same definitions the model is served, so what you read here is what a run sees.

Declaring a tool

A task can call only the tools it declares, by exact name, in its tools:

{
  "tools": [
    "workspace.read_file",
    "workspace.edit",
    "workspace.git_commit",
    "os.set_execution_name"
  ]
}
  • A name in a built-in namespace (os., workspace., memory., web.) that is not listed here is refused when the task is saved (tool_unknown). So is a tool only the CEO chat offers (tool_not_run_callable): a run never answers one.
  • A task can pin a field to particular values: <tool>#<field>=<value>,<value>. The model is offered only those values, and a call carrying any other is refused.
  • The model calls a tool with its dots replaced: workspace.read_file is workspace__read_file.
  • Agents can read this reference as data: GET /v1/tools/built-in and GET /v1/tools/built-in/:name, with a session or an API token scoped tools:read.

The tools

Family Tools Page
Workspace workspace.read_file, workspace.list_dir, workspace.write_file, workspace.delete_file, workspace.edit, workspace.search, workspace.run_command, workspace.verified_results, workspace.git_commit, workspace.git_push, workspace.share_file Workspace tools
Memory memory.ask, memory.train, memory.upload Memory tools
Execution labels os.set_execution_name, os.add_execution_link OS tools
Stopping the execution os.wait_execution, os.stop_execution OS tools
Reading the execution os.read_execution OS tools
Gate summary os.set_gate_summary, os.decide_gate OS tools
CEO questions os.ask_ceo OS tools
Self-improvement os.list_recommendations, os.record_issue_outcome, os.get_recommendation, os.decide_recommendation OS tools
Mail os.mail_list, os.mail_read, os.mail_reply, os.mail_send, os.mail_contacts, os.mail_contact_save, os.member_mailbox_actions OS tools
Mail triage os.mail_set_label, os.mail_set_handled, os.mail_set_many OS tools
Mail follow-ups os.mail_quiet_threads, os.mail_mark_chased, os.mail_snooze OS tools
Your mail os.my_mail_list, os.my_mail_read, os.my_mail_attachment, os.my_mail_set_label, os.my_mail_set_handled, os.my_mail_set_many, os.my_mail_reply, os.my_mail_send, os.my_mail_forward, os.my_mail_delete, os.my_mail_actions, os.my_mail_start_action, os.my_mail_schedule_action, os.my_mail_unschedule_action, os.my_mail_contacts, os.my_mail_contact_save, os.my_mail_contact_delete, os.my_mail_signature, os.my_mail_signature_set, os.my_mail_addresses, os.my_mail_address_signature_set OS tools
Escalations os.escalate_mail, os.mail_reply_draft OS tools
KPIs os.list_kpis, os.record_kpi_reading, os.get_enterprise_kpis, os.set_enterprise_kpis, os.get_team_kpis, os.set_team_kpis, kpi.record_reading, kpi.list_readings, role.list_kpis, role.define_kpi, role.edit_kpi OS tools
Context os.set_context, os.get_context, os.delete_context OS tools
Company state os.inspect_enterprise, os.directory, os.list_blockers, os.list_open_gates, os.list_waiting OS tools
Unblocking runs os.retry_run, os.route_run, os.clear_run, os.escalate_run OS tools
Planning os.read_enterprise, os.search_catalog, os.list_tool_bindings, os.list_built_in_tools, os.read_task, os.assess_impact, os.write_plan, os.read_plan OS tools
Chat threads os.chat_list, os.chat_read, os.chat_write, os.chat_open OS tools
Chat os.list_tasks, os.start_task, os.get_run, os.read_run_log, os.hand_off_task_brief, os.list_runs, os.kpi_board, os.list_enterprise_kpis, os.finish_waiting, os.restart_waiting, os.clear_blocker, os.inspect_task_contract, os.inspect_execution, os.preview_run_route, os.export_workflow_evidence, os.return_file, os.set_steps, os.connect_tool, os.use_tool Chat tools
Organisation os.list_roles, os.read_role, os.create_role, os.update_role, os.delete_role, os.add_role_task, os.remove_role_task, os.add_role_member, os.remove_role_member, os.list_task_definitions, os.read_task_definition, os.create_task, os.publish_task_version, os.set_task_run_status, os.set_task_schedule, os.remove_task_schedule, os.set_task_input_values, os.read_context, os.write_context, os.list_teams, os.read_team, os.create_team, os.update_team, os.delete_team, os.add_team_member, os.remove_team_member, os.publish_role, os.publish_team OS tools
Work items os.add_work_item, os.list_work_items, os.read_work_item, os.update_work_item, os.close_work_item, os.claim_work_item, os.read_work_item_draft, os.write_work_item_draft OS tools
Shared causes os.attach_repair OS tools
Computer use <prefix>.navigate, <prefix>.click, <prefix>.type, <prefix>.screenshot, <prefix>.extract, <prefix>.download, <prefix>.upload, <prefix>.sign_in, <prefix>.snapshot, <prefix>.wait, <prefix>.select, <prefix>.press, <prefix>.switch_tab, <prefix>.hover, <prefix>.scroll Computer-Use tools
Web web.read, web.sitemap, web.request Web tools

Read and write

Read tools change nothing. Write tools change something: a file, a label, a decision, a note in memory. A run credential can write only if its task declares an os.* tool that writes.

Write tools: workspace.write_file, workspace.delete_file, workspace.edit, workspace.run_command, workspace.git_commit, workspace.git_push, workspace.share_file, memory.train, os.set_execution_name, os.add_execution_link, os.wait_execution, os.stop_execution, os.set_gate_summary, os.decide_gate, os.ask_ceo, os.record_issue_outcome, os.decide_recommendation, os.mail_reply, os.mail_send, os.mail_contact_save, os.mail_set_label, os.mail_set_handled, os.mail_set_many, os.mail_mark_chased, os.mail_snooze, os.my_mail_set_label, os.my_mail_set_handled, os.my_mail_set_many, os.my_mail_reply, os.my_mail_send, os.my_mail_forward, os.my_mail_delete, os.my_mail_start_action, os.my_mail_schedule_action, os.my_mail_unschedule_action, os.my_mail_contact_save, os.my_mail_contact_delete, os.my_mail_signature_set, os.my_mail_address_signature_set, os.escalate_mail, os.mail_reply_draft, os.record_kpi_reading, os.set_enterprise_kpis, os.set_team_kpis, os.set_context, os.delete_context, kpi.record_reading, role.define_kpi, role.edit_kpi, os.retry_run, os.route_run, os.clear_run, os.escalate_run, os.write_plan, os.chat_write, os.chat_open, os.start_task, os.hand_off_task_brief, os.finish_waiting, os.restart_waiting, os.clear_blocker, os.create_role, os.update_role, os.delete_role, os.add_role_task, os.remove_role_task, os.add_role_member, os.remove_role_member, os.create_task, os.publish_task_version, os.set_task_run_status, os.set_task_schedule, os.remove_task_schedule, os.set_task_input_values, os.write_context, memory.upload, os.create_team, os.update_team, os.delete_team, os.add_team_member, os.remove_team_member, os.return_file, os.add_work_item, os.update_work_item, os.close_work_item, os.claim_work_item, os.write_work_item_draft, os.publish_role, os.publish_team, os.set_steps, os.attach_repair, os.connect_tool, <prefix>.click, <prefix>.type, <prefix>.upload, <prefix>.select, <prefix>.press, os.use_tool.

A few reads have a side effect, listed on the tool:

  • os.mail_read: Marks the message read for the member, the same as opening it in the portal.
  • os.my_mail_read: Marks the message read for you, the same as opening it.
  • os.chat_read: Over the API and the MCP server, marks the thread read, the same as opening it in the portal. In a run, nothing.

Gates and grants

A task can put a gate on a tool it declares, in its gates, and the call then waits for the CEO. A gate on a workspace.* or memory.* tool waits like any other gated call. A memory.* call is checked against the memory grants first, so one they refuse fails without asking anyone. While a task’s gates cover workspace.git_push, the OS pushes none of the run’s work on its behalf, not even a checkpoint. Some built-in tools carry gates or grants of their own:

  • os.ask_ceo is always gated, whatever the task declares, and the run ends on the CEO’s decision.
  • os.mail_reply is always gated, whatever the task declares, and the run ends on the CEO’s decision.
  • os.mail_send is always gated, whatever the task declares, and the run ends on the CEO’s decision.
  • os.escalate_mail is always gated, whatever the task declares, and the run ends on the CEO’s decision.
  • os.set_gate_summary must be called before os.mail_reply, which is handed back until it is. A task that declares one must declare the other.
  • memory.train: task is always allowed. member and role only on an original task, never a clone. team and enterprise only when this version grants that layer and the source event id starts with the granted prefix. A cloned task may too, in its own enterprise's memory and never its publisher's, as a task the enterprise wrote itself may; only a layer withdrawn on the team's page of a team the running member sits on or leads stops it, with clone_memory_not_granted. Reserved event ids (team: and gate:) stay refused.

What else a tool needs (a repo input, an assigned member, a binding) is on its own entry.

Retry safety

A call can be sent twice: a response lost on the way back, a retried run. Each tool says what a repeat does:

Retry Meaning Tools
safe Safe: repeating the call changes nothing. workspace.read_file, workspace.list_dir, workspace.search, workspace.verified_results, memory.ask, os.read_execution, os.list_recommendations, os.get_recommendation, os.mail_list, os.mail_read, os.mail_contacts, os.member_mailbox_actions, os.mail_quiet_threads, os.mail_mark_chased, os.mail_snooze, os.my_mail_list, os.my_mail_read, os.my_mail_attachment, os.my_mail_actions, os.my_mail_contacts, os.my_mail_signature, os.my_mail_addresses, os.list_kpis, os.get_enterprise_kpis, os.get_team_kpis, os.get_context, kpi.list_readings, role.list_kpis, os.inspect_enterprise, os.directory, os.list_blockers, os.list_open_gates, os.list_waiting, os.read_enterprise, os.search_catalog, os.list_tool_bindings, os.list_built_in_tools, os.read_task, os.assess_impact, os.read_plan, os.chat_list, os.chat_read, os.list_tasks, os.get_run, os.read_run_log, os.list_runs, os.kpi_board, os.list_enterprise_kpis, os.inspect_task_contract, os.inspect_execution, os.preview_run_route, os.export_workflow_evidence, os.list_roles, os.read_role, os.list_task_definitions, os.read_task_definition, os.read_context, os.list_teams, os.read_team, os.list_work_items, os.read_work_item, os.read_work_item_draft, <prefix>.navigate, <prefix>.screenshot, <prefix>.extract, <prefix>.download, <prefix>.sign_in, <prefix>.snapshot, <prefix>.wait, <prefix>.switch_tab, <prefix>.hover, web.read, web.sitemap, web.request
idempotent Idempotent: a repeat of the same call acts once, or leaves the same state. workspace.write_file, workspace.git_push, memory.train, os.set_execution_name, os.add_execution_link, os.wait_execution, os.stop_execution, os.set_gate_summary, os.decide_gate, os.ask_ceo, os.record_issue_outcome, os.decide_recommendation, os.mail_contact_save, os.mail_set_label, os.mail_set_handled, os.mail_set_many, os.my_mail_set_label, os.my_mail_set_handled, os.my_mail_set_many, os.my_mail_delete, os.my_mail_schedule_action, os.my_mail_unschedule_action, os.my_mail_contact_save, os.my_mail_contact_delete, os.my_mail_signature_set, os.my_mail_address_signature_set, os.record_kpi_reading, os.set_enterprise_kpis, os.set_team_kpis, os.set_context, os.delete_context, role.edit_kpi, os.retry_run, os.route_run, os.clear_run, os.escalate_run, os.write_plan, os.start_task, os.hand_off_task_brief, os.finish_waiting, os.clear_blocker, os.update_role, os.delete_role, os.add_role_task, os.remove_role_task, os.add_role_member, os.remove_role_member, os.set_task_run_status, os.set_task_schedule, os.remove_task_schedule, os.set_task_input_values, os.write_context, memory.upload, os.update_team, os.delete_team, os.add_team_member, os.remove_team_member, os.return_file, os.add_work_item, os.update_work_item, os.close_work_item, os.claim_work_item, os.write_work_item_draft, os.set_steps, os.attach_repair, os.connect_tool, <prefix>.select
unsafe Not retry-safe: a repeat acts again. workspace.delete_file, workspace.edit, workspace.run_command, workspace.git_commit, workspace.share_file, os.mail_reply, os.mail_send, os.my_mail_reply, os.my_mail_send, os.my_mail_forward, os.my_mail_start_action, os.escalate_mail, os.mail_reply_draft, kpi.record_reading, role.define_kpi, os.chat_write, os.chat_open, os.restart_waiting, os.create_role, os.create_task, os.publish_task_version, os.create_team, os.publish_role, os.publish_team, <prefix>.click, <prefix>.type, <prefix>.upload, <prefix>.press, <prefix>.scroll, os.use_tool

Errors

A failed call comes back one of three ways:

Handling What happens
Handed back (hand_back) Refused and handed back: nothing ran, and the model gets another turn
Tool error (tool_error) A tool error: the model reads it as the result and carries on
Run fails (fail) The run fails

Any tool call can come back with these, before the tool itself is reached:

Error When What happens
tool_not_on_task The tool exists, but the task does not declare it. The run fails
unknown_tool_name No tool anywhere has that name: a typo. The model is told the task's closest tools. Refused and handed back: nothing ran, and the model gets another turn
unknown_tool_repeated Three unknown names were already handed back in this run, and it called another. The run fails
bare_tool_name The call named a whole vendor catalog (github) instead of one of its tools. Refused and handed back: nothing ran, and the model gets another turn
tool_value_not_declared The task pinned a field (<tool>#<field>=<value>) and the call carried another value. Refused and handed back: nothing ran, and the model gets another turn
tool_value_refused The same, where the task marked the field fatal (<tool>#!<field>=<value>). The run fails

Each tool lists its own errors on its entry.