STARNET TERMLINK OPEN SOURCE

COMING FROM OPENCLAW OR HERMES?

// your concepts map cleanly — and your existing setup keeps working

StarNet is a different shape of harness: instead of one assistant living in your chat apps, it's a station of many agents whose floor plan defines the workflow. But almost everything you already know translates directly.

Concept map

You know it asIn StarNet
Persona / soul fileThe agent dossier — personality, beliefs, goals, shaped at recruitment and evolving as you work
SkillsSkills — same idea, capability-gated by the station floor (a skill that needs an ungranted tool stays visibly dormant)
Cron jobs / heartbeatsRoutines — scheduled real runs that surface as readable sessions afterwards
Chat channelsChannels — Telegram, Discord, Slack, Matrix, and Signal (via your signal-cli bridge) connect the same way: your bot token, your server
One assistant, many contextsMany agents, one station — each with its own model, memory, desk, and tool grants, running concurrently
Config files for permissionsThe floor — placed gear grants real tools, shared by the whole crew; redraw instead of re-config
MCP serversMCP connectors — same protocol, curated catalog plus anything you run yourself

You don't have to switch

StarNet exposes an MCP stdio bridge and an OpenAI-style /v1 ingress endpoint, so the harness you already run can drive StarNet capabilities directly. Keep your daily driver; give it a station to command. Interop details in Connectors & interop.

What's genuinely different

Agent importer: the Recruitment Bay has a built-in importer that carries an existing OpenClaw or Hermes agent (persona, memory, config) into a StarNet dossier — point it at your agent's folder and it walks the rest.