Showcase
Teams and projects shipping real software with the Stella CLI — Oxagen, who build their platform with Stella, and stella-examples, the open cookbook with a working example for every configurable surface.
Real teams, shipping real software, with Stella in the loop. Each entry names who they are, what they ship, and how Stella fits the way they work.
Oxagen
oxagen.sh ships Oxagen with the Stella CLI as their code agent of choice. Day-to-day feature work, refactors, and fix-ups run through Stella sessions: the Command Deck for interactive work, goal mode when there's a definition of done to drive to green, and fleets when a batch of tasks can fan out across isolated worktrees — with every run's cost and outcome metered in the workspace's local telemetry.
Oxagen also hosts this documentation site — stella.oxagen.sh runs on their
infrastructure.
Stella is BYOK and local-first for showcased teams too: Oxagen's sessions run on their own provider keys, and their telemetry never leaves their machines.
stella-examples
github.com/macanderson/stella-examples is the open configuration cookbook for Stella itself: a working example for every configurable surface in the CLI, each file matching the schema Stella actually parses, each directory README saying where the file goes on disk. Clone it, copy a file into place, and it works.
| Surface | Examples |
|---|---|
| Settings profiles | minimal, balanced, max-quality, dirt-cheap, local-ollama, and team settings.json profiles, plus the credentials.toml shape — the model lineups from the examples as ready-to-copy files |
| Lifecycle hooks | A SessionStart context injector, a PreToolUse bash guard that vetoes destructive commands, and a PostToolUse JSONL audit log — wired together in one hooks block (docs) |
| Custom commands | /fix-issue (with $ARGUMENTS), /changelog, /pr-description (docs) |
| Custom agents | code-reviewer (read-only toolbelt), test-writer (witness tests + verify_done), docs-writer (no shell) (docs) |
| Skills | conventional-commits and release-checklist (docs) |
| Rules & guards | Hard guards — no-force-push, protect-migrations, no-shell — and a soft code-conventions rule (docs) |
| Custom tools | todo_scan (input schema + STELLA_INPUT_* env) and loc_report (minimal manifest) (docs) |
| MCP servers | An mcp.toml with both stdio and HTTP transports (docs) |
| Fleet plans | A feature build-out DAG in TOML and a parallel cleanup sweep in JSON, with claims and worktree isolation (docs) |
| Memory & domains | A hand-tuned domains.toml and the lesson → skill → rule promotion loop (docs) |
| Scripting & CI | ci-autofix.sh (budget-capped, oracle-armed) and nightly-goal.sh (cron-able goal runs) |
Everything in stella-examples respects the trust boundary: project-scope
hooks, MCP servers, and credential-routing fields stay inert in a cloned
repo until you opt in with STELLA_TRUST_PROJECT=1.
Add your project
Shipping with Stella? Open a pull request against
macanderson/stella that adds an entry
to stella-docs/content/docs/showcase.mdx — who you are, a link, and a few
sentences on how Stella fits your workflow. Entries should be things that
actually ship; hello-worlds are better served by the
examples. Have a hook, agent, profile, or plan worth
sharing instead? Send it to
stella-examples.