A solar system
of your own machines.

Solix is mission control for the computers you already run. A Mac becomes a planet, agents become crew, and a First Mate routes every job to the machine — and the model — that makes sense right now.

see the system macOS host · iOS observatory · solix CLI

S Y S T E M

Every machine is a planet.

The host app turns any Mac into a reachable world: persistent terminals that survive disconnects, paired devices, secret permits, and a heartbeat of CPU, memory, and active crew. Your iPhone is the observatory — every planet on one dark globe, one tap from its consoles.

Add a server, a studio box, a spare mini — each enrolls into the same solar system and reports its own capacity. Work goes to where the project lives, not where the request happened to start.

host server phone

C R E W

Agents are crew. State is a glyph.

Bots run in persistent terminals, not request threads — detach, come back tomorrow, the session is still warm. The roster reads like a flight board, and color is never the only signal.

activeproducing output now
holdingneeds an answer
landedfinished, unseen
·driftingquiet but alive
?darkcan't tell

F I R S T  M A T E

One agent commands the rest.

/solix:first-mate commandeers any agent shell into the orchestrator. It reads the chart — which projects live where, which planets have spare capacity, which models are free today — and dispatches work. Bounded tasks, real paths, expected output, a stopping condition.

Every landing writes a run record: provider, model, duration, outcome. First Mate scores the work and the next routing decision gets smarter. Cost is a first-class input, not an afterthought.

devinswe · medium → maxfree promo
gemini2.5-flash · free poolfree promo
codexspark → gpt-6-astracheap → premium
claudehaiku → fable · effort levelscheap → premium
+ nineteen moreevery CLI the planet has installeddetected live

H E L M

Projects are containers.

A project holds everything that serves one purpose — the backend, the frontend, the site, the docs — plus its helm items: working-file scope and a permit list of secret names. Agents see the permits, never the values.

solix — local socketdeck · crew of one
$ solix project show solix
d938da9f  solix  ~/Developer/Code/Solix MAC
provider  codex
secret    ANTHROPIC_API_KEY → claude
file      RemoteCore/Sources/RemoteCore/Bots.swift

$ solix mate --provider devin --model swe --effort high
 First Mate online — swe-2 high, unmetered today

$ solix runs
a3f9c1d2  scout   devin   2m41s  landed  5★
77be12aa  clerk   gemini  4m02s  landed  4★

D E C K

Built to be operated.

A menu-bar host on the Mac. An orbital globe on the iPhone. A solix CLI that agents themselves can drive — the same skills, symlinked into every provider's directory, so /solix works the same in Devin, Claude, Codex, Grok, and everywhere else a shell can read a file.

No public control plane. Machines pair with QR invites and device keys; the host is authoritative; secrets stay in the keychain behind named permits.

G E T  S O L I X

Run your own solar system.

The macOS host ships as a plain zip — no installer, no store. It plants itself in your menu bar, installs the solix CLI, and starts at login.

get the hostmacOS · arm64 · 3.8 MB
$ curl -fLO https://solix.fyi/Solix-macOS.zip && unzip Solix-macOS.zip && cd Solix
$ xattr -dr com.apple.quarantine RemoteHost.app   # signed run-locally, not notarized
$ open RemoteHost.app                            # menu bar — keep it running
$ ./solix install                                # CLI → ~/.local/bin · app + login agent

Teach every agent on the machine to drive it — one repo, every provider's skill format:

get the skillsgithub.com/Mojave-Studio/solix-skills
$ solix skill add Mojave-Studio/solix-skills   # inside a running host
# or standalone — link into every agent's skills dir:
$ git clone https://github.com/Mojave-Studio/solix-skills ~/.config/solix-skills
$ ~/.config/solix-skills/install.sh

Handing this off to an agent instead? Give it the repo README — it's written to be followed by one: raw.githubusercontent.com/Mojave-Studio/solix-skills/main/README.md

pairingone-time token — QR on iPhone, or solix pair prints an invite + verification code to compare on both ends (headless-friendly, any OS)2-factor
secretsmacOS keychain, named permits only — values inject into the spawned process env, never cross the wirekeychain
networklocal socket (same-UID) + local network only — no public control plane; use a trusted LAN or Tailscale, transport is authenticated but not encryptedLAN only
permissionsper-device grants gate every remote op — a fresh pairing gets view-status onlyleast privilege