agentleFS
mcarmona1064-cellmcarmona1064-cell/clawbridge-codex/.claude/skills/add-atomic-chat-tool/SKILL.md

add-atomic-chat-tool

Skill1 starsChanged 6 months agoMITView on GitHub

Add Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.

  • Reads credentials

7 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-anydoc, add-clidash and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TomGranotSkill

    add-anydoc

    Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.

    Also in 5 projects that use this

  • TomGranotSkill

    add-clidash

    Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.

    Also in 5 projects that use this

  • qwibitaiSkill

    add-iron-proxy

    Install or refresh Iron Proxy and its official Iron Control web console for NanoClaw. Use when selecting the Iron gateway, adding its management UI, configuring credentials and grants, or restoring the proxy, approval bridge, and agent guidance.

    Also in 4 projects that use this

  • qwibitaiSkill

    add-mattermost

    Add a self-hosted or cloud Mattermost bot channel through the Chat SDK bridge, reusing a healthy server when available and linking to official server setup guidance when needed.

    Also in 4 projects that use this

  • b1rdmaniaSkill

    migrate-memory

    Migrate from monolith CLAUDE.md to the three-file memory system (identity + state + log). Non-destructive — backs up the original first.

    Also in 6 projects that use this

  • nanocoaiSkill

    add-cursor

    Use Cursor (local Agent SDK) as a full agent provider — planning, tool orchestration, MCP tools, session resume — alongside or instead of Claude. Cursor-account sign-in or API key, held by the credential gateway. Per-group via `ncl groups config update --provider cursor`. Distinct from using Cursor as a cloud agent (those run on Cursor VMs and are not this provider).

    Also in 3 projects that use this

  • +5 more from TomGranot
  • +1 more from qwibitai

The file

We split this skill into the rules it gives an agent

9 rules. 2 are common, 1 is distinctive, and 6 are very specific to this project.

  • 2

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if container/agent-runner/src/atomic-chat-mcp-stdio.ts exists.

    line 22
  2. Common:

    Verify Atomic Chat is installed and its local API server is running.

    line 26
  3. Common:

    If the request fails:

    line 32
  4. Very specific:

    Add an atomic_chat entry alongside clawbridge:

    line 62
  5. Very specific:

    Add ATOMIC_CHAT forwarding right after it:

    line 100
  6. Distinctive:

    All three must be clean before proceeding.

    line 163
  7. Very specific:

    Verify the host API is reachable: curl http://127.0.0.1:1337/v1/models

    line 224
  8. Very specific:

    Check Docker can reach the host: docker run --rm curlimages/curl curl -s http://host.docker.internal:1337/v1/models

    line 226
  9. Very specific:

    If using a custom host, check ATOMIC_CHAT_HOST in .env

    line 227

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add Atomic Chat Integration

This skill adds a stdio-based MCP server that exposes models running in the local Atomic Chat desktop app as tools for the container agent. Claude remains the orchestrator but can offload work to local models served by Atomic Chat on http://127.0.0.1:1337/v1 (OpenAI-compatible).

Tools exposed:

  • atomic_chat_list_models — list models currently available in Atomic Chat (GET /v1/models)
  • atomic_chat_generate — send a prompt to a specified model and return the response (POST /v1/chat/completions)

Model management (download, delete) is done through the Atomic Chat desktop UI — the app is a fork of Jan and manages its own model library.

The skill ships the MCP server source in this folder and copies it into the agent-runner tree at install time, then wires it up with small edits to index.ts, providers/claude.ts, and container-runner.ts. No branch merge — all edits are additive and idempotent.

Phase 1: Pre-flight

Check if already applied

Check if container/agent-runner/src/atomic-chat-mcp-stdio.ts exists. If it does, skip to Phase 3 (Configure).

Check prerequisites

Verify Atomic Chat is installed and its local API server is running. On the host:

curl -s http://127.0.0.1:1337/v1/models | head

If the request fails:

  1. Install Atomic Chat from the latest release (macOS only for now — atomic-chat.dmg).
  2. Open the app.
  3. Open Settings → Local API Server and make sure it's enabled on port 1337.
  4. Go to the Hub (or Models) tab and download at least one model (e.g. Llama 3.2 3B, Qwen 2.5 Coder 7B).
  5. Load the model once by sending any message in Atomic Chat's UI to warm it up.

Phase 2: Apply Code Changes

Copy the MCP server source

cp .claude/skills/add-atomic-chat-tool/atomic-chat-mcp-stdio.ts container/agent-runner/src/atomic-chat-mcp-stdio.ts

Register the MCP server in the agent-runner

Edit container/agent-runner/src/index.ts. Find the mcpServers object that currently looks like this:

  const mcpServers: Record<string, { command: string; args: string[]; env: Record<string, string> }> = {
    clawbridge: {
      command: 'bun',
      args: ['run', mcpServerPath],
      env: {},
    },
  };

Add an atomic_chat entry alongside clawbridge:

  const mcpServers: Record<string, { command: string; args: string[]; env: Record<string, string> }> = {
    clawbridge: {
      command: 'bun',
      args: ['run', mcpServerPath],
      env: {},
    },
    atomic_chat: {
      command: 'bun',
      args: ['run', path.join(__dirname, 'atomic-chat-mcp-stdio.ts')],
      env: {
        ...(process.env.ATOMIC_CHAT_HOST ? { ATOMIC_CHAT_HOST: process.env.ATOMIC_CHAT_HOST } : {}),
        ...(process.env.ATOMIC_CHAT_API_KEY ? { ATOMIC_CHAT_API_KEY: process.env.ATOMIC_CHAT_API_KEY } : {}),
      },
    },
  };

