Sign the CLI in once and your coding agent can drive every part of Configure this dashboard can: ask about your users, browse conversations, create keys, register callbacks, read logs.
One instruction
Paste into your agent. It reads the integration guide and follows it end to end.
Sign in once
After this, the agent runs everything below as you.
npx configure login
Everything the dashboard does
setup, keys, sso, users, ask, conversations, logs, usage. If a page here can do it, the CLI can.
configure ask "what do my users want?"
Integration guide
The file the agent reads. Also readable by a human.
configure.dev/skill.md
Different from the memory skill your users install (configure.dev/memory.md). Theirs teaches an agent to use a person's profile; this lets an agent build with Configure and operate this account.
Configure is ready
Paste this to your coding agent.
Cursor, Claude Code, Windsurf — they read configure.dev/skill.md, ask which path you want, and wire Configure into the agent you already have.
Prompt for your coding agent
Read https://configure.dev/skill.md and follow it. If .env already has CONFIGURE_API_KEY and CONFIGURE_PUBLISHABLE_KEY, use them; otherwise run npx configure setup --users yourself to create the keys and register the OAuth callback. Prefer integrating into the existing app over scaffolding a new one.
Agent—
Developer—
Your keys
No keys yet.
Install Configure
Run this in your project root before pasting the prompt. The coding agent will pick up from there.
npm install configure
1Install
npm install configure
2Authenticate users in the browser
Add a Personalization entry or Link trigger. It handles phone OTP and fires configure:linked with an agent-scoped token.
Send the Link token to your backend. Read the approved profile there, pass formatted profile context to the model, expose Configure tools, and commit after read-backed turns.
Secret keys have full API access. Use server-side only.
Save this key now — it won't be shown again.
NameTypeKeyCreatedLast Used
Sign in with Configure
Each app has one client. npx configure setup --users creates it for localhost; add your deployed callback here so the same CONFIGURE_OAUTH_CLIENT_ID works in every environment.
Agent
No agents yet.
Lowercase letters, numbers and hyphens, 2–63 characters. This is the handle your API key acts as; the display name is what users see on the consent screen.
HTTPS, or localhost while developing. This must match the redirect your app sends, character for character.
Save this secret now — it won't be shown again. Keep it server-side; rotate it here if it is lost.