tykimos/agent-native-agent/ana

Attach ANA to your service

ANA turns any web app into one you operate by watching + talking: a coding agent runs inside a tmux pane; the browser sends chat that ANA injects into that pane, and mirrors the session (agent replies, tool activity, busy state) back to the page — no MCP, no bridge, no hooks. The entire runtime is one dependency-free file: `channel-core.js`.

The whole idea (2 pieces)

[your web page] ──POST /api/chat──► server ──paste-buffer + Enter──► [tmux pane: claude / any agent]
      ▲                               │                                     │
      └── SSE /api/stream ◄───────────┘  300ms capture-pane → parse → ledger (auto-mirror)

1. A server that mounts channel-core.js and serves your HTML.
2. A tmux session running a coding-agent CLI (claude, or any).

Attach in 3 steps (very simple)

1. Copy `channel-core.js` into your project (it is dependency-free, Node ≥ 20 + tmux).

2. Mount it — add ~12 lines to (or beside) your server:

const path = require('node:path');
const core = require('./channel-core.js');
const app = core.createChannelServer({
  PORT: 8809, BIND: '127.0.0.1',
  SESSION: core.defaultSession(__dirname, process.env),   // TMUX_SESSION || <ANA name>-claude
  SOCKET: process.env.TMUX_SOCKET || '',          // default tmux socket
  TARGET: core.resolveTarget(__dirname, process.env),
  FEED_FILE: path.join(__dirname, '.ana', 'transcript.jsonl'),
  SERVABLE: new Set(['index.html']),              // your dashboard file(s)
  defaultDoc: 'index.html',
  autoConfigPane: true,                            // sets alternate-screen off on connect
});
app.listen(() => console.log('ANA → http://localhost:8809'));

3. Add the chat widget to your page — send with POST /api/chat {text} and stream with GET /api/stream (SSE). Minimal client:

<script>
  const es = new EventSource('/api/stream');
  es.onmessage = (e) => { const d = JSON.parse(e.data); /* d.kind: snapshot|commit|pending|status|screen|draft */ };
  function send(text) { fetch('/api/chat', { method:'POST', headers:{'content-type':'application/json'}, body: JSON.stringify({ text, force: true }) }); }
</script>

Run

tmux new -s base-ana-claude   # inside it, start your agent:  claude
node server.js                # → http://localhost:8809 , open in a browser

Session name = <ANA name>-claude. The ANA name is your project folder when it is <xxx>-ana (e.g. ~/ana/shop-ana → shop-ana-claude), otherwise base-ana. The chat's session list shows only <ANA name>-<yyy> sessions (-codex, -review, …); ANA_NAME, TMUX_SESSION and ANA_TMUX_ALL=1 override.

That's it — type in the page, the agent answers in the page.

What channel-core gives you (the API)

Sessions. Every tmux session (target) gets its own ledger (.ana/transcripts/<target>.jsonl; the default session keeps .ana/transcript.jsonl), poll loop, SSE subscribers and injection queue. A request's session is: x-ana-target header or ?target= (explicit, e.g. for the agent's own curl) → the person's most recent pick (.ana/targets.json, keyed by the userKey(req) hook — the identity header in the ANA base) → the default TARGET. Switching sessions swaps the whole chat history, and each signed-in person lands on the session they used last.

Rich responses (optional)

Plain replies mirror automatically. For preview + approve cards, the agent posts POST /api/agent {text, diff, why?, ask?, effect?, ifNot?} (the plain fields show on the approval card — what's going on, what's asked, what it changes, what if not; without them the card says how many items it adds, changes and removes); your server applies the diff on approval and bumps a version so every device re-syncs. See dashboard-api.js in the ANA base for the todo/schedule/memo/evolve reference implementation.

Safety notes (already built in)

• Server binds 127.0.0.1 by default — a coding agent has tool-execution power, so never expose it unauthenticated (BIND=0.0.0.0 is opt-in for trusted networks only).
• /api/chat//api/keys require content-type: application/json + same-origin (CSRF guard). Only SERVABLE files are served.
• Injection is refused when the pane is a shell (agent exited) or a TUI dialog is open — surface health.dialog in your UI so the user can respond with /api/keys.

Full reference app (dashboard with ANA mode, context chips, docked chat, evolution tab): the repository root. Run it, then copy the parts you want.