Launcher — User Guide
The Psycheros launcher is a desktop app that installs your entity as a persistent background service and gives you a single window to chat with it. Your entity runs continuously — closing the launcher doesn’t stop it.
If you’ve never run Psycheros before, start here.
Installing
Section titled “Installing”- Download
Psycheros-macOS-latest.dmg. - Drag
Psycheros.appto/Applications/. - Right-click (or
Control-click) the app and choose Open from the context menu. This is required on the first launch only — Psycheros is not code-signed and macOS Gatekeeper blocks a normal double-click. - macOS shows a dialog: “Psycheros” can’t be opened because Apple cannot check it for malicious software. Click Open anyway.
- The app launches. Every subsequent launch is a normal double-click.
If you only see Move to Trash and no Open option, your Mac is on the strictest Gatekeeper setting. Lower it under System Settings → Privacy & Security → Security, or run this in Terminal once:
xattr -dr com.apple.quarantine /Applications/Psycheros.appWhy this is expected: Psycheros hasn’t paid Apple’s Developer ID signing fee. The extra step is only needed once. After that, macOS remembers your approval.
Windows
Section titled “Windows”- Download
Psycheros-Windows-latest.msi. - Run it. Windows SmartScreen may show “Windows protected your PC” — click More info → Run anyway. This is expected for unsigned installers.
- The launcher installs and opens.
First run
Section titled “First run”The launcher walks you through setup:
- Your name — what the entity calls you.
- Entity name — what the entity is called.
- Timezone — used for daily memory consolidation and scheduling.
- LLM API key — any OpenAI-compatible key (Z.ai, OpenRouter, OpenAI, etc.).
Once configured, click Install autostart. The launcher writes an OS service definition (launchd on macOS, Scheduled Task on Windows) and starts the daemon. From then on, your entity runs at every login and is auto-restarted by the OS if it crashes.
The launcher window
Section titled “The launcher window”The launcher has two surfaces:
- Chat — the main view. The entity’s web UI rendered inside the launcher
window. Same interface you’d see at
http://localhost:3000in a browser. - Manager — press ⌘, (macOS) or Ctrl+, (Windows) to toggle. Shows daemon status, install/uninstall autostart, logs, version info, and recovery tools.
You don’t need to keep the launcher open. The entity runs as a background service regardless. The launcher is just a window onto it.
Coming from the v1 launcher
Section titled “Coming from the v1 launcher”If you were running the v1 launcher (a browser dashboard at localhost:3001)
and want to bring your existing entity over:
- Export from v1 first. In v1’s chat UI, go to Settings → System Admin →
Entity Data → Export and save the
.zip. - Install the v2 launcher (steps above).
- Complete v2’s welcome wizard and click Install autostart — a fresh empty entity comes up.
- In v2’s chat UI, go to Settings → System Admin → Entity Data → Import and
select the
.zipfrom step 1. The daemon restarts and your migrated entity takes over.
Updating
Section titled “Updating”The launcher checks GitHub Releases every 3 hours for newer versions. When an update is available, a toast notification appears inside the launcher window.
To check manually, open the manager (⌘,) and look at the version info card. Click any version chip to open that package’s release page on GitHub.
Troubleshooting
Section titled “Troubleshooting”The launcher won’t open on macOS. Make sure you right-clicked → Open on the
first launch. If Gatekeeper still blocks it, open Terminal and run:
xattr -dr com.apple.quarantine /Applications/Psycheros.app
“Port 3000 already in use.” Another instance of Psycheros is running. The launcher detects this and connects to the existing daemon — just use the chat window.
The entity isn’t responding. Open the manager (⌘,) and check the status card. If the daemon shows as Stopped, click Start daemon. If it shows as Running but chat isn’t loading, check the log tail at the bottom of the manager for errors.
First run is slow. Deno downloads its dependencies on first launch. This only happens once.
Entity Loom (import wizard). To import chat histories from other platforms,
start Entity Loom separately (deno task start inside packages/entity-loom/)
and open http://localhost:3210. See the
Entity Loom user guide for details.
When not to use the launcher
Section titled “When not to use the launcher”The launcher is the recommended path for desktop users. If you’re deploying Psycheros to a server, running it in Docker, or embedding it in your own infrastructure, the Docker image or building from source is a better fit. See the repo README for those paths.
The legacy v1 launcher
Section titled “The legacy v1 launcher”The v1 launcher was a browser-tab dashboard at http://localhost:3001 with
Install / Update / Start / Stop buttons. It ran Psycheros as a child process,
meaning closing the dashboard killed the entity. The v2 launcher replaces it
with an OS-supervised service model.
The v1 installer scripts (install.sh / install.ps1) are still available on
the
launcher-v* releases
for anyone who prefers that path, but new users should start with v2.