Dench CLI command reference

Run any command with npx -y -p @dench.com/cli dench <command>, or dench <command> if installed globally.

CRM

objects, fields, entries, cells, query

Integrations

apps, tool status/connect/run

Approvals

request, approve, reject

Memory

search, save

Browser

actions, Playwright sessions

Billing

status, topup, upgrade

API

the HTTP equivalent

Add --json to almost any command for machine-readable output.

dench signin --kind cursor --name "Cursor Agent - Project"
dench signin --new-workspace --org-name "Example" --kind cursor --name "Cursor Agent - Project"
dench signin --email user@example.com --kind cursor --name "Cursor Agent - Project"

Context

dench context --json
dench status --mine --json
dench agents --json
dench approvals --json

CRM

dench crm objects list --json
dench crm objects get <object> --json
dench crm objects create <name> --icon database --json
dench crm objects update <object> --visibility workspace|owner_only|owner_plus_members --json
dench crm fields list <object> --json
dench crm entries list <object> --json
dench crm entries list <object> --mine --json            # personal scope: assigned to me
dench crm views entries <object> <view> --assigned-to <userId|email|unassigned> --json
dench crm entries create <object> --data '{"Name":"Example"}' --json
dench crm entries update <object> <entryId> --data '{"Status":"Done"}' --json
dench crm cells set <object> <entryId> <field> '"value"' --json
dench crm query <object> --where '{"Status":"Open"}' --json
dench crm aggregate <object> --field Amount --json
dench crm batch --file ops.jsonl --json

Tasks are CRM entries on the protected task object, with shortcuts:

dench crm entries list task --json
# Field names are validated on write (unknown fields are rejected). Check
# them first with `dench crm fields list task`.
dench crm entries create task --data '{"Name":"Follow up","Status":"To Do"}' --json
dench crm tasks mine [--priority high] --json
dench crm tasks list <object> <entryId> --json
dench crm tasks create <object> <entryId> --name "Follow up" --assignee <userId> --due 2026-09-05 --priority high
dench crm tasks priority <taskEntryId> <low|medium|high | --none>
dench crm tasks subtasks <taskEntryId> --json
dench crm tasks create-subtask <taskEntryId> --name "Write runbook" [--assignee <userId>] [--due YYYY-MM-DD] [--priority low]
dench crm tasks parent <taskEntryId> <parentTaskEntryId | --none>
dench crm tasks repeat <taskEntryId> [daily|weekdays|weekly|monthly|yearly] [--on mon,wed] [--every N] [--day 17|last] [--nth 2 --on tue] [--ends-after N | --until YYYY-MM-DD] [--on-schedule] [--skip-weekends]
dench crm tasks repeat <taskEntryId> --rrule "FREQ=WEEKLY;BYDAY=MO"
dench crm tasks repeat <taskEntryId> --skip | --pause | --resume | --off
dench crm tasks series [--status active|paused|ended]
dench crm tasks series <seriesId> --occurrences
dench crm tasks complete <taskEntryId>
dench crm tasks reopen <taskEntryId>
dench crm tasks delete <taskEntryId> [--keep-subtasks]

Comments

Threaded comments on a record; [@Name](/?member=<userId>) mentions notify, --dench summons the agent into the thread.

dench crm comments list <object> <entryId> --json
dench crm comments replies <commentId> --json
dench crm comments create <object> <entryId> --body "…" [--reply-to <commentId>] [--dench]
dench crm comments update <commentId> --body "…"
dench crm comments delete <commentId>
dench crm comments react <commentId> 👍
dench crm watch <object> <entryId> [--off]

Analytics

The dashboard above every object table — same math the UI draws. See Analytics.

dench crm analytics get <object> [--view <view>] --json
dench crm analytics compute <object> [--view <view>] [--period this_month] [--panel <id> …] [--panels '<json>'] [--filters '<FilterGroup>'] --json
dench crm analytics save <object> <panelId> --panel '<json>' [--view <view>]
dench crm analytics delete <object> <panelId> [--view <view>]
dench crm analytics reorder <object> <id1> <id2> … [--view <view>]
dench crm analytics roles <object> --roles '<json>'
dench crm analytics collapse <object> | expand <object>
dench crm analytics scope <object> <view> --mode own|shared

Meetings

Meetings are meeting CRM records (create/update/delete with dench crm entries … meeting). These verbs reach the transcript, action items and attendance beside the record, and import many calls at once.

