mojave-studio/solix
Drive a Solix host — persistent terminals, a coding-agent crew with a First Mate orchestrator, projects, shared memory, and Helm registers — through the Solix MCP and CLI skill set.
Drive a Solix host through the solix CLI — persistent terminals, a crew of coding agents with a First Mate orchestrator, the routed task queue, projects, shared memory, secrets, the Helm registers, fleet machines, git, and Mac controls. Use when coordinating agents, tasks, projects, or terminals on a machine running Solix, or when the user mentions Solix, the First Mate, or solix.
Audit and unify agent instruction files (AGENTS.md, CLAUDE.md, GEMINI.md, Windsurf rules, …) so every agent CLI on this machine reads the same rules. Use when asked to unify agent memory/instructions, check instruction drift, or when agents are behaving differently because they read different rule files.
Register this thread with the Solix First Mate — report the task up front, then stream milestone updates into its terminal so the orchestrator can track, redirect, or intervene.
Save a shell command to the Solix Commands register so it can be opened and run later as a plain terminal — no agent chat required. Use when the user wants a reusable one-tap/one-command shortcut (a build, a deploy step, a log tail) rather than something an agent needs to reason about each time.
Commandeer this agent as the Solix First Mate: inspect resources, start and supervise persistent terminals or coding agents, apply machine controls, and preserve durable handoff context. Use when an agent is asked to coordinate work through Solix.
Drive the user's git repos through the solix CLI — status, diff, AI-drafted commits, branches, pull requests, push — including plain-speech requests like "commit this repo and write a message then push".
Leave a durable handoff note in Solix memory — what this chat did, what's next, and what's blocking — so the next agent or session can pick up without re-reading transcripts. With a harness argument, also spawn a successor bot on that provider (optional model) and brief it to continue the work immediately.
Manage the user's Solix Helm Commands register — create, list, show, edit, run, rename, or delete named shell commands via the solix CLI. Use when the user wants to save, inspect, change, run, or remove a reusable shell command on the host.
Manage the user's Solix Helm Docs register — add notes or links, adopt a project's AGENTS.md/CLAUDE.md, list, show bodies, or remove docs via the solix CLI. Use when the user wants to store, fetch, or delete reference text the crew can pull on demand.
Manage the user's Solix Helm Files register — register a path to local key/cert material, list, show, rename, or delete file pointers via the solix CLI. The register holds the path, never the contents. Use when wiring a local file into Solix setups.
Manage the user's Solix Helm Settings register — set, list, rename, or delete host-read config (autonomy level, mate bindings, alert routes, issue triggers) via the solix CLI. Use when changing how the Solix host itself behaves.
Manage the user's Solix Helm Skills register — add a local skill directory to the store, list, show, inject one live into a chat, or remove store skills via the solix CLI. Use when adding, inspecting, updating, or deleting agent skills Solix holds.
Manage the user's Solix Helm Values register — set, list, rename, or delete named variables that fill {{var}} placeholders in saved commands and host config, via the solix CLI. Use when the user wants to store, inspect, change, or remove a named value on the host.
Manage the user's Solix Helm Vaults register — import an Obsidian vault, list vaults, read their notes, or remove imports via the solix CLI. Vaults read live from disk and route notes to their owning project. Use when the user wants to wire a notes vault into Solix.
Add this chat to a Solix project — loads the project's context (working files, secret permits, provider) and records the membership in the shared memory graph.
Land the current Solix terminal — close its window/viewers while the shell keeps running on the host, cached for later resume. Use when asked to land/park this terminal or wrap up and exit a Solix session.
Load Helm register items into THIS chat — secrets, skills, docs, values, commands, files, or the whole Helm. The operator picks all-vs-one in a Mac popup the agent never sees; selected items are inserted as incoming work.
Wire Solix as an MCP server (solix mcp stdio, solix mcp --cloud to the production Cloudflare MCP) so a chat can send work to First Mate, or tidy MCP servers across agent CLIs — find failed, redundant, and disabled servers, remove the dead ones, and reauthorize expired OAuth. Use when asked to expose Solix to ChatGPT/Claude/Grok, add a Solix MCP connector, clean up, dedupe, fix, or reauth MCPs, or when an agent reports an MCP 'Needs authentication' or 'Failed to connect'.
Hand this chat's work to a fresh successor bot before running out of context — write the handoff, spawn a replacement on the same project, brief it, and exit cleanly instead of dying mid-task.
Tidy agent skills across every skills directory on this machine — find duplicates, broken links, shadowed copies, and stale versions, and remove or relink them. Use when asked to clean up, dedupe, audit, or fix installed skills, or when a skill loads the wrong version.
Read usage across every linked provider — rate-limit windows, % left, reset times, walls, promo/credit pools, and measured run results. Use when asked about usage, quotas, rate limits, when a window resets, or where work can run.