Tool System

Chief’s reasoning loop works by calling tools. Every meaningful action (running a script, browsing a page, reading a file, posting in Slack) is a tool call. This page lists the categories of tools Chief has access to.

Built-in Tools

These are always available, no integration needed.

Tool	What it does
`bash`	Execute a shell command in a sandboxed Bun runtime
`code`	Write & execute TypeScript / Python in a sandbox with timeout
`read_file`	Read a file from a Slack upload, generated artifact, or integration
`write_file`	Generate a file (text, MD, CSV, JSON) and stage it for upload
`browse`	Open a URL in a headless Playwright browser
`search`	Run a web search via the configured search provider
`extract_pdf`	Parse a PDF — text, tables, OCR for scans
`extract_excel`	Parse an XLSX or CSV
`vision`	Analyze an image with Claude vision
`generate_pdf`	Render a branded PDF from markdown / HTML
`generate_docx`	Generate a DOCX with brand styling
`slack_post`	Post a message to a Slack channel or DM
`slack_react`	Add or remove a reaction emoji
`slack_upload`	Upload a file to a Slack thread
`memory_save`	Save a tenant-scoped memory
`memory_recall`	Look up a saved memory
`approval_request`	Pause and ask a designated user for approval

Integration Tools

When you connect an integration in Dashboard → Integrations, Chief gains tools scoped to that integration. For example, connecting Stripe adds:

stripe.list_charges
stripe.list_customers
stripe.create_refund
stripe.list_invoices
stripe.list_subscriptions
... etc

Each integration’s full tool list is shown on its dashboard card after connection.

Custom API Tools

Custom integrations appear as a single tool with parameters:

custom_api.call(integration_name, method, path, body?)

If you uploaded an OpenAPI spec, individual endpoints get named tools instead.

Tool Selection

Chief picks tools by reasoning over the request, the available tool list, and recent context. For ambiguous requests, Chief asks rather than guessing — “Should I pull from Stripe or Sheets for this revenue question?”

Tool Safety Boundaries

Tool	Safety boundary
`bash` / `code`	Sandboxed runtime, no host filesystem, no host network beyond allowlist
`browse`	Sandboxed browser, no persistent cookies between tasks
Mutating integration tools (refund, delete, send)	Subject to your approval rules
Custom API DELETE / PATCH	Subject to your approval rules

Adding Tools

You can’t add arbitrary tools to Chief from outside (that would be a security boundary). The supported extension points are:

First-class integrations — request via support@hirechief.ai
Custom API integrations — bring your own HTTP API
MCP servers — point Chief at a self-hosted Model Context Protocol server

Tool Execution Logs

Every tool call Chief makes is logged with timestamp, parameters, response shape (not body), duration, and outcome. Visible in Dashboard → Usage → [task] → Tool Trace.

Slack Events Webhook Endpoints