refactor: rename nanoclaw → ghostclaw throughout codebase

Complete rename of all internal references now that GhostClaw has
diverged from NanoClaw with its own architecture (no containers,
settings-based MCP, CLAUDE_CONFIG_DIR isolation).

- NANOCLAW_* env vars → GHOSTCLAW_*
- MCP server name nanoclaw → ghostclaw
- .nanoclaw/ state dir → .ghostclaw/
- Output markers NANOCLAW_OUTPUT_* → GHOSTCLAW_OUTPUT_*
- Package name → ghostclaw-agent-runner
- LaunchAgent → com.ghostclaw
- All 34 skill files, test files, docs updated
- 446 tests pass, both projects compile

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: ziggy

.claude/skills/add-discord/SKILL.md

@@ -6,7 +6,7 @@ This skill adds Discord support to NanoClaw using the skills engine for determin
 
 ### Check if already applied
 
-Read `.nanoclaw/state.yaml`. If `discord` is in `applied_skills`, skip to Phase 3 (Setup). The code changes are already in place.
+Read `.ghostclaw/state.yaml`. If `discord` is in `applied_skills`, skip to Phase 3 (Setup). The code changes are already in place.
 
 ### Ask the user
 
@@ -26,7 +26,7 @@ Run the skills engine to apply this skill's code package. The package files are
 
 ### Initialize skills system (if needed)
 
-If `.nanoclaw/` directory doesn't exist yet:
+If `.ghostclaw/` directory doesn't exist yet:
 
 ```bash
 npx tsx scripts/apply-skill.ts --init
@@ -48,7 +48,7 @@ This deterministically:
 - Three-way merges updated routing tests into `src/routing.test.ts`
 - Installs the `discord.js` npm dependency
 - Updates `.env.example` with `DISCORD_BOT_TOKEN` and `DISCORD_ONLY`
-- Records the application in `.nanoclaw/state.yaml`
+- Records the application in `.ghostclaw/state.yaml`
 
 If the apply reports merge conflicts, read the intent files:
 - `modify/src/index.ts.intent.md` — what changed and invariants for index.ts
@@ -173,7 +173,7 @@ Tell the user:
 ### Check logs if needed
 
 ```bash
-tail -f logs/nanoclaw.log
+tail -f logs/ghostclaw.log
 ```
 
 ## Troubleshooting
@@ -183,7 +183,7 @@ tail -f logs/nanoclaw.log
 1. Check `DISCORD_BOT_TOKEN` is set in `.env` AND synced to `data/env/env`
 2. Check channel is registered: `sqlite3 store/messages.db "SELECT * FROM registered_groups WHERE jid LIKE 'dc:%'"`
 3. For non-main channels: message must include trigger pattern (@mention the bot)
-4. Service is running: `launchctl list | grep nanoclaw`
+4. Service is running: `launchctl list | grep ghostclaw`
 5. Verify the bot has been invited to the server (check OAuth2 URL was used)
 
 ### Bot only responds to @mentions

.claude/skills/add-discord/modify/src/config.ts

@@ -28,7 +28,7 @@ const HOME_DIR = process.env.HOME || os.homedir();
 export const MOUNT_ALLOWLIST_PATH = path.join(
   HOME_DIR,
   '.config',
-  'nanoclaw',
+  'ghostclaw',
   'mount-allowlist.json',
 );
 export const STORE_DIR = path.resolve(PROJECT_ROOT, 'store');
@@ -37,7 +37,7 @@ export const DATA_DIR = path.resolve(PROJECT_ROOT, 'data');
 export const MAIN_GROUP_FOLDER = 'main';
 
 export const CONTAINER_IMAGE =
-  process.env.CONTAINER_IMAGE || 'nanoclaw-agent:latest';
+  process.env.CONTAINER_IMAGE || 'ghostclaw-agent:latest';
 export const CONTAINER_TIMEOUT = parseInt(
   process.env.CONTAINER_TIMEOUT || '1800000',
   10,

.claude/skills/add-gmail/SKILL.md

@@ -11,7 +11,7 @@ This skill adds Gmail support to NanoClaw — either as a tool (read, send, sear
 
 ### Check if already applied
 
-Read `.nanoclaw/state.yaml`. If `gmail` is in `applied_skills`, skip to Phase 3 (Setup). The code changes are already in place.
+Read `.ghostclaw/state.yaml`. If `gmail` is in `applied_skills`, skip to Phase 3 (Setup). The code changes are already in place.
 
 ### Ask the user
 
@@ -26,7 +26,7 @@ AskUserQuestion: Should incoming emails be able to trigger the agent?
 
 ### Initialize skills system (if needed)
 
-If `.nanoclaw/` directory doesn't exist yet:
+If `.ghostclaw/` directory doesn't exist yet:
 
 ```bash
 npx tsx scripts/apply-skill.ts --init