dench meetings list --json
dench meetings get <meetingId> --json
dench meetings transcript get <meetingId> [--json|--text]
dench meetings transcript set <meetingId> --text transcript.txt | --jsonl segments.jsonl [--append]
dench meetings action-items list|add|set|done|undone|delete …
dench meetings participants list <meetingId> --json
dench meetings participants set <meetingId> --people 'Hank <hank@globex.com>; ada@acme.com' [--replace]
dench meetings import --csv calls.csv | --jsonl calls.jsonl [--map '{…}'] [--dedupe-key <col>] [--on-conflict skip|update|error] --json

Members

Profiles, presence, and what each teammate is doing. <userId|email> accepts either.

dench members list --json
dench members get <userId|email> --json
dench members activity <userId|email> [--limit 30] [--kinds comments,changes]
dench members tasks <userId|email>
dench members presence [<userId|email>...]
dench members me [--name "…"] [--tagline "…"] [--timezone <IANA>] [--avatar ./me.png]

Notifications

dench notifications list [--filter inbox|unread|archived|all|mentions] --json
dench notifications count
dench notifications read <id> [--unread]
dench notifications read-all
dench notifications archive <id>
dench notifications prefs [--set emailEnabled=false] [--set <kind>.email=false]

Approval Commands

dench approval request "Deploy to production?" --risk high --json
dench approval approve <approval_id> --evidence "User said yes in chat" --json
dench approval reject <approval_id> --evidence "User said no in chat" --json

Dench Integrations

dench integrations lists every connected app: Composio apps plus the Gmail, Outlook, Calendar and LinkedIn accounts Dench connects itself. Each row carries source (composio or unipile) — only composio rows have a connectedAccountId to pass to dench tool run --account. (For the App Store — installing and publishing apps — see dench apps.)

dench integrations --json
dench tool status --json
dench tool status github --json
dench tool connect github --json
dench tool search "create github issue" --toolkit github --json
dench tool run <tool_slug> --args '{"key":"value"}' --json
dench tool disconnect <connection_id> --json

Memory

dench memory search "deployment policy" --json
dench memory save deployment-policy "Never deploy without approval." --kind decision --json

Browser

dench browser open https://example.com --json
dench browser inspect --json
dench browser click --text "Sign in"
dench browser screenshot --output page.jpg --json
dench browser session create --json
dench browser session status <session_id> --json
dench browser session stop <session_id> --json

Interactive actions and Playwright/CDP sessions are covered in Browser.

Chat

dench chat list --json
dench chat search "pricing" --json
dench chat read <thread_id> --json
dench chat new "Research the latest CRM changes" --json
dench chat send <thread_id> "Continue" --json
dench chat follow <thread_id>
dench agent new "Run the same chat agent loop" --json

Routines

dench cron list --json
dench cron create "Daily digest" --prompt "Summarize open CRM tasks" --every 1d --json
dench cron update <job_id> --name "New name" --json
dench cron enable <job_id> --json
dench cron disable <job_id> --json
dench cron run <job_id> --json
dench cron history --json

dench routine and dench routines are aliases for dench cron.

Outreach Campaigns

Email and LinkedIn steps sent to a list of people on one schedule. <campaign> is an id or an exact name.

dench campaign list --all --json
dench campaign create --name "Founder outreach" --timezone America/Los_Angeles --window "Mon-Fri 9-18" --daily-cap 30 --email-mailboxes <mailboxId1>,<mailboxId2> --linkedin-accounts <linkedinId> --json
dench campaign set <campaign> --window "Mon-Fri 9-18" --window "Sat 10-12" --no-stop-on-reply --start 2026-09-03 --json
dench campaign set <campaign> --email-mailboxes <mailboxId1>,<mailboxId2> --linkedin-accounts none --json
dench campaign accounts --json
dench campaign steps get <campaign> > steps.json
dench campaign steps set <campaign> --file steps.json --json
dench campaign add <campaign> --object lead --view "Q3 targets" --json
dench campaign add <campaign> --object people --entries <id1>,<id2> --json
dench campaign add <campaign> --name "Ada Lovelace" --email ada@example.com --json
dench campaign launch <campaign> --ack-linkedin-risk --json
dench campaign get <campaign> --json
dench campaign people <campaign> --status paused --json
dench campaign stop <campaign> --person <enrollmentId> --json
dench campaign resume-person <campaign> --person <enrollmentId> --json
dench campaign events <campaign> --max-pages 2 --json
dench campaign pause <campaign> --json
dench campaign resume <campaign> --json
dench campaign archive <campaign> --json

