FAQ & Windows
The short answers, plus an honest accounting of what "Windows experimental" means today.
The short answers
Is it free?
Yes. MIT licensed, no paid tier, no account.
Where does my data live?
Queues, artifacts, decisions, sessions, and quota snapshots stay as markdown and JSONL inside the instance directory you chose. The core makes no network calls and needs no API key; adapters only invoke tools you configure.
Does it automate ChatGPT?
Only if you choose the chatgpt-browser advisor, and then only via your own agent driving your own logged-in browser. Review the terms of the services you automate; manual and claude-code are first-class alternatives.
What port does the console use?
7433 by default, bound to 127.0.0.1 only. Change it with --port.
How do I delete everything?
Uninstall the tool (see Install) and delete your instance directories. That is the whole footprint.
Windows, honestly
Windows support is experimental. The code went through a portability pass and carries no POSIX-only calls, but the CI signal is still settling. Current state:
| Works | Status |
|---|---|
| Core CLI (init, status, tick, queue, capture, usage) | Expected to run; file locks are plain portable files, no fcntl |
| Web console | Stdlib server, expected to run at 127.0.0.1:7433 |
| Desktop notifications | PowerShell toast notifications (Windows 10+) |
| Installer | install.ps1 mirrors install.sh (venv + arthur.cmd shim) |
| Not yet | Why |
|---|---|
| CI-verified green matrix | windows-latest was just added; treat it as pending until it is visibly green |
chatgpt-browser advisor | Its browser runtime paths are macOS/Linux-only |
| ArthurBar menu bar app | macOS 14+ SwiftUI, by design |
| Tracker/quota command templates with exotic paths | Templates split with POSIX quoting rules; backslash-heavy commands can mis-split |
If you run it on Windows, WSL remains the boring, well-trodden path; native is the adventurous one. Bug reports from either are welcome.