@@ -46,7 +46,7 @@ Apply the changes described in `modify/container/agent-runner/src/index.ts.inten
 
 #### 3. Record in state
 
-Add `gmail` to `.nanoclaw/state.yaml` under `applied_skills` with `mode: tool-only`.
+Add `gmail` to `.ghostclaw/state.yaml` under `applied_skills` with `mode: tool-only`.
 
 #### 4. Validate
 
@@ -73,7 +73,7 @@ This deterministically:
 - Three-way merges Gmail MCP server into `container/agent-runner/src/index.ts` (@gongrzhe/server-gmail-autoauth-mcp)
 - Three-way merges Gmail JID tests into `src/routing.test.ts`
 - Installs the `googleapis` npm dependency
-- Records the application in `.nanoclaw/state.yaml`
+- Records the application in `.ghostclaw/state.yaml`
 
 If the apply reports merge conflicts, read the intent files:
 
@@ -182,14 +182,14 @@ Tell the user:
 
 ### Test channel mode (Channel mode only)
 
-Tell the user to send themselves a test email. The agent should pick it up within a minute. Monitor: `tail -f logs/nanoclaw.log | grep -iE "(gmail|email)"`.
+Tell the user to send themselves a test email. The agent should pick it up within a minute. Monitor: `tail -f logs/ghostclaw.log | grep -iE "(gmail|email)"`.
 
 Once verified, offer filter customization via `AskUserQuestion` — by default, only emails in the Primary inbox trigger the agent (Promotions, Social, Updates, and Forums are excluded). The user can keep this default or narrow further by sender, label, or keywords. No code changes needed for filters.
 
 ### Check logs if needed
 
 ```bash
