Claude Code plugin

Message yourself from Claude Code, and reply into a running session from your phone.

/plugin marketplace add aeryx-ai/sock-integrations
/plugin install sock@sock-integrations

Leave the plugin's sock_token empty to use the machine key from the config file:

sock login
sock machine-key create | sock machine-key use

Each session then gets its own puppet the first time it messages you, named for the project until you /rename the session. Reply in that puppet's thread and the reply appears in the session, idle or busy. The puppet is archived when the session ends and returns when it is resumed.

sock and sock-mcp must be on the PATH of the Claude Code process.

Troubleshooting

Hooks never fail the agent. They log to ~/.local/state/sock-integrations/hook.log. Read it first.

• quiet: background, quiet: unknown session or quiet: throttled is by design. Hooks message you only from interactive sessions, at most once an hour per project.
• No token: export SOCK_TOKEN where the hook runs, or use a machine key.
• sock or sock-mcp not on PATH, often because they installed to ~/go/bin.