setup

declaude setup

The plugin already registers the Claude Code hook. It ships hooks/hooks.json, which Claude Code loads on install. An unset hook_enabled option means on, so a fresh install rewrites replies after its API key is configured. The manifest does not declare a default because Claude Code may export declared defaults to plugin processes. The api_key option stays optional because the MCP tools sign in on their own.

One case still stays inert. A user who exports DECLAUDE_TOKEN and never sets hook_enabled keeps the plugin hook off. That user may still run a version 1.0 manual hook, and two hooks would translate and bill every reply twice.

Work through the steps below in order. Report the result of each one.

1. Remove any manual hook entry

Claude Code merges hooks from several settings files. Search all of them:

for f in "${CLAUDE_CONFIG_DIR:-$HOME/.claude}"/settings.json \
         "${CLAUDE_CONFIG_DIR:-$HOME/.claude}"/settings.local.json \
         .claude/settings.json .claude/settings.local.json; do
  [ -f "$f" ] && grep -l declaude_hook "$f"
done

Open each file the search names. Look for a MessageDisplay or Stop entry that runs declaude_hook.py. Remove that entry.

The plugin now registers the hook. A manual entry on top of it translates every reply twice and bills the user twice. Do not enable the plugin hook until every manual entry is removed.

2. Check for a legacy key

echo "${DECLAUDE_TOKEN:+set}"

If the answer is set, do not edit or replace it. The plugin can keep using DECLAUDE_TOKEN during migration. If the answer is empty, the user may still have a key in secure plugin storage; check that in step 3.

3. Configure and enable the plugin hook

Only after every manual entry is removed, run:

/plugin configure declaude@tenken

Set the options in the configuration dialog:

• api_key: if a key is already stored, do not edit or replace it. Otherwise get a dk_ key at /signin and enter it in this masked field. Do not paste it into the chat. Existing DECLAUDE_TOKEN users may leave this empty, because the hook falls back to that environment variable.
• hook_enabled: type true or false in this field. An unset value means on. Type false to stop automatic rewrites. Type true if the user exports DECLAUDE_TOKEN and wants the plugin hook on. The hook exits silently when it has no key, so a missing key produces no error message.