-tail -f logs/nanoclaw.log
+tail -f logs/ghostclaw.log
 ```
 
 ## Troubleshooting
@@ -227,7 +227,7 @@ npx -y @gongrzhe/server-gmail-autoauth-mcp
 
 1. Remove `~/.gmail-mcp` mount from `src/container-runner.ts`
 2. Remove `gmail` MCP server and `mcp__gmail__*` from `container/agent-runner/src/index.ts`
-3. Remove `gmail` from `.nanoclaw/state.yaml`
+3. Remove `gmail` from `.ghostclaw/state.yaml`
 4. Clear stale agent-runner copies: `rm -r data/sessions/*/agent-runner-src 2>/dev/null || true`
 5. Rebuild: `cd container && ./build.sh && cd .. && npm run build && launchctl kickstart -k gui/$(id -u)/com.ghostclaw` (macOS) or `systemctl --user restart ghostclaw` (Linux)
 
@@ -239,6 +239,6 @@ npx -y @gongrzhe/server-gmail-autoauth-mcp
 4. Remove `gmail` MCP server and `mcp__gmail__*` from `container/agent-runner/src/index.ts`
 5. Remove Gmail JID tests from `src/routing.test.ts`
 6. Uninstall: `npm uninstall googleapis`
-7. Remove `gmail` from `.nanoclaw/state.yaml`
+7. Remove `gmail` from `.ghostclaw/state.yaml`
 8. Clear stale agent-runner copies: `rm -r data/sessions/*/agent-runner-src 2>/dev/null || true`
 9. Rebuild: `cd container && ./build.sh && cd .. && npm run build && launchctl kickstart -k gui/$(id -u)/com.ghostclaw` (macOS) or `systemctl --user restart ghostclaw` (Linux)

.claude/skills/add-gmail/modify/container/agent-runner/src/index.ts

@@ -105,8 +105,8 @@ async function readStdin(): Promise<string> {
   });
 }
 
-const OUTPUT_START_MARKER = '---NANOCLAW_OUTPUT_START---';
-const OUTPUT_END_MARKER = '---NANOCLAW_OUTPUT_END---';
+const OUTPUT_START_MARKER = '---GHOSTCLAW_OUTPUT_START---';
+const OUTPUT_END_MARKER = '---GHOSTCLAW_OUTPUT_END---';
 
 function writeOutput(output: ContainerOutput): void {
   console.log(OUTPUT_START_MARKER);
@@ -432,21 +432,21 @@ async function runQuery(
         'TeamCreate', 'TeamDelete', 'SendMessage',
         'TodoWrite', 'ToolSearch', 'Skill',
         'NotebookEdit',
-        'mcp__nanoclaw__*',
+        'mcp__ghostclaw__*',
         'mcp__gmail__*',
       ],
       env: sdkEnv,
       permissionMode: 'bypassPermissions',
       allowDangerouslySkipPermissions: true,
       settingSources: ['project', 'user'],
       mcpServers: {
-        nanoclaw: {
+        ghostclaw: {
           command: 'node',
           args: [mcpServerPath],
           env: {
-            NANOCLAW_CHAT_JID: containerInput.chatJid,
-            NANOCLAW_GROUP_FOLDER: containerInput.groupFolder,
-            NANOCLAW_IS_MAIN: containerInput.isMain ? '1' : '0',
+            GHOSTCLAW_CHAT_JID: containerInput.chatJid,
+            GHOSTCLAW_GROUP_FOLDER: containerInput.groupFolder,
+            GHOSTCLAW_IS_MAIN: containerInput.isMain ? '1' : '0',
           },
         },
         gmail: {

.claude/skills/add-gmail/modify/src/container-runner.ts

@@ -24,8 +24,8 @@ import { validateAdditionalMounts } from './mount-security.js';
 import { RegisteredGroup } from './types.js';
 
 // Sentinel markers for robust output parsing (must match agent-runner)
-const OUTPUT_START_MARKER = '---NANOCLAW_OUTPUT_START---';
-const OUTPUT_END_MARKER = '---NANOCLAW_OUTPUT_END---';
+const OUTPUT_START_MARKER = '---GHOSTCLAW_OUTPUT_START---';
+const OUTPUT_END_MARKER = '---GHOSTCLAW_OUTPUT_END---';
 
 export interface ContainerInput {
   prompt: string;

.claude/skills/add-gmail/tests/gmail.test.ts

@@ -6,9 +6,9 @@ const root = process.cwd();
 const read = (f: string) => fs.readFileSync(path.join(root, f), 'utf-8');
 
 function getGmailMode(): 'tool-only' | 'channel' {
-  const p = path.join(root, '.nanoclaw/state.yaml');
+  const p = path.join(root, '.ghostclaw/state.yaml');
   if (!fs.existsSync(p)) return 'channel';
-  return read('.nanoclaw/state.yaml').includes('mode: tool-only') ? 'tool-only' : 'channel';
+  return read('.ghostclaw/state.yaml').includes('mode: tool-only') ? 'tool-only' : 'channel';
 }
 
 const mode = getGmailMode();

.claude/skills/add-heartbeat/SKILL.md

@@ -54,7 +54,7 @@ mkdir -p data/ipc/main/tasks
 cat > "data/ipc/main/tasks/heartbeat_$(date +%s).json" << 'EOF'
 {
   "type": "schedule_task",
-  "prompt": "Read $NANOCLAW_GROUP_DIR/HEARTBEAT.md (or ./HEARTBEAT.md in the current directory) and run each check listed. Only message the user if something needs attention. If everything is fine, respond with <internal>All checks passed</internal> and nothing else.",
+  "prompt": "Read $GHOSTCLAW_GROUP_DIR/HEARTBEAT.md (or ./HEARTBEAT.md in the current directory) and run each check listed. Only message the user if something needs attention. If everything is fine, respond with <internal>All checks passed</internal> and nothing else.",
   "schedule_type": "cron",
   "schedule_value": "*/30 * * * *",
   "context_mode": "isolated"

.claude/skills/add-parallel/SKILL.md

@@ -83,14 +83,14 @@ Update `container/agent-runner/src/index.ts`:
 Find the section where `mcpServers` is configured (around line 237-252):
 ```typescript
 const mcpServers: Record<string, any> = {
-  nanoclaw: ipcMcp
+  ghostclaw: ipcMcp
 };
 ```
 
 Add Parallel AI MCP servers after the nanoclaw server:
 ```typescript
 const mcpServers: Record<string, any> = {
-  nanoclaw: ipcMcp
+  ghostclaw: ipcMcp
 };
 
 // Add Parallel AI MCP servers if API key is available
