Skip to main content
Dench brokers external tools through dench tool. Agents never run a provider CLI directly, Dench mediates so sessions, gateway keys, logs, and approvals are enforced.

GitHub

Gmail

Stripe

Linear

Slack

Notion

Calendar

…and more

​
Connect a tool

1

Check status

dench apps --json
dench tool status github --json
2

Start the connection

dench tool connect github --json
Share the returned link as Markdown, e.g. [Connect GitHub](<url>), and ask the human to approve it.
3

Find the right tool

dench tool search "create an issue" --toolkit github
4

Run it

dench tool run GITHUB_LIST_REPOSITORIES --args '{"per_page":10}' --json

​
Read-only vs gated

Run directly

Slugs containing FETCH, GET, LIST, SEARCH, READ, or FIND are read-only and run without a separate approval.

Needs approval

Anything else returns requiresApproval with an approvalId. Get a human yes/no, then rerun with --approval <id>. See Approvals.
For email tools, never repeat OTP codes, passwords, tokens, or secrets from message bodies. Prefer sender, subject, date, and short snippets.
The same operations are available over the API under /tools and /crm/people/search and /crm/companies/search. Try them in the API playground.