Skip to main content
The published package is @dench.com/cli and the binary is dench. Run it with npx -y -p @dench.com/cli dench <command> or install it globally.
1

Sign in

Start the approval flow. Pick the command for your agent:
npx -y -p @dench.com/cli dench signin --kind cursor --name "Cursor Agent - Project"
An agent cannot approve its own sign-in. The approval must come from a human in the browser.
2

Approve in the browser

Open the printed link, confirm the workspace, and click Approve. No browser? Add --email you@example.com to get a 6-digit code instead.
3

Verify

Confirm the session and CRM access:
npx -y -p @dench.com/cli dench context --json
npx -y -p @dench.com/cli dench crm objects list --json
npx -y -p @dench.com/cli dench crm entries list task --json
Setup is complete once approval succeeds and these commands return data.

​
Stable identity

For a long-lived agent, set a stable session key before signing in: 
DENCH_SESSION_KEY=project-agent \
  npx -y -p @dench.com/cli dench signin --kind cursor --name "Cursor Agent - Project"
Do not set DENCH_SESSION_KEY to internal auto: or explicit: values. Switch between existing sessions with dench use <key-or-slug>.

​
Headless and CI

Skip the browser flow with a workspace API key from your settings: 
export DENCH_API_KEY="<workspace key>"
npx -y -p @dench.com/cli dench crm entries list people --json

​
Troubleshooting

Use npx -y -p @dench.com/cli dench <command>. A bare npx -y @dench.com/cli … fails because npx can’t find a bin matching the package name.
Run dench signin once and ask the human to approve it.
Run dench sessions --json, ask which to use, then dench use <key-or-slug>.
Chat, files, enrichment, and image-gen are paid. Run dench upgrade --tier pro and share the link. See Billing.

​
Next

CRM playbook

Model people, companies, tasks, and custom objects.

API playground

Try every endpoint live with your bearer token.