@@ -122,7 +122,7 @@ allowedTools: [
   'Bash',
   'Read', 'Write', 'Edit', 'Glob', 'Grep',
   'WebSearch', 'WebFetch',
-  'mcp__nanoclaw__*',
+  'mcp__ghostclaw__*',
   'mcp__parallel-search__*',
   'mcp__parallel-task__*'
 ],
@@ -178,14 +178,14 @@ AskUserQuestion: I can do deep research on [topic] using Parallel's Task API. Th
 
 1. Create the task using `mcp__parallel-task__create_task_run`
 2. Get the `run_id` from the response
-3. Create a polling scheduled task using `mcp__nanoclaw__schedule_task`:
+3. Create a polling scheduled task using `mcp__ghostclaw__schedule_task`:
    ```
    Prompt: "Check Parallel AI task run [run_id] and send results when ready.
 
    1. Use the Parallel Task MCP to check the task status
    2. If status is 'completed', extract the results
-   3. Send results to user with mcp__nanoclaw__send_message
-   4. Use mcp__nanoclaw__complete_scheduled_task to mark this task as done
+   3. Send results to user with mcp__ghostclaw__send_message
+   4. Use mcp__ghostclaw__complete_scheduled_task to mark this task as done
 
    If status is still 'running' or 'pending', do nothing (task will run again in 30s).
    If status is 'failed', send error message and complete the task."
@@ -224,7 +224,7 @@ Build the container with updated agent runner:
 
 Verify the build:
 ```bash
-echo '{}' | docker run -i --entrypoint /bin/echo nanoclaw-agent:latest "Container OK"
+echo '{}' | docker run -i --entrypoint /bin/echo ghostclaw-agent:latest "Container OK"
 ```
 
 ### 7. Restart Service
@@ -240,8 +240,8 @@ launchctl kickstart -k gui/$(id -u)/com.ghostclaw  # macOS
 Wait 3 seconds for service to start, then verify:
 ```bash
 sleep 3
-launchctl list | grep nanoclaw  # macOS
-# Linux: systemctl --user status nanoclaw
+launchctl list | grep ghostclaw  # macOS
+# Linux: systemctl --user status ghostclaw
 ```
 
 ### 8. Test Integration
@@ -257,7 +257,7 @@ Tell the user to test:
 
 Check logs to verify MCP servers loaded:
 ```bash
