About Clone

Clone is a company-governed AI coworker assigned to a person, with its own identity, accounts, computer and wallet.

One conversation coordinates many agents. People and agents share a live workspace and keep working concurrently.

Source: README.md

The aim is to provision a Clone for an employee as naturally as provisioning a company Google account. It should feel like an available coworker with its own identity, rather than an assistant impersonating its user through their personal accounts.

This is broad product direction, not a promise that every integration ships together.

Source: docs/product.md

A Clone needs its own email inbox and calendar. Files use Clone’s existing filesystem and configured storage.

The desired flow is to invite it to a service such as Figma. It then registers or signs in using its own identity and connects an appropriate integration, MCP server or browser workflow, subject to policy.

Temporary workers use explicitly authorized access under that identity, rather than creating an account for every task.

Source: docs/product.md

Each Clone is assigned to one person. It responds to and is directed by that person.

The company provisions it and controls its access, permissions and permitted autonomy. Personal preferences operate inside company restrictions.

Account recovery, MFA, reassignment and employee offboarding need explicit handling.

Source: docs/product.md

The person should feel they are only ever talking to one agent, with one main chat surface, a durable identity and the ability to coordinate many agents.

Work can be shared, delegated and parallelized across many agents and tasks at once. The person should not need to route requests between workers or assemble their results.

Delegation must preserve applicable permissions and information restrictions. A unified identity does not mean every worker sees every task, memory or screen.

Source: docs/product.md

At the restricted end, a Clone can act as a chat assistant. At the autonomous end, it can perform broad operational work. These are configurable permissions, not separate products.

The permission model needs to cover reading data, changing data, communicating, installing connectors, creating accounts, delegating work, running code and spending money.

The company should be able to give each Clone a wallet with one or more cards and spending limits. Card limits must be enforced outside the agent, not merely described in its instructions. The card setup has not been validated yet.

Source: docs/product.md

The backend is Rust.

Clone-owned backend services target GCP Sydney, the web app targets Cloudflare Workers, and only native and CLI release downloads target R2.

The approach is to learn from the strongest open-source systems and reuse sound foundations, while owning the architecture and critical execution paths.

Source: README.md

A private Sydney environment runs the backend, harness and VM services. Public rollout and full product and device acceptance remain separate work.

Source: README.md