Quickstart
1. Start the server
aircode
First run output:
AirCode Ø 1.0.0 — server ready
Local http://127.0.0.1:7860
Tailscale http://100.x.y.z:7860
Password k6uu3U6UG8AXgTnvNgNj
This password was generated for you and saved to ~/.config/aircode/config.json.
It is shown only once — run `aircode password reset` to rotate it.
AirCode Ø picks a free port automatically (7860 upward) and generates an access password. If Tailscale is present, it binds your tailnet IP so your phone can reach it; otherwise it binds localhost only.
2. Open the cockpit
Open the printed URL on any device that can reach the machine and log in with the password. On a phone, add it to your home screen — or install the mobile app.
3. Launch your first session
- Pick a project directory.
- Pick the execution environment:
- Local runs through host tmux or Windows ConPTY.
- Docker sandbox runs one supported direct session in a worker while mounting the selected project.
- Pick an engine (Claude Code, Codex, Gemini CLI, Grok Build, Kimi Code) and a permission mode.
- Launch. The agent keeps running on the AirCode machine — close the tab, take the train, come back: it’s still working. Notifications ping you when the agent needs input or finishes.
The Web, Desktop and native mobile launchers expose the same environment choice. Docker is currently a Codex source preview; see Docker sandbox before enabling bypass permissions.
4. Make it permanent
aircode service install # systemd user service, starts at login
loginctl enable-linger $USER # start at boot, survive logout
aircode status, aircode stop, aircode logs --follow do what they say.
Stopping or updating the server never kills running sessions — they live in
tmux, not in the server process.
5. Install the agent CLIs
AirCode Ø orchestrates the CLIs you already use. Install and authenticate them as
usual (claude, codex, gemini, …) under the same user. aircode doctor
commands verify what’s available.