appendix

FAQ

Current early-access answers about installation, agents, data, and collaboration.

What can I install today?

The public early-access release supports macOS Apple silicon and Windows x64. Use the install page for the current packages. Intel Mac and Linux builds are not published yet.

Which agents are supported?

Claude Code and Codex are the core Remote Host providers. Grok remains available for compatible local desktop sessions. Manifoldone uses your provider authentication and account; provider subscriptions and API charges stay between you and the provider.

What is a Remote Host?

It is an Apple-silicon Mac you manage that runs Agent threads inside an isolated Linux VM. It gives you a recoverable workspace without presenting Manifoldone as a hosted provider-account reseller. Remote Host support is currently private beta.

Does my code stay local?

Local execution and its working tree stay on the desktop machine. Cloud-session execution and working files live in the isolated Remote Host runtime. The selected provider CLI may send prompts and relevant context to its provider under that provider’s terms. Connected collaboration also sends the account, workspace, session, presence, and selected display/control data needed for other clients to participate.

Do not treat “local execution” as “no data ever leaves the machine.” The current fixed fields, sharing boundary, and deletion controls are described in Data & privacy.

Why not just use the provider’s own app or an AI editor?

Those products remain useful and Manifoldone does not replace them. Manifoldone is the workspace around Claude Code and Codex across clients. It preserves transcripts and Git checkpoints, supports recovery, and connects that work to review and accountable handoff. Grok local compatibility remains a secondary capability.

How is this different from agent teams inside one provider?

Provider agent teams coordinate agents within that provider. Manifoldone’s focus is preserving Claude Code and Codex work across interruptions and letting approved people work in the same durable Agent session. Their commands are attributable and serialized; the Remote Host credential stays off collaborator clients. Shared execution is available only for eligible provider identities.

How do I add a teammate today?

The project owner can search for an existing account or create a seven-day, single-use invite link for a member or viewer. The server stores only the token hash. The owner can revoke an unused link, and sign-in returns a new user to the pending invitation. Founder-led setup remains available through the private beta.

Does collaboration work remotely?

Connected viewing and member execution are available as early-access surfaces. Authorization, command ordering, disconnect, reconnect, and recovery behavior are still being hardened. Use version control for important work and grant member access only to people you trust; viewer remains read-only.

Does it work offline?

Local desktop sessions and saved history are designed around the local machine. Account, shared workspace, and remote collaboration features require their services to be reachable.

What about Perforce?

The current product workflow is Git-based. Perforce is a possible future design-partner investigation, not a supported or scheduled feature.

Can I self-host?

Agent execution is already on your own machine. A supported self-hosted relay is not currently offered.

How do I report an early-access blocker?

Use the support form with the app version, operating system, provider, and visible error category. Do not include credentials, environment variables, proprietary code, prompts, or terminal logs. The app can also copy a content-free diagnostic summary from Settings.