steps.json is a JSON array of steps (email, wait, linkedin_visit, linkedin_connection, linkedin_message); steps can only change while the campaign is a draft. --window takes "<days> <start>-<end>", e.g. "Mon-Fri 9-18" or "Mon,Wed,Fri 10-16", and may repeat. A bare --start / --end date is midnight in the campaign’s timezone. launch checks readiness first and prints each blocker in plain words. get shows the funnel, what is being sent now, what comes next and why anything is holding. Outreach needs a workspace member’s credentials; an organization-only API key cannot run it. Sender pools are configured once with --email-mailboxes and --linkedin-accounts (up to 50 ids per channel, comma-separated or a JSON array). Omit to preserve existing settings; none or '[]' clears a pool. These map to emailMailboxAccountIds / linkedinAccountIds in the API. Steps in a pool campaign omit sender ids; legacy step senders are kept until conversion. Only accessible accounts may be selected, launch validates availability, and existing conversations keep their assigned sender. dench campaign accounts --json lists email and LinkedIn senders with local ids and display labels, never provider credentials. Discovery follows the acting member’s permissions: their private accounts plus teammates’ shared connections. LinkedIn rows include linkedinAccountId, availability, remainingToday (invites/messages/profiles) and remainingInvitesThisWeek. Today’s invites also respect the weekly cap. Counts are account-local usage snapshots before queued work and campaign limits; launch/dispatch revalidate. For API clients, GET /v1/campaigns/accounts/linkedin returns the same LinkedIn summaries using a member-bound API key or agent session.

Files

dench files ls / --json
dench files mv /old.txt /new.txt --json
dench files rm /old.txt --json
dench stage /tmp/output /workspace/output --json

Search And Images

dench search "latest AI CRM workflows" --json
dench search "senior ML engineers at fintech companies" --category people --json
dench search "Swiss fintech founded after 2020" --category company --json
dench search contents https://example.com --json
dench search answer "What changed?" --json
dench image generate "simple app icon" --json
dench image edit "make it blue" --input ./icon.png --json

--category people and --category company return structured entity data. They do not return email addresses or phone numbers. Domain filters work for company search but are refused for people search. Published-date filters are refused for both entity categories because Exa does not apply them reliably.

Dench Web

Page reads, brand kits, sitemaps, crawls, screenshots, and structured extracts. Prefer these over writing your own scraper. Search stays dench search. dench context is workspace orientation, not this.

dench web scrape https://example.com --json
dench web brand stripe.com --json
dench web sitemap example.com --limit 1000 --json
dench web crawl https://example.com --max-pages 15 --json
dench web screenshot https://example.com --full-page --json
dench web extract https://example.com --schema '{"type":"object","properties":{"title":{"type":"string"}}}' --json
dench web product https://example.com/product --json
dench web competitors stripe.com --json
dench web styleguide stripe.com --json
dench web classify stripe.com --scheme naics --json

Crawl defaults to 15 pages and is hard-capped at 50.

Billing

dench billing status --json
dench billing topup --amount 10 --json
dench upgrade --tier pro --json

Sessions

dench sessions --json
dench use <session-key-or-workspace-slug> --json
dench logout --json

Session commands operate on the caller’s local machine.

Agent Config

dench identity show --json
dench organisation show --json
dench user show --json
dench tools show --json
dench mem show --json
dench heartbeat status --json
dench bootstrap status --json
dench model default <model_id> --json
dench daily today --json

Start

Core

CLI

API

Dench CLI command reference

CRM

Integrations

Approvals

Memory

Browser

Billing

API

Context

CRM

Comments

Analytics

Meetings

Members

Notifications

Approval Commands

Dench Integrations

Memory

Browser

Chat

Routines

Outreach Campaigns

Files

Search And Images

Dench Web

Billing

Sessions

Agent Config

CRM

Integrations

Approvals

Memory

Browser

Billing

API

​Sign In

​Context

​CRM

​Comments

​Analytics

​Meetings

​Members

​Notifications

​Approval Commands

​Dench Integrations

​Memory

​Browser

​Chat

​Routines

​Outreach Campaigns

​Files

​Search And Images

​Dench Web

​Billing

​Sessions

​Agent Config

Sign In

Context

CRM

Comments

Analytics

Meetings

Members

Notifications

Approval Commands

Dench Integrations

Memory

Browser

Chat

Routines

Outreach Campaigns

Files

Search And Images

Dench Web

Billing

Sessions

Agent Config