gnet — brand
Name
gnet — lowercase, always. "g" is silent in the ASCII banner but spoken as "gee-net". The ambiguity is intentional: it reads as both "G-net" (a network of agents) and "gnat" (small, agile, swarms).
One-liner
Multi-agent Claude Code orchestrator that lives in your terminal.
Voice
- Terse. Terminal-native. One idea per sentence.
- Technically precise. If a number is interesting, include it.
- Zero hype. No "revolutionary", no "AI-powered", no emoji in docs.
- Honest about tradeoffs. If a feature is a stub, the README says so.
Contrast with commercial agentic IDE marketing: they sell magic, gnet sells control. "Here is exactly what will happen, here is exactly what it will cost, here are the files you can inspect."
Visual tone
- Terminal: cyan prompts (
[gnet] …), purple banners for agent panes, green ok/warn, red errors. No background colors. No boxes-and-lines ASCII art beyond the banner. - GUI (
gnet gui): dark glassmorphism.#0a0a0fbackground,rgba(255,255,255,0.04)panels,backdrop-filter: blur(10px), cyan→purple gradient accents (#7dd3fc → #c084fc). No drop shadows, no skeuomorphism, no animation beyond subtle hover lifts. - Docs: plain markdown. Tables over bullet soup. Code blocks for anything the reader might copy.
Naming conventions
- Subcommands: single short English verb.
run,attach,synth,kill,resume,mcp,gui,voice,savings. No kebab-case subcommands. - Helpers:
gnet-<verb>(e.g.,gnet-ask,gnet-voice) when they ship as separate binaries. - State directory: always
.gnet/at the workdir root. Never~/.gnet. - Agent ids: short kebab-case, topic-first (
security-auditor,docs-writer,perf-sleuth). Human-readable names are title case.
What gnet is NOT
- Not "AI". gnet orchestrates Claude. Call it what it is.
- Not a platform. It is a CLI tool.
- Not a startup. It is a personal tool shared under an OSS license.
- Not a replacement for thinking. It is an amplifier for a thinking dev.