Add the tool glob to the allowlist

Edit container/agent-runner/src/providers/claude.ts. Find 'mcp__clawbridge__*', in the TOOL_ALLOWLIST array and add 'mcp__atomic_chat__*', on the following line:

  'mcp__clawbridge__*',
  'mcp__atomic_chat__*',
];

Forward host env vars into the container

Edit src/container-runner.ts in buildContainerArgs. Find the TZ env line:

  args.push('-e', `TZ=${TIMEZONE}`);

Add ATOMIC_CHAT forwarding right after it:

  args.push('-e', `TZ=${TIMEZONE}`);

  // Atomic Chat MCP tool: forward host overrides if set (default is host.docker.internal:1337).
  if (process.env.ATOMIC_CHAT_HOST) {
    args.push('-e', `ATOMIC_CHAT_HOST=${process.env.ATOMIC_CHAT_HOST}`);
  }
  if (process.env.ATOMIC_CHAT_API_KEY) {
    args.push('-e', `ATOMIC_CHAT_API_KEY=${process.env.ATOMIC_CHAT_API_KEY}`);
  }

Surface [ATOMIC] log lines at info level

In the same file, find the stderr logger:

  container.stderr?.on('data', (data) => {
    for (const line of data.toString().trim().split('\n')) {
      if (line) log.debug(line, { container: agentGroup.folder });
    }
  });

Replace it with:

  container.stderr?.on('data', (data) => {
    for (const line of data.toString().trim().split('\n')) {
      if (!line) continue;
      if (line.includes('[ATOMIC]')) {
        log.info(line, { container: agentGroup.folder });
      } else {
        log.debug(line, { container: agentGroup.folder });
      }
    }
  });

Add env-var stubs to .env.example

Append to .env.example:

# Atomic Chat MCP tool (.claude/skills/add-atomic-chat-tool)
# Override the host where Atomic Chat exposes its OpenAI-compatible API.
# Default: http://host.docker.internal:1337 (with fallback to localhost)
# ATOMIC_CHAT_HOST=http://host.docker.internal:1337

# Optional API key. Leave unset for a local Atomic Chat install — it does not require auth.
# ATOMIC_CHAT_API_KEY=

Validate code changes

pnpm run build
pnpm exec tsc -p container/agent-runner/tsconfig.json --noEmit
./container/build.sh

All three must be clean before proceeding.

Phase 3: Configure

Set Atomic Chat host (optional)

By default, the MCP server connects to http://host.docker.internal:1337 (Docker Desktop) with a fallback to localhost. To use a custom host, add to .env:

ATOMIC_CHAT_HOST=http://your-atomic-chat-host:1337

Set API key (optional)

Atomic Chat does not require authentication when running locally — leave this unset. Only set it if you've put Atomic Chat behind a reverse proxy that enforces auth:

ATOMIC_CHAT_API_KEY=sk-...

Restart the service

launchctl kickstart -k gui/$(id -u)/com.clawbridge  # macOS
# Linux: systemctl --user restart clawbridge

Phase 4: Verify

Test inference

Tell the user:

Send a message like: "use atomic chat to tell me the capital of France"

The agent should use atomic_chat_list_models to find available models, then atomic_chat_generate to get a response.

Check logs if needed

tail -f logs/clawbridge.log | grep -i atomic

Look for:

  • [ATOMIC] Listing models... — list request started
  • [ATOMIC] Found N models — models discovered
  • [ATOMIC] >>> Generating with <model> — generation started
  • [ATOMIC] <<< Done: <model> | Xs | N tokens | M chars — generation completed

Troubleshooting

Agent says "Atomic Chat is not installed" or tries to run a CLI

The agent is looking for a CLI that doesn't exist instead of using the MCP tools. This means:

  1. The MCP server wasn't copied — check container/agent-runner/src/atomic-chat-mcp-stdio.ts exists
  2. The MCP server wasn't registered — check container/agent-runner/src/index.ts has the atomic_chat entry in mcpServers
  3. The allowlist wasn't updated — check container/agent-runner/src/providers/claude.ts includes mcp__atomic_chat__* in TOOL_ALLOWLIST
  4. The container wasn't rebuilt — run ./container/build.sh

"Failed to connect to Atomic Chat"

  1. Verify the host API is reachable: curl http://127.0.0.1:1337/v1/models
  2. Confirm the Local API Server is enabled in Atomic Chat's settings
  3. Check Docker can reach the host: docker run --rm curlimages/curl curl -s http://host.docker.internal:1337/v1/models
  4. If using a custom host, check ATOMIC_CHAT_HOST in .env

model not found / 404 on generate

The model ID passed to atomic_chat_generate must exactly match one of the IDs returned by atomic_chat_list_models. Ask the agent to list models first, then pick one from that list.

Slow first response

Atomic Chat lazy-loads models into memory on first use. The initial call may take longer while the model warms up. Subsequent calls against the same model are fast.

Agent doesn't use Atomic Chat tools

The agent may not know about the tools. Try being explicit: "use the atomic_chat_generate tool with llama3.2-3b-instruct to answer: ..."

Context window or output size issues

Atomic Chat respects each model's native context length. If you hit limits, pass max_tokens explicitly when calling atomic_chat_generate, or switch to a model with a larger context window in the Atomic Chat UI.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.