ticlawk 0.1.12-dev.0

package/LICENSE

@@ -0,0 +1,15 @@
+ISC License
+
+Copyright (c) 2026 ticlawk
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
+REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
+AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
+INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
+LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
+OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+PERFORMANCE OF THIS SOFTWARE.

package/README.md

@@ -0,0 +1,426 @@
+# ticlawk
+
+[![npm version](https://img.shields.io/npm/v/ticlawk)](https://www.npmjs.com/package/ticlawk)
+
+**Connect any agent harness to any mobile client.**
+
+*M agent harnesses × N mobile clients used to be M×N integrations. ticlawk makes it M+N.*
+
+You run the harness locally — Claude Code, Codex, OpenClaw, whatever you're
+testing this week. `ticlawk` is the layer that lets any of them talk
+through any mobile/web client you like to use (Telegram,
+[ticlawk](https://ticlawk.com), more to come). 
+
+<p align="center">
+  <img src="assets/ticlawk-concept.svg" alt="ticlawk connects any client to any agent" width="860">
+</p>
+
+Left side: any agent harness that runs on your machine.
+Middle: `ticlawk`.
+Right side: any mobile or web app you like to use to manage your agent.
+
+---
+
+## Quickstart — Telegram in 5 minutes
+
+This is the fastest way to see it work. You need a Telegram bot token from
+[@BotFather](https://t.me/BotFather) and a project directory on this machine
+where Claude Code can run.
+
+```bash
+# 1. install
+curl -fsSL https://raw.githubusercontent.com/darthjaja6/ticlawk/main/install.sh | bash
+
+# 2. choose Telegram as the active adapter
+ticlawk config set adapter telegram
+
+# 3. store Telegram auth locally
+ticlawk auth telegram --bot-token <your-bot-token>
+
+# 4. restart the daemon so it starts polling the bot
+# Linux
+systemctl --user restart ticlawk
+
+# macOS
+launchctl kickstart -k gui/$(id -u)/ticlawk
+
+# 5. connect that bot to a Claude Code project
+ticlawk connect --adapter telegram --workdir /path/to/project
+
+# optional: if you want to resume an existing Claude Code session instead,
+# add --session-id <claude-session-id>
+
+# 6. say hi to your bot on Telegram — the first DM becomes the bot's only chat
+```
+
+`--workdir` is the important part. `ticlawk` binds the adapter to a local
+project directory and runtime. `--session-id` is optional: use it only when you
+want to resume an existing Claude Code or Codex conversation instead of letting
+the next message create a fresh session automatically.
+
+**Finding `<claude-session-id>`** — if you want to resume, use the filename
+(without `.jsonl`) of the transcript under `~/.claude/projects/**/`. Pick the
+one whose working directory matches the project you want the bot to work on.
+
+If `hello` in Telegram comes back as a reply from that Claude Code session,
+you're done. Everything below is for when you want ticlawk, Codex, OpenClaw,
+or more control.
+
+> ⚠️ **Single user, by design.** The Telegram bot binds to the **first** private
+> DM that messages it, and refuses everyone else. This is not a bug — it's the
+> security boundary. The bot can run shell commands and edit files in your
+> project; locking it to one chat keeps that capability where you intended.
+> Don't add the bot to groups, and don't share its token.
+
+---
+
+## Using ticlawk instead of Telegram
+
+If you want the [ticlawk mobile app](https://ticlawk.com) instead, connect from
+the project directory and scan the QR code with ticlawk. `ticlawk` will
+detect local runtimes in that directory, and ticlawk will ask you which one to
+connect:
+
+```bash
+cd /path/to/project
+ticlawk connect
+```
+
+Full walkthrough: [docs/clients/ticlawk.md](docs/clients/ticlawk.md).
+Telegram details: [docs/clients/telegram.md](docs/clients/telegram.md).
+
+---
+
+## Using Codex, OpenClaw, or opencode instead of Claude Code
+
+Keep the same two-step adapter flow:
+
+1. `ticlawk auth <adapter> ...`
+2. `ticlawk connect --adapter <adapter> ...`
+
+Then swap the runtime locator with `--type`:
+
+```bash
+# Telegram + Codex
+ticlawk connect --adapter telegram --type codex --workdir /path/to/project
+
+# ticlawk + Codex, when you want to bypass mobile runtime selection
+ticlawk connect --adapter ticlawk --type codex --workdir /path/to/project
+
+# Telegram + OpenClaw
+ticlawk connect --adapter telegram --type openclaw --agent-id main
+
+# ticlawk + OpenClaw
+ticlawk connect --adapter ticlawk --type openclaw --agent-id main
+
+# Telegram + opencode
+ticlawk connect --adapter telegram --type opencode --workdir /path/to/project
+
+# ticlawk + opencode, when you want to bypass mobile runtime selection
+ticlawk connect --adapter ticlawk --type opencode --workdir /path/to/project
+```
+
+Runtime locators at a glance:
+
+| Runtime     | Required       | Optional resume handle | Where to find it                                              |
+|-------------|----------------|------------------------|---------------------------------------------------------------|
+| Claude Code | `--workdir`    | `--session-id`         | filename of `~/.claude/projects/**/*.jsonl` (without `.jsonl`)|
+| Codex       | `--workdir`    | `--session-id`         | `payload.id` in the first `session_meta` record of `~/.codex/sessions/**/*.jsonl` |
+| OpenClaw    | `--agent-id`   | none                   | logical agent name (`main` by default)                        |
+| opencode    | `--workdir`    | `--session-id` (with `--workdir`) | `.id` from `opencode session list --format json` (run inside the project dir) |
+
+[OpenClaw](https://github.com/openclaw/openclaw) is an open-source local-first
+agent runtime; skip this row if you don't use it.
+
+OpenClaw has built-in channels; use `ticlawk` only if you want a single
+chat surface across Claude Code, Codex, OpenClaw, and opencode.
+
+[opencode](https://opencode.ai) is provider-agnostic — it doesn't carry its own
+account system. Before connecting through `ticlawk`, install the CLI
+(`npm i -g opencode-ai`) and authenticate it once against the LLM provider
+you want it to use (`opencode auth login`, then pick Anthropic / OpenAI /
+Google / OpenRouter / etc. and paste the corresponding API key). Model
+selection lives in opencode's own config (`opencode.json` in the project
+root, or user-level config) — `ticlawk` does not pass `--model`.
+
+`ticlawk` spawns opencode with `--dangerously-skip-permissions`
+(matching how Codex is wired), so chat messages can drive shell commands and
+file edits in the bound `--workdir` without further confirmation prompts.
+This is the same security boundary documented above; only connect a workdir
+you trust to a chat you control.
+
+---
+
+## `auth` vs `connect`
+
+You only need to know this once:
+
+- **`auth`** — store adapter-specific setup input locally.
+  Telegram takes `--bot-token`. ticlawk uses QR pairing from `connect`.
+- **`connect`** — connect the selected adapter to a local runtime.
+  For ticlawk, `ticlawk connect` auto-detects local runtimes and
+  lets you pick in the mobile app. Use `--workdir` for Telegram or explicit
+  ticlawk runtime selection, optionally add `--session-id` to resume, or use
+  `--agent-id` for OpenClaw.
+
+`auth` is adapter-specific by subcommand shape:
+- `ticlawk auth telegram --bot-token ...`
+
+That keeps adapter auth flags scoped to the adapter without making users learn
+the `--` passthrough convention.
+
+---
+
+## Daily use
+
+After setup, the usual workflow is simple:
+
+- Keep `ticlawk` running as a user service. If Linux prints an
+  `Action required` message during install or connect, run the command it
+  shows so the daemon keeps running after logout and reboot.
+- Keep using the same Telegram chat or ticlawk channel. The adapter auth and
+  channel binding stay on disk until you change them.
+- If you want to have the work done just like tiktoking, run
+  `ticlawk connect ...` again with the new `--workdir`.
+- If you want to resume an existing Claude Code or Codex conversation, add
+  `--session-id`; otherwise the next message creates a fresh session.
+- If an OpenClaw agent changes, reconnect with the new `--agent-id`.
+- If replies stop because the local runtime session ended, run `connect` again
+  or reset the session from the client UI.
+- `ticlawk health` is the first thing to check when something feels off.
+
+---
+
+## Verifying and troubleshooting
+
+```bash
+ticlawk health
+```
+
+- `ok: true` and the adapter-specific fields populated → you're good.
+- Can't reach `127.0.0.1:8741` → the daemon isn't running. Start it with
+  `systemctl --user restart ticlawk`,
+  `launchctl kickstart -k gui/$(id -u)/ticlawk`, or `ticlawk start`.
+- Telegram shows `runtimeConnected: true` and `connectedChat: false` →
+  send the first DM to the bot to claim its only chat.
+- Telegram shows `botConfigured: false` → rerun
+  `ticlawk auth telegram --bot-token ...`, then restart the daemon.
+- ticlawk shows `apiKey: false` → rerun `ticlawk connect`
+  from the project directory and scan the QR code.
+
+Logs:
+
+```bash
+tail -f ~/.ticlawk/ticlawk.log         # normal output
+tail -f ~/.ticlawk/ticlawk-crash.log   # crashes, signals, exit diagnostics
+```
+
+---
+
+## What the installer does
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/darthjaja6/ticlawk/main/install.sh | bash
+```
+
+It expects local `node` and `npm`, then:
+
+- installs or updates the npm package with `npm install -g ticlawk`
+- creates `~/.ticlawk/` for config and logs
+- installs a user-level service — systemd on Linux, launchd on macOS — so the
+  daemon restarts automatically
+
+On Linux, if systemd linger is off, the installer prints:
+
+```text
+Action required
+
+ticlawk may stop when you log out because systemd linger is off.
+
+Run this command to keep it running after logout and reboot:
+  sudo loginctl enable-linger <user>
+```
+
+Prefer not to `curl | bash`? Install with npm, then connect from the project
+directory you want the agent to use:
+
+```bash
+npm install -g ticlawk
+ticlawk connect
+```
+
+`connect` saves the pairing and refreshes the background service. If Linux
+systemd linger is off, it prints the same `Action required` message shown by
+the installer.
+
+Update with `ticlawk update`. To remove the service and legacy managed
+install files while keeping `~/.ticlawk` config, bindings, profiles, and
+logs:
+
+```bash
+ticlawk uninstall
+```
+
+That removes:
+
+- legacy `~/.local/share/ticlawk`
+- legacy `~/.local/bin/ticlawk`
+- `~/.config/systemd/user/ticlawk.service` (Linux)
+- `~/Library/LaunchAgents/ticlawk.plist` (macOS)
+
+`~/.ticlawk` is preserved. Use `npm uninstall -g ticlawk` to remove
+the npm package itself.
+
+---
+
+## Config
+
+Config lives in `~/.ticlawk/.config`. Most people only need to set
+`adapter`, then use `auth` for adapter-specific setup. The dotted
+credential keys below still exist for manual or advanced setups.
+
+```bash
+ticlawk config                              # show current config
+ticlawk config set adapter telegram         # or: ticlawk
+ticlawk auth telegram --bot-token <t>
+ticlawk config set telegram.bot-token <t>   # advanced/manual override
+ticlawk config set ticlawk.connector-api-key <k> # advanced/manual override
+ticlawk config set ticlawk.connector-ws-url <url> # advanced/manual override
+ticlawk config set streaming off            # disable streaming output globally
+ticlawk config set streaming.codex on       # force streaming on for codex only
+ticlawk config set streaming.codex default  # clear the codex override; inherit the global setting
+```
+
+Key mapping (for anyone editing the file directly):
+
+| Config key            | Env var              |
+|-----------------------|----------------------|
+| `adapter`             | `AF_ADAPTER`         |
+| `telegram.bot-token`  | `TELEGRAM_BOT_TOKEN` |
+| `ticlawk.connector-api-key` | `TICLAWK_CONNECTOR_API_KEY` |
+| `ticlawk.api-url`     | `TICLAWK_API_URL`    |
+| `ticlawk.connector-ws-url` | `TICLAWK_CONNECTOR_WS_URL` |
+
+Streaming defaults to on. Full CLI reference: `ticlawk help`.
+
+---
+
+## CLI reference
+
+<!-- usage:start -->
+```text
+ticlawk
+
+Usage:
+  ticlawk help
+  ticlawk help <command>
+  ticlawk start
+  ticlawk health
+  ticlawk config
+  ticlawk config get <adapter|streaming...|runtimes.claude_code.path|runtimes.codex.path|runtimes.opencode.path|runtimes.pi.path|telegram.bot-token|ticlawk.connector-api-key|ticlawk.api-url|ticlawk.connector-ws-url>
+  ticlawk config set <adapter|streaming...|runtimes.claude_code.path|runtimes.codex.path|runtimes.opencode.path|runtimes.pi.path|telegram.bot-token|ticlawk.connector-api-key|ticlawk.api-url|ticlawk.connector-ws-url> <value>
+  ticlawk auth <adapter> [adapter-auth-args...]
+  ticlawk connect [ticlawk] [codex|claude|opencode|openclaw|pi] [runtime args...]
+  ticlawk connect [--adapter <adapter>] [--session-id <id>] --workdir <dir> [--switch-user]
+  ticlawk connect [--adapter <adapter>] --type codex [--session-id <id>] --workdir <dir> [--name <name>] [--runtime-path <path>] [--switch-user]
+  ticlawk connect [--adapter <adapter>] --type openclaw --agent-id <id> [--name <name>] [--runtime-path <path>] [--switch-user]
+  ticlawk connect [--adapter <adapter>] --type opencode [--session-id <id>] --workdir <dir> [--name <name>] [--runtime-path <path>] [--switch-user]
+  ticlawk connect [--adapter <adapter>] --type pi [--session-id <id>] --workdir <dir> [--name <name>] [--runtime-path <path>] [--switch-user]
+  ticlawk profile list
+  ticlawk profile current
+  ticlawk profile use ticlawk:<user-id>
+  ticlawk install-daemon
+  ticlawk update [-y]
+  ticlawk uninstall [-y]
+  ticlawk version
+
+Commands:
+  auth     store adapter-specific auth/setup input locally
+  connect  connect the selected adapter to a local runtime
+  profile  list or switch saved local identities
+  install-daemon  install or refresh the background daemon
+  update   update the npm package and refresh the daemon
+  uninstall  remove service and legacy install files, preserving ~/.ticlawk
+
+Config examples:
+  ticlawk config get adapter
+  ticlawk config set adapter telegram
+  ticlawk config set adapter ticlawk
+  ticlawk config set streaming off                    # turn streaming off for all runtimes
+  ticlawk config set streaming.codex default          # clear the codex-specific override and inherit the global streaming setting
+  ticlawk config set runtimes.claude_code.path /path/to/claude_code # advanced/manual
+  ticlawk config set runtimes.codex.path /path/to/codex # advanced/manual
+  ticlawk config set runtimes.opencode.path /path/to/opencode # advanced/manual
+  ticlawk config set runtimes.pi.path /path/to/pi # advanced/manual
+  ticlawk config set telegram.bot-token <bot-token>   # advanced/manual
+  ticlawk config set ticlawk.connector-api-key <key>   # advanced/manual
+  ticlawk config set ticlawk.api-url <api-url>        # advanced/manual
+  ticlawk config set ticlawk.connector-ws-url <url>   # advanced/manual
+
+Examples:
+  ticlawk connect
+  ticlawk connect ticlawk
+  ticlawk connect ticlawk codex
+  ticlawk connect ticlawk openclaw --agent-id main
+  ticlawk auth telegram --bot-token <bot-token>
+  ticlawk connect --adapter telegram --workdir /path/to/project
+  ticlawk connect --adapter telegram --session-id <claude-session-id>
+  ticlawk connect --adapter telegram --type codex --workdir /path/to/project
+  ticlawk connect --adapter telegram --type openclaw --agent-id main
+  ticlawk connect --adapter telegram --type opencode --workdir /path/to/project
+  ticlawk connect --adapter telegram --type pi --workdir /path/to/project
+```
+<!-- usage:end -->
+
+---
+
+## Security model
+
+This is the part to read before you set anything up.
+
+- **The bot can run code on your machine.** Whatever Claude Code / Codex /
+  OpenClaw can do in the bound `--workdir`, the chat client can ask it to do.
+  Treat the chat as you'd treat a shell.
+- **Single chat, single user.** The Telegram adapter binds to the first private
+  DM and rejects all others. The ticlawk adapter binds to one channel per
+  connect. Don't share bot tokens or connector credentials.
+- **Secrets stay local.** Bot tokens, ticlawk API keys, and binding metadata
+  live in `~/.ticlawk/.config` (mode `0600`) and never leave your
+  machine. The daemon listens on `127.0.0.1:8741` only — it does not bind to
+  any external interface.
+- **Token leak = remote shell.** If your Telegram bot token leaks, anyone with
+  it can take over the bot and start a chat as the first DM. Rotate via
+  [@BotFather](https://t.me/BotFather) immediately. Same applies to a leaked
+  ticlawk connector API key — revoke it from the ticlawk app.
+- **No telemetry.** `ticlawk` does not send analytics or usage data
+  anywhere. The only outbound traffic is to Telegram (when the telegram
+  adapter is active) or to your configured ticlawk API URL (default
+  `ticlawk.com`, when the ticlawk adapter is active).
+
+---
+
+## How it works
+
+1. You send a message in Telegram or ticlawk.
+2. The adapter delivers it to the local `ticlawk` daemon.
+3. The daemon routes it into the bound Claude Code / Codex / OpenClaw session
+   on your machine.
+4. The runtime replies; `ticlawk` captures the output (including
+   streaming tokens and supported artifacts).
+5. The reply goes back through the adapter to the same chat.
+
+For ticlawk inbound delivery, `ticlawk` keeps a WebSocket connection to
+the ticlawk connector wake endpoint. Wake events such as `jobs.available` and
+`bindings.changed` do not include message text, media, or task payloads. On wake,
+the local daemon uses the existing HTTP APIs to claim pending jobs and refresh
+channel bindings. The durable queue and `claim-pending` API remain the only
+ownership boundary. By default the wake endpoint is
+`wss://edge.ticlawk.com/functions/v1/connector-wake`; override it with
+`ticlawk.connector-ws-url` only for local development or advanced setups.
+Low-frequency recovery audits still run so a missed wake or reconnect window
+does not strand durable jobs; they stay slow and do not speed up when the wake
+connection is disconnected.
+
+The daemon owns the binding — which adapter target talks to which local
+runtime, and the metadata needed to resume that runtime later. Adapters own
+their own authentication. That's the whole architecture.

package/agent-freeway.mjs

@@ -0,0 +1,2 @@
+// Legacy module alias kept so direct local imports can survive the rename.
+export * from './ticlawk.mjs';

package/assets/ticlawk-concept.svg

@@ -0,0 +1,137 @@
+<svg width="960" height="520" viewBox="0 0 960 520" fill="none" xmlns="http://www.w3.org/2000/svg" role="img" aria-labelledby="title desc">
+  <title id="title">ticlawk connects any client to any agent</title>
+  <desc id="desc">A hub-and-spoke diagram with clients on the left, ticlawk in the center, and agent runtimes on the right.</desc>
+
+  <defs>
+    <linearGradient id="hub" x1="372" y1="162" x2="588" y2="378" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#1D4ED8"/>
+      <stop offset="0.52" stop-color="#0F766E"/>
+      <stop offset="1" stop-color="#7C2D12"/>
+    </linearGradient>
+    <linearGradient id="clientLine" x1="180" y1="72" x2="460" y2="260" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#2563EB"/>
+      <stop offset="1" stop-color="#0F766E"/>
+    </linearGradient>
+    <linearGradient id="agentLine" x1="500" y1="260" x2="780" y2="448" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#0F766E"/>
+      <stop offset="1" stop-color="#C2410C"/>
+    </linearGradient>
+    <filter id="shadow" x="-20%" y="-20%" width="140%" height="140%" color-interpolation-filters="sRGB">
+      <feDropShadow dx="0" dy="10" stdDeviation="16" flood-color="#0F172A" flood-opacity="0.12"/>
+    </filter>
+    <style>
+      .label { fill: #0f172a; font-family: ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; font-weight: 700; font-size: 16px; }
+      .small { fill: #475569; font-family: ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; font-weight: 600; font-size: 13px; }
+      .hubText { fill: white; font-family: ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; font-weight: 800; font-size: 27px; }
+      .hubSub { fill: #E0F2FE; font-family: ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; font-weight: 650; font-size: 13px; letter-spacing: 0.08em; }
+      .caption { fill: #334155; font-family: ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; font-weight: 650; font-size: 14px; }
+      .node { fill: #FFFFFF; stroke: #CBD5E1; stroke-width: 1.4; }
+      .dot { fill: #F8FAFC; stroke: #CBD5E1; stroke-width: 1.4; }
+    </style>
+  </defs>
+
+  <rect width="960" height="520" rx="22" fill="#F8FAFC"/>
+  <rect x="24" y="24" width="912" height="472" rx="18" fill="#FFFFFF" stroke="#E2E8F0"/>
+
+  <text x="180" y="64" text-anchor="middle" class="caption">Any client surface</text>
+  <text x="780" y="64" text-anchor="middle" class="caption">Any agent runtime</text>
+
+  <path d="M230 116 C310 126 350 166 405 215" stroke="url(#clientLine)" stroke-width="4" stroke-linecap="round"/>
+  <path d="M230 188 C310 192 354 216 405 244" stroke="url(#clientLine)" stroke-width="4" stroke-linecap="round"/>
+  <path d="M230 260 C306 260 348 260 405 260" stroke="url(#clientLine)" stroke-width="4" stroke-linecap="round"/>
+  <path d="M230 332 C310 328 354 304 405 276" stroke="url(#clientLine)" stroke-width="4" stroke-linecap="round"/>
+  <path d="M230 404 C310 394 350 354 405 305" stroke="url(#clientLine)" stroke-width="4" stroke-linecap="round"/>
+
+  <path d="M555 215 C610 166 650 126 730 116" stroke="url(#agentLine)" stroke-width="4" stroke-linecap="round"/>
+  <path d="M555 244 C606 216 650 192 730 188" stroke="url(#agentLine)" stroke-width="4" stroke-linecap="round"/>
+  <path d="M555 260 C612 260 654 260 730 260" stroke="url(#agentLine)" stroke-width="4" stroke-linecap="round"/>
+  <path d="M555 276 C606 304 650 328 730 332" stroke="url(#agentLine)" stroke-width="4" stroke-linecap="round"/>
+  <path d="M555 305 C610 354 650 394 730 404" stroke="url(#agentLine)" stroke-width="4" stroke-linecap="round"/>
+
+  <g filter="url(#shadow)">
+    <rect x="70" y="88" width="160" height="56" rx="8" class="node"/>
+    <circle cx="100" cy="116" r="14" fill="#DBEAFE"/>
+    <path d="M94 116h12M100 110v12" stroke="#2563EB" stroke-width="2.4" stroke-linecap="round"/>
+    <text x="124" y="112" class="label">Telegram</text>
+    <text x="124" y="130" class="small">chat bot</text>
+
+    <rect x="70" y="160" width="160" height="56" rx="8" class="node"/>
+    <circle cx="100" cy="188" r="14" fill="#CCFBF1"/>
+    <rect x="94" y="180" width="12" height="16" rx="3" stroke="#0F766E" stroke-width="2.2"/>
+    <path d="M98 202h4" stroke="#0F766E" stroke-width="2.2" stroke-linecap="round"/>
+    <text x="124" y="184" class="label">ticlawk</text>
+    <text x="124" y="202" class="small">mobile app</text>
+
+    <rect x="70" y="232" width="160" height="56" rx="8" class="node"/>
+    <circle cx="100" cy="260" r="14" fill="#FDE68A"/>
+    <path d="M92 256h16M92 262h16M100 252v16" stroke="#A16207" stroke-width="2" stroke-linecap="round"/>
+    <text x="124" y="256" class="label">Web UI</text>
+    <text x="124" y="274" class="small">browser</text>
+
+    <rect x="70" y="304" width="160" height="56" rx="8" class="node"/>
+    <circle cx="100" cy="332" r="14" fill="#EDE9FE"/>
+    <path d="M94 326l6 6-6 6M102 338h6" stroke="#6D28D9" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round"/>
+    <text x="124" y="328" class="label">CLI</text>
+    <text x="124" y="346" class="small">terminal</text>
+
+    <rect x="70" y="376" width="160" height="56" rx="8" class="node"/>
+    <circle cx="100" cy="404" r="14" fill="#FFE4E6"/>
+    <path d="M94 398h12v12H94z" stroke="#BE123C" stroke-width="2.2" stroke-linejoin="round"/>
+    <path d="M97 395h6M97 413h6" stroke="#BE123C" stroke-width="2.2" stroke-linecap="round"/>
+    <text x="124" y="400" class="label">Custom app</text>
+    <text x="124" y="418" class="small">your surface</text>
+  </g>
+
+  <g filter="url(#shadow)">
+    <rect x="730" y="88" width="160" height="56" rx="8" class="node"/>
+    <circle cx="760" cy="116" r="14" fill="#FEF3C7"/>
+    <path d="M753 121l7-12 7 12M756 117h8" stroke="#B45309" stroke-width="2.2" stroke-linecap="round" stroke-linejoin="round"/>
+    <text x="784" y="112" class="label">Claude Code</text>
+    <text x="784" y="130" class="small">project agent</text>
+
+    <rect x="730" y="160" width="160" height="56" rx="8" class="node"/>
+    <circle cx="760" cy="188" r="14" fill="#DBEAFE"/>
+    <path d="M754 188a6 6 0 1 1 12 0a6 6 0 1 1-12 0" stroke="#1D4ED8" stroke-width="2.2"/>
+    <path d="M760 176v4M760 196v4M748 188h4M768 188h4" stroke="#1D4ED8" stroke-width="2.2" stroke-linecap="round"/>
+    <text x="784" y="184" class="label">Codex</text>
+    <text x="784" y="202" class="small">coding agent</text>
+
+    <rect x="730" y="232" width="160" height="56" rx="8" class="node"/>
+    <circle cx="760" cy="260" r="14" fill="#CCFBF1"/>
+    <path d="M752 260h16M760 252v16M755 255l10 10M765 255l-10 10" stroke="#0F766E" stroke-width="2" stroke-linecap="round"/>
+    <text x="784" y="256" class="label">OpenClaw</text>
+    <text x="784" y="274" class="small">local runtime</text>
+
+    <rect x="730" y="304" width="160" height="56" rx="8" class="node"/>
+    <circle cx="760" cy="332" r="14" fill="#FCE7F3"/>
+    <path d="M752 332c3-8 13-8 16 0c-3 8-13 8-16 0Z" stroke="#BE185D" stroke-width="2.2"/>
+    <circle cx="760" cy="332" r="3" fill="#BE185D"/>
+    <text x="784" y="328" class="label">opencode</text>
+    <text x="784" y="346" class="small">provider agnostic</text>
+
+    <rect x="730" y="376" width="160" height="56" rx="8" class="node"/>
+    <circle cx="760" cy="404" r="14" fill="#E0E7FF"/>
+    <path d="M754 398h12v12h-12zM751 401h3M766 401h3M751 407h3M766 407h3" stroke="#4338CA" stroke-width="2" stroke-linejoin="round"/>
+    <text x="784" y="400" class="label">Custom agent</text>
+    <text x="784" y="418" class="small">your harness</text>
+  </g>
+
+  <g filter="url(#shadow)">
+    <circle cx="480" cy="260" r="118" fill="url(#hub)"/>
+    <circle cx="480" cy="260" r="86" fill="#FFFFFF" fill-opacity="0.12" stroke="#FFFFFF" stroke-opacity="0.32" stroke-width="1.5"/>
+    <circle cx="480" cy="260" r="52" fill="#FFFFFF" fill-opacity="0.16" stroke="#FFFFFF" stroke-opacity="0.38" stroke-width="1.4"/>
+
+    <circle cx="480" cy="176" r="8" class="dot"/>
+    <circle cx="548" cy="212" r="8" class="dot"/>
+    <circle cx="548" cy="308" r="8" class="dot"/>
+    <circle cx="480" cy="344" r="8" class="dot"/>
+    <circle cx="412" cy="308" r="8" class="dot"/>
+    <circle cx="412" cy="212" r="8" class="dot"/>
+    <path d="M480 184v152M420 216l120 88M540 216l-120 88" stroke="#FFFFFF" stroke-opacity="0.65" stroke-width="2.6" stroke-linecap="round"/>
+
+    <text x="480" y="253" text-anchor="middle" class="hubText">ticlawk</text>
+    <text x="480" y="281" text-anchor="middle" class="hubSub">UNIVERSAL ROUTER</text>
+  </g>
+
+  <text x="480" y="465" text-anchor="middle" class="small">Bind sessions, relay streams, keep every side replaceable.</text>
+</svg>

package/bin/agent-freeway.mjs

@@ -0,0 +1,4 @@
+#!/usr/bin/env node
+
+// Legacy CLI alias kept so existing automation can survive the package rename.
+import './ticlawk.mjs';