@ear3/voice-config-cli

🤖 AI agents / LLMs: start with AGENTS.md, then llms.txt — both bundled in this package (also at https://www.ear3.ai/llms.txt). They are the complete machine-readable guide: commands, ids, and the exact create → deploy → integrate flow. To make Claude Code pick this up automatically in your project, add one line to your CLAUDE.md:

@node_modules/@ear3/voice-config-cli/AGENTS.md

Create and deploy an Ear3 AI voice interview from the terminal. Sign in once through the browser — no key copy-pasting:

npx @ear3/voice-config-cli login    # opens the dashboard, you click Approve — done
npx @ear3/voice-config-cli create \
  --name "Coffee habits" \
  --prompt "3 quick questions about how people brew and drink coffee"

AI agents: before running create, if the user hasn't said what the interview should be about, ask them first — or, if they mentioned a topic earlier, propose it and confirm. Never invent the --prompt. And use the exact public URL the CLI prints — copy it verbatim, never construct it.

~30 seconds later you get a deployed interview:

• a public URL you can share immediately (no code needed),
• the interviewId (deployment id) + ready-made env lines and snippets for @ear3/voice-interviewer and a plain hosted-page iframe.

Run it with no flags for interactive prompts. --json prints the raw API response for scripting.

More commands:

ear3 create --no-deploy   # generate a draft only — deploy it later
ear3 deploy <id>          # deploy an existing interview → interviewId + link
ear3 edit <id>            # open the dashboard editor for an interview
ear3 responses <id>       # pull responses + transcripts to the terminal
ear3 insights <id> "<q>"  # ask an AI question about the responses
ear3 list                 # your deployed interviews (id, status, responses)
ear3 session <sessionId>  # one session: status, response, transcript key
ear3 logout               # forget the stored key

Options

| Flag | Env | Default | | ------------------- | ------------------ | ------------------- | | --key sk_… | EAR3_CONFIG_CLI_KEY | stored by ear3 login | | --api-base <url> | EAR3_API_BASE | https://app.ear3.ai | | --language | | en | | --max-questions | | 10 (3–30) | | --respondents | | 10 | | --duration (min) | | 5 |

ear3 login mints a secret key for you via a browser approval (choose test or live on the approval page); it lands in ~/.ear3/config.json (0600). Alternatively pass --key sk_… / EAR3_CONFIG_CLI_KEY manually — mint one at Dashboard → Settings → API Keys. Full credentials guide: https://www.ear3.ai/developer/sdk/credentials

Claude Code plugin

Using Claude Code? The Ear3 plugin's /ear3:create-interview skill takes you from a plain-language topic to a deployed interview (and the interviewId + key this package needs) in one go — Claude also invokes it on its own when you ask to create an interview:

/plugin marketplace add https://www.ear3.ai/claude/marketplace.json
/plugin install ear3@ear3

Not using Claude Code plugins? (Cursor, Codex, plain agents): copy skills/create-interview/ into your project's .claude/skills/ — it works without the namespace, as /create-interview.

License

MIT.