ExtendPacks, themes, agents and the API

Add packs

Panes, speech models, map collections, knowledge bundles and themes all come as packs, so you add only what you use. RoachNet Apps is the catalog: pick an item, choose Install to RoachNet, and the site opens a roachnet:// install link. You don't need an account.

Settings › Packs shows what each pack is, what it touches and what removing it would leave behind. Removing a pack keeps its data unless you choose to retire it. RoachNet Apps and feature packs has the details.

Make a theme

1. Open Settings › Appearance and start from one of the 37 built-in themes or 13 snippets.

2. Change any color, font, radius, shadow, glass layer or background in the editor.

3. Export it to share it. A theme is a JSON file.

To add a theme someone sent you, import it, or drop the file into ~/RoachNet/storage/themes; RoachNet watches that folder. Themes covers theme packs and your phone.

Bring your own agents

Claude Code, Codex, Gemini CLI, OpenCode and Cursor CLI can join a company in the Org as employees. They work with the other agents through issues, comments, @mentions, sub-issues and approvals. Hire one from Org › Agents › Hire agent…, which shows whether each CLI is installed and signed in.

RoachNet runs the CLI you installed, signed in the way you signed it in, and never reads, copies or stores your account's credentials. Each agent gets an access level, and Full is something you opt in to for each agent. Only Claude Code and Codex were run live for 1.1; the other three were built to each tool's documented interface. The Org has the access levels.

If you pay for a Claude or ChatGPT plan, RoachNet can also offer it as a model, through your signed-in Claude Code or Codex CLI. See Plans as models.

Point your tools at your models

The model server answers the Ollama, OpenAI and Anthropic APIs on 127.0.0.1:36434. A tool that already talks to one of them can use your Mac's models when you change its address. Use RoachNet with Ollama, OpenAI and Anthropic clients has an example for each.

Script the local API

The local API covers the rest: the Vault, Maps, packs, the Org, traces and the runtime itself.

1. Read the runtime's address from the runtime state file. Find the port and token has the lines to paste.

2. Make a RoachClaw API token in Settings › RoachClaw, scoped to chat, read or admin, and send it as Authorization: Bearer …. You can revoke it there. Since 1.1.3 the launch token stays in the runtime's memory, so no script can read it from a file.

3. Look up the route you need in the route browser. Each route has its request, its response and a curl you can paste.

Related

• The local API
• RoachTrace traces every Org run and model call, so you can see what an agent did.
• Brand and design, if you're making something that carries the roach.