add-emacs
Add Emacs as a channel. Opens an interactive chat buffer and org-mode integration so you can talk to NanoClaw from within Emacs (Doom, Spacemacs, or vanilla). Local HTTP bridge — no bot token or external service needed.
Profile →npx skills add nanocoai/nanoclaw --skill add-emacs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Add Emacs Channel Adds Emacs support via a local HTTP bridge. Works with Doom Emacs, Spacemacs, and vanilla Emacs 27.1+. ## What you can do with this - **Ask while coding** — open the chat buffer (`C-c n c` / `SPC N c`), ask about a function or error without leaving Emacs - **Code review** — select a region and send it with `nanoclaw-org-send`; the response appears as a child heading inline in your org file - **Meeting notes** — send an org agenda entry; get a summary or action item list back as a child node - **Draft writing** — send org prose; receive revisions or continuations in place - **Research capture** — ask a question directly in your org notes; the answer lands exactly where you need it ## Install NanoClaw doesn't ship channels in trunk. This skill copies the Emacs adapter and the Lisp client in from the `channels` branch. Native HTTP bridge — no Chat SDK, no adapter package. ### Pre-flight (idempotent) Skip to **Enable** if all of these are already in place: - `src/channels/emacs.ts` exists - `src/channels/emacs.test.ts` exists - `src/channels/emacs-registration.test.ts` exists - `emacs/nanoclaw.el` exists - `src/channels/index.ts` contains `import './emacs.js';` Othe
- What you can do with this
- Install
- Pre-flight (idempotent)
- 1. Fetch the channels branch
- 2. Copy the adapter and Lisp client
- 3. Append the self-registration import
- 4. Build and validate
- Enable
- Wire the channel
- If this is your first agent group
- Otherwise — wire to an existing agent group
- Configure Emacs
- Restart NanoClaw
- Verify
git fetch origin channels
mkdir -p emacs
git show origin/channels:src/channels/emacs.ts > src/channels/emacs.ts
git show origin/channels:src/channels/emacs.test.ts > src/channels/emacs.test.ts
git show origin/channels:src/channels/emacs-registration.test.ts > src/channels/emacs-registration.test.ts
git show origin/channels:emacs/nanoclaw.el > emacs/nanoclaw.el
pnpm run build
pnpm exec vitest run src/channels/emacs-registration.test.ts
node -e "console.log(require('crypto').randomBytes(16).toString('hex'))"
pnpm exec tsx setup/index.ts --step register -- \What does the add-emacs skill do?
Add Emacs as a channel. Opens an interactive chat buffer and org-mode integration so you can talk to NanoClaw from within Emacs (Doom, Spacemacs, or vanilla). Local HTTP bridge — no bot token or external service needed.
How do I install it?
Run `npx skills add nanocoai/nanoclaw --skill add-emacs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nanocoai/nanoclaw, a repository with 30,426 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.