Compatibility
What runs where, and what is still to come. Every row carries a status, its edition, and the one thing worth knowing about it.
What Fugaro does today is on the features page.
Legend
- Supported
- Built, not enabled
- Coming soon
- Roadmap
- Not planned
Read against the CLI at v0.26.1 and the console at v0.123.0.
Local environment (CLI)
One release builds macOS and Linux from the same source, and the released binary carries the Subscription Edition code compiled in beside the MIT core.
| What | Status | Edition |
|---|---|---|
| macOSApple silicon and Intel. | Supported | Core (MIT) |
| Linuxamd64 and arm64. | Supported | Core (MIT) |
| Windows (WSL)The Linux binary inside WSL 2. Keep the checkout out of /mnt/c, install Claude Code in the distro, and sign in with gcloud there: its credentials are a file inside the distro, not the one on Windows. | Supported | Core (MIT) |
| Windows (native)A native port is approved through its first slice; the release builds no Windows binary yet. | Coming soon | Core (MIT) |
Console
| What | Status | Edition |
|---|---|---|
| macOSOne universal build for Apple silicon and Intel. | Supported | Subscription Edition |
| LinuxAppImage and deb packages for x64. | Supported | Subscription Edition |
| WindowsNo Windows build exists; one is approved, running the Linux CLI through wsl.exe. | Coming soon | Subscription Edition |
| Sign-inThe console runs on top of the CLI and inherits its identity; there is no separate console login. | Supported | Subscription Edition |
Mobile app
| What | Status | Edition |
|---|---|---|
| iOSOne global app published by Fugaro is planned; no release has been cut. | Coming soon | Subscription Edition |
| AndroidThe same app as iOS. | Coming soon | Subscription Edition |
Agent harness
| What | Status | Edition |
|---|---|---|
| Claude CodeThe only harness a run drives today. | Supported | Core (MIT) |
| OpenAI CodexNo Codex code exists; it is a non-goal of the multi-model design. | Roadmap | Core (MIT) |
| OthersNo current value in adding more harnesses. | Not planned | Core (MIT) |
Model access
Models are wired per role: a cheap model for the inner loop, frontier models for senior and security review.
| What | Status | Edition |
|---|---|---|
| OpenRouterOpenRouter or any Anthropic-compatible endpoint, for the coder and first-line reviewer. | Supported | Core (MIT) |
| Anthropic API keyThe senior and security reviewers, e.g. Opus, on a project's own key. The path is built; this api-key half is not enabled yet, and its live check has not run. The cloud review job the key would serve is admitted — what is still owed there is the live check rather than the code. | Built, not enabled | Core (MIT) |
| Claude OAuth token (bring your own credentials)Several named accounts per project, chosen per profile or stage as before, and each one also a typed credential that an ordered pool may group and a craft's access name. Automatic failover between them is not claimed. Use of a subscription is subject to the provider's own terms. | Supported | Core (MIT) |
| Direct keys for DeepSeek and other Anthropic-compatible endpointsA user-named provider entry with its own base URL, models and prices. | Supported | Core (MIT) |
| Native OpenAINo native OpenAI provider kind exists. | Roadmap | Core (MIT) |
| ChatGPT / Codex OAuthThe token name is reserved in the OAuth-token design; no code. | Roadmap | Core (MIT) |
| Vertex AIClaude on Vertex is the default auth, billed to the project's own GCP account. A dollar cap on Vertex is observe-only until Check 20's Vertex facts are recorded. | Supported | Core (MIT) |
Cloud
Fugaro runs in its own isolated GCP project, so it doesn't matter where your code or production lives.
| What | Status | Edition |
|---|---|---|
| Google Cloud (GCP)Deliberately GCP-only. | Supported | Core (MIT) |
| AWS, AzureNo plan today, and no ruling against them: either would mean replacing Firebase. | Not planned | Core (MIT) |
Execution backends
| What | Status | Edition |
|---|---|---|
| Cloud Run jobs (gen 2)The default backend, on the gen 2 execution environment. | Supported | Core (MIT) |
| VM / Cloud BatchOpt-in per installation (the project config names it cloud-batch). The owner has declared it operational, on the owner's word: its live checks, 57b and 124, are still owner-run. fugaro doctor reports an installation that selects it, failing until the backend's own checks pass; doctor reports and does not fence, so a launch is not blocked by it. | Supported | Core (MIT) |
Forges
| What | Status | Edition |
|---|---|---|
| GitHub CloudPull requests, comments and follow-ups. | Supported | Core (MIT) |
| Bitbucket CloudPull requests, comments and follow-ups. | Supported | Core (MIT) |
| GitLab CloudGitLab appears in the test fixtures only. | Roadmap | Core (MIT) |
| GitHub Enterprise Server and GitLab self-managedSelf-hosted forges are a plan, not a build. | Roadmap | Subscription Edition |
| Bitbucket Data CenterThe Bitbucket integration speaks the Cloud API roots only today. | Roadmap | Subscription Edition |
Issue trackers
| What | Status | Edition |
|---|---|---|
| Read and update issues in your own agentYour own agent reads the tracker through its own MCP servers and hands Fugaro a finished task. | Supported | Core (MIT) |
| Tracker access inside a runA run's agent gets no tracker server, and the review stages strip any MCP configuration. | Roadmap | Core (MIT) |
| Native triggers (label or assign to start a task)No webhook layer exists. | Roadmap | Subscription Edition |
Notifications
None of this is built: there is no sender, no token store and no webhook.
| What | Status | Edition |
|---|---|---|
| Mobile pushThe primary channel for individuals. | Roadmap | Subscription Edition |
| Slack, channel notificationsThrough an incoming webhook. | Roadmap | Subscription Edition |
| Microsoft Teams, channel notificationsAlongside Slack. | Roadmap | Subscription Edition |
| Slack / Teams interactive threadsOne thread per task, with replies and buttons going back to the agent. | Roadmap | Subscription Edition |
| EmailAlongside Slack and Teams. | Roadmap | Subscription Edition |
Identity and roles
| What | Status | Edition |
|---|---|---|
| Google identity via gcloudThe CLI and the console; there is no separate Fugaro login. | Supported | Core (MIT) |
| Google identity with email or domain allowlistsThe phone signs in with a Google account, and the installation's email or domain allowlists decide who gets in. | Supported | Core (MIT) |
| QR pairing (CLI)The CLI writes the pairing; the device's role is the issuer's own, and the flag may only lower it. | Supported | Core (MIT) |
| QR pairing (app scanner)The app-side scanner is not built. The pairing records a role on the device, not yet enforced by the security rules. | Coming soon | Subscription Edition |
| Roles: Admin, Operator, ViewerThe three roles the CLI, console and docs name; enforcement is design only. | Coming soon | Core (MIT) |
| Device management (CLI)List and revoke paired devices. | Supported | Core (MIT) |
| Device management (app and console)No app or console screen exists. | Roadmap | Subscription Edition |
| SSO and workforce identity federationNo SSO or federation code exists. | Roadmap | Subscription Edition |
| Workspaces spanning several projectsDesign answered, and the local layer and the CLI's reads are merged; no workspace service exists. | Roadmap | Subscription Edition |