Mythos

Devices in 📝MythOS are the machines you register to run 📝Loops: a small runner on your own computer checks in with MythOS, claims the loop runs meant for it, and runs each one in Claude Code on your own subscription. A run that never leaves the cloud cannot reach the files, tools and sign-ins on your machine, so a device brings the run to where that work already lives while MythOS shows its health and readiness from anywhere. Devices and Loops are for 📝Oracle members only, and Devices opens together with Loops; the runner installs on macOS today, and PC support is planned.

Key Capabilities

  • One-line install — Add device gives you one command that installs the runner and enrolls the machine
  • Readiness checklist — the device page shows each step that is done and the one fix for each that is not
  • Health at a glance — heartbeats, a 30-day history strip, checks, disk, memory and terminal sessions per device
  • Laptop-aware — a sleeping laptop shows Asleep and raises no alert unless it stays quiet for 24 hours
  • You choose its work — a device takes the loops pinned to it, and unpinned loops only if you opt in
  • Run opt-ins — per-device switches for what loops on that machine may do in MythOS, set only on the web
  • Self-updating — the runner updates itself between runs, checksum-verified
  • Clean removal — uninstall revokes the device's keys and removes only what setup installed

Getting Started

  1. On the Mac, install what running loops needs: Apple's Command Line Tools with xcode-select --install (they bring Python 3.9 or later), Claude Code with curl -fsSL https://claude.ai/install.sh | bash, and tmux with brew install tmux if you use Homebrew (otherwise follow tmux's own install guide). Without Claude Code and tmux the device still enrolls, heartbeat-only, and setup names what to install.
  2. Open Loops → Devices and choose Add Device. Give it a name and a permanent id, then pick how often it checks in and which channel receives its alerts.
  3. Copy the install line and run it in Terminal on that Mac. The code is single use and expires after ten minutes; New Code opens another.
curl -fsSL https://mythos.one/install/device | sh -s -- --code XXXX-XXXX
  1. Setup enrolls the device, schedules its heartbeat, checks prerequisites, turns on run claiming, and asks you to sign Claude Code in for background runs — one browser sign-in. A missing step does not stop it; re-running mythos-device setup resumes where it left off.
  2. Watch Add device's last step, which stays on the device page: Ready to run loops when everything is in place, or Heartbeat only — N steps left with one fix per open item:
    • Agent CLI (Claude Code) — the agent that runs your loops. Fix: curl -fsSL https://claude.ai/install.sh | bash
    • tmux — the terminal session each run lives in. Fix: brew install tmux
    • Signed in for background runs — a run the schedule starts cannot use Claude Code's interactive sign-in, so the device keeps its own. Fix: mythos-device sign-in
    • Run claiming — whether this device takes loop runs at all. Fix: mythos-device runner enable, once Claude Code and tmux are installed

FAQ

  • Who can use Devices, and how many? 📝Oracle members, the same members who can use Loops, with up to five devices per account; each uses two of your ten API keys, and a Revoked device does not count. The runner supports macOS only for now; PC is planned, with no date set.
  • Which loops does a device run? Loops pinned to it by their Device setting, plus unpinned ones if you turn on Take any unpinned loop; a loop that needs a capability goes only to a device with that plug-in (mythos-device plugin add <name> <command…>). Script steps run their declared commands there with no model, each only after you confirm it in the loop's trust on the web.
  • What may loops on a device do in my library? They work under a fixed list of allowed actions, with switches on the device page for Delete and restructure, Share and invite, Community and audience, and Loop management (on by default) and Other libraries (off by default). Only you can change them, on the web; no key can.
  • How do I update, uninstall or remove a device? The runner updates itself between runs, checksum-verified. mythos-device uninstall revokes its keys and removes only what setup installed, --forget also deletes its history from MythOS, and if the machine is gone, use Remove on the device page.
  • Something isn't working — what are the common fixes? Run mythos-device doctor, which re-checks every step and prints one fix per problem. The common ones:
    • command not found: mythos-device — open a new terminal; the installer adds ~/.mythos/bin to your PATH, and ~/.mythos/bin/mythos-device always works.
    • "Python 3.9 or later is required" — run xcode-select --install, then the install line again, with a new code if the old one expired.
    • The heartbeat cannot read the Keychain — set "secretStore": "file" in ~/.mythos/device/config.json, choose Rotate Key, and re-run setup with --replace.
    • Signed out — run mythos-device sign-in.
    • Device limit reached (DEVICE_LIMIT) or Code expired — remove a device you no longer use, or choose New Code; codes last ten minutes and work once.

Related

  • 📝Sessions & Devices — a different feature: the browsers and computers signed in to your account, not machines that run loops

Contexts

Created with 💜 by One Inc | Copyright 2026