-tail -20 logs/nanoclaw.log
+tail -20 logs/ghostclaw.log
 ```
 
 Look for: `Parallel AI MCP servers configured`
@@ -276,7 +276,7 @@ Look for: `Parallel AI MCP servers configured`
 
 **Task polling not working:**
 - Verify scheduled task was created: `sqlite3 store/messages.db "SELECT * FROM scheduled_tasks"`
-- Check task runs: `tail -f logs/nanoclaw.log | grep "scheduled task"`
+- Check task runs: `tail -f logs/ghostclaw.log | grep "scheduled task"`
 - Ensure task prompt includes proper Parallel MCP tool names
 
 ## Uninstalling

.claude/skills/add-slack/SKILL.md

@@ -11,7 +11,7 @@ This skill adds Slack support to NanoClaw using the skills engine for determinis
 
 ### Check if already applied
 
-Read `.nanoclaw/state.yaml`. If `slack` is in `applied_skills`, skip to Phase 3 (Setup). The code changes are already in place.
+Read `.ghostclaw/state.yaml`. If `slack` is in `applied_skills`, skip to Phase 3 (Setup). The code changes are already in place.
 
 ### Ask the user
 
@@ -27,7 +27,7 @@ Run the skills engine to apply this skill's code package. The package files are
 
 ### Initialize skills system (if needed)
 
-If `.nanoclaw/` directory doesn't exist yet:
+If `.ghostclaw/` directory doesn't exist yet:
 
 ```bash
 npx tsx scripts/apply-skill.ts --init
@@ -49,7 +49,7 @@ This deterministically:
 - Three-way merges updated routing tests into `src/routing.test.ts`
 - Installs the `@slack/bolt` npm dependency
 - Updates `.env.example` with `SLACK_BOT_TOKEN`, `SLACK_APP_TOKEN`, and `SLACK_ONLY`
-- Records the application in `.nanoclaw/state.yaml`
+- Records the application in `.ghostclaw/state.yaml`
 
 If the apply reports merge conflicts, read the intent files:
 - `modify/src/index.ts.intent.md` — what changed and invariants for index.ts
@@ -167,7 +167,7 @@ Tell the user:
 ### Check logs if needed
 
 ```bash
-tail -f logs/nanoclaw.log
+tail -f logs/ghostclaw.log
 ```
 
 ## Troubleshooting
@@ -177,7 +177,7 @@ tail -f logs/nanoclaw.log
 1. Check `SLACK_BOT_TOKEN` and `SLACK_APP_TOKEN` are set in `.env` AND synced to `data/env/env`
 2. Check channel is registered: `sqlite3 store/messages.db "SELECT * FROM registered_groups WHERE jid LIKE 'slack:%'"`
 3. For non-main channels: message must include trigger pattern
-4. Service is running: `launchctl list | grep nanoclaw`
+4. Service is running: `launchctl list | grep ghostclaw`
 
 ### Bot connected but not receiving messages
 

.claude/skills/add-slack/modify/src/config.ts

@@ -26,7 +26,7 @@ const HOME_DIR = process.env.HOME || '/Users/user';
 export const MOUNT_ALLOWLIST_PATH = path.join(
   HOME_DIR,
   '.config',
-  'nanoclaw',
+  'ghostclaw',
   'mount-allowlist.json',
 );
 export const STORE_DIR = path.resolve(PROJECT_ROOT, 'store');
@@ -35,7 +35,7 @@ export const DATA_DIR = path.resolve(PROJECT_ROOT, 'data');
 export const MAIN_GROUP_FOLDER = 'main';
 
 export const CONTAINER_IMAGE =
-  process.env.CONTAINER_IMAGE || 'nanoclaw-agent:latest';
+  process.env.CONTAINER_IMAGE || 'ghostclaw-agent:latest';
 export const CONTAINER_TIMEOUT = parseInt(
   process.env.CONTAINER_TIMEOUT || '1800000',
   10,