@eleanor4devs/cli

Eleanor CLI for eleanor4devs — install the MCP entry, install/list skill packs, link to Telegram, check status.

Install

npm install -g @eleanor4devs/cli
eleanor4devs install

Requires Node 20+. No sudo, no global system deps; installs only into ~/.claude/ (MCP entry + skills) and ~/.eleanor4devs/ (audit log + auth state).

Commands

eleanor4devs install

Writes the eleanor4devs MCP server entry into ~/.claude/mcp_servers.json (preserving any existing entries from other agents), installs the Core Skills Pack under ~/.claude/skills/eleanor4devs/, and sets up the Claude Code hook templates.

eleanor4devs install-skills [--core|--how-to]

Install the Core Skills Pack (7 markdown skills — transfer-control, pause-thread, wake-thread, adopt-session, check-focus, dispatch-thread, summarize-for-voice-review) or the How-To Pack (pointers at global /brainstorm / /spec / /plan / /implement / /review skills with usage notes).

eleanor4devs skills list

Lists installed skills under ~/.claude/skills/eleanor4devs/ with their source pack.

eleanor4devs auth

Displays a one-time code. Send it to @eleanor4devs_bot on Telegram. The bot links your Telegram identity to this CLI install.

eleanor4devs status

Confirms your auth, prints the connected Telegram identity, lists the threads Eleanor is currently watching.

/e4d (Claude Code slash command)

Per-session opt-in. Type /e4d inside a Claude Code session to toggle Eleanor reporting for that session only. Each session is opted in independently — installing eleanor4devs monitors nothing by default. The slash command body runs eleanor4devs toggle --session ${CLAUDE_SESSION_ID} via the Bash tool; Claude Code substitutes the session id at file-load time. To take a session out of Eleanor's view, type /e4d again in that session. Concurrent Claude sessions you never opted in stay completely untouched (no reports, no in-session banners) — this is the cross-session-interference fix that shipped in v0.0.15.

/e4d-status (Claude Code slash command)

Read-only counterpart to /e4d: prints the current eleanor4devs status output (linked state + recent-sessions table) plus this session's own reporting state. Never mutates anything.

eleanor4devs uninstall [--yes]

The clean reverse of install — removes every eleanor4devs artifact on the machine except the npm package itself: the Claude Code lifecycle hook entries (when registered), the eleanor4devs MCP entry in ~/.claude/mcp_servers.json, the /e4d + /e4d-status slash commands, the installed skill packs, and ~/.eleanor4devs (per-session reporting state, device credential, local audit log). Other agents' hooks, MCP entries, commands, and skills are preserved untouched. On a linked machine it first (best-effort) reports your opted-in sessions as disabled and revokes the device credential server-side — an unreachable backend never blocks the local removal. Interactive runs list what will be removed and ask first; --yes skips the prompt (required for non-interactive use). Idempotent — a second run reports nothing to remove. It finishes by printing the one step it does not perform: npm uninstall -g @eleanor4devs/cli.

eleanor4devs --version

Prints the CLI version.

Auth flow

CLI auth uses a one-time code linked through the Telegram bot per spec DD-4 (Telegram-only auth at MVP; Google / Apple ship Post-MVP with the native apps).

Updating

npm install -g @eleanor4devs/cli@latest

Releases are lockstep across all 4 @eleanor4devs/* packages (provider-contract, sdk, mcp, cli) — they share a single version.

Uninstall

eleanor4devs uninstall
npm uninstall -g @eleanor4devs/cli

eleanor4devs uninstall removes everything the installer and the /e4d opt-ins put on the machine — hooks, MCP entry, slash commands, skill packs, ~/.eleanor4devs — preserving every other agent's entries, and on a linked machine best-effort disables your opted-in sessions and revokes the device credential. The npm package itself is the one artifact left; remove it with the second command (uninstall prints it as the final step). eleanor4devs logout alone suffices when you only want to unlink this machine and keep the install.

Coexistence with dotfile/AGENTS.md setups

eleanor4devs install writes ONLY:

• ~/.claude/mcp_servers.json (merged, never clobbered)
• ~/.claude/settings.json (only the hooks key, merged with other agents' entries)
• ~/.claude/skills/eleanor4devs/ (the Core Skills Pack)
• ~/.claude/commands/e4d.md and ~/.claude/commands/e4d-status.md
• ~/.eleanor4devs/state.json (per-session reporting state — only if absent)

It never writes ~/.claude/CLAUDE.md, ~/.codex/AGENTS.md, or any other agent-memory file. If you manage your config through a dotfile repo (the Kychee model uses junctions/symlinks from ~/.claude/skills into a shared hub), the installer leaves the symlink targets the dotfile repo owns alone, and writes only the regular files it manages itself. Codex skill discovery has its own discovery path and is wired up in a separate install task (Phase 10, not yet shipped).

Spec reference

Internal product spec is private. Public documentation: https://eleanor4devs.com.

License

UNLICENSED — code shipped publicly for consumer access only. Contact for licensing terms.