Personal AI command center, memory engine, voice runtime, and cross-harness agent operating layer.
Running more than one coding agent is now normal. Starlight builds the layer that keeps them coherent: one cockpit, one configuration, one memory, one voice, and an evaluation harness that checks the parts still work together after every change.
Website starlightintelligence.ai · Protocol starlightintelligence.org/protocol · Sister orgs Starlight Systems · Arcanea Labs · GenCreator · FrankX
| Repository | What it does |
|---|---|
| starlight-voice | Personal voice operator: Tauri tray, Pipecat sidecar, push-to-talk with a sub-800 ms hot path. |
| starlight-design-intelligence | Brand packs, motion systems, and interface review doctrine for FrankX, Starlight, and Arcanea. |
| starlight-agent-skills | Portable substrate skills for Claude Code, Codex, Cursor, Gemini, and OpenCode. |
| starlight-evals | Evaluation harness for models, memory, retrieval, and multi-agent routing. |
| starlight-technology | Hardware sizing, local inference benchmarks, and buying intelligence for AI-native teams. |
| marketing-intelligence | Agentic marketing system: content, search, and distribution patterns with worked examples. |
The cockpit, kernel, agent configuration, and memory routing are private while they mature. Each public repository above is usable without the private layer.
flowchart LR
CC["starlight-command-center<br/>Operator cockpit"] --> AC["starlight-agent-config<br/>Cross-harness rules & hooks"]
CC --> MV["starlight-voice<br/>Real-time voice operator"]
AC --> SM["starlight-memory<br/>Memory routing & recall"]
AC --> SK["starlight-agent-skills<br/>Portable substrate skills"]
SM --> SE["starlight-evals<br/>Whole-system evaluation"]
DI["starlight-design-intelligence<br/>Brand packs & UI tokens"] --> CC
# Memory provider contract and CLI
npm install @starlight-intelligence/memory
# Run the evaluation harness
git clone https://github.com/Starlight-Intelligence/starlight-evals.git
cd starlight-evals && npm install && npm testEvery repository in this org follows the Starlight estate contract:
- Draft-first pull requests. A pull request starts as a draft and is marked ready when its checks pass.
- Independent verification. The harness that made the change is not the harness that approves it.
- No committed secrets. Credentials live in local environment files or Infisical; pre-commit and CI reject secret patterns.
- Readable documentation. Sentence case headings, concrete verbs, and claims that point at evidence.
Every repository states its own state at the top of its README: active, experimental, or retired. Retired repositories are archived rather than deleted, and each one carries a note naming its successor.
Maintained by Frank Riemer · Built on the Starlight Intelligence Protocol