Morph and connected apps

Every Doozy workspace has one persistent Morph environment (aka cloud computer, sandbox, or agent computer). Doozies use it to browse, run commands, work with repositories and files, install tools, and carry state from one to-do to the next.

One Morph environment per workspace

All Doozies in the same workspace share:

• the persistent filesystem;
• checked-out repositories and branches;
• installed command-line tools and packages;
• browser profiles and authenticated sessions;
• command-line credentials configured for that workspace;
• generated artifacts and intermediate work.

Each Doozy has its own role, memory, to-dos, and conversation context, but Morph is a shared execution environment. Doozies in the same workspace aren’t security boundaries from one another.

Different workspaces receive different Morph environments. Use workspace boundaries when two projects shouldn’t share files, sessions, credentials, or connected data.

Work continues in the cloud

Morph doesn’t depend on your laptop staying awake. A Doozy can continue research, testing, generation, or scheduled work after you close Doozy.

You can return to the linked conversation or to-do to see progress, inspect results, redirect the plan, or handle an approval. Long-running work should produce checkpoints so useful progress isn’t trapped in one fragile process.

Watch computer work

When a to-do uses an interactive browser or desktop application, open the live computer view to observe it. The view shows the current workspace environment, not a simulation of your local screen.

Watching is useful for diagnosing a blocked flow, confirming the selected account, or checking a visual result. You don’t need to keep the viewer open for the Doozy to continue.

Take over for sensitive steps

Use Take over when a website requires a password, passkey, verification code, CAPTCHA, payment confirmation, legal attestation, identity check, or other step that should remain human-only.

While you control the session, complete only the necessary step and return control when the sensitive information is no longer visible. Don’t type secrets into the conversation. A Doozy can continue from the resulting authenticated session without knowing the credential itself.

Sign in once per workspace

A successful browser or CLI login can be reused by the Doozies in that workspace. This reduces repeated setup and lets specialized Doozies cooperate in the same tools.

Before signing in, confirm the workspace is the correct security boundary. Don’t authenticate a personal or production account in a workspace whose members or Doozies shouldn’t use it. Prefer restricted service accounts and least-privilege scopes.

Connect an app

Connections provide structured access to services such as email, calendar, chat, storage, project management, source control, CRM, and analytics.

Use a connection (aka connector or integration) instead of browser automation when it provides the required operation. Connections are usually more reliable, easier to audit, and clearer about scope. Browser and computer use remain useful for visual work or services without a suitable connection.

Connections are registered at the workspace level. A Doozy’s toolkit controls which of those connections it can normally use. Removing a tool from one Doozy doesn’t revoke the underlying workspace connection from every other Doozy.

Connect Codex

Connect an eligible ChatGPT subscription through OpenAI sign-in in the provider settings. Once connected, choose Codex as the model provider for any Doozy or supported to-do. When work needs computer access, the Doozy can use Codex alongside files, browser sessions, repositories, and tools in Morph. API-key access remains available and is billed through the associated OpenAI Platform account.

Don’t copy your local Codex authentication file into a conversation or shared artifact. Treat cached credentials as secrets. For parallel coding work, use branches or worktrees and assign clear ownership before Doozies modify the same repository.

Persistent and replaceable state

Keep source work, artifacts, and important configuration in persistent workspace directories or connected systems. Treat temporary directories, package caches, running processes, and uncommitted experiments as replaceable.

Updates and recovery should preserve durable workspace data. A full reset may restore an earlier snapshot and lose recent unsynchronized changes, so commit or export important work before using it.

Your local computer is separate

Morph can’t silently reach files or applications on your physical computer. Local execution requires a separate, explicit capability and approval policy. Prefer uploading specific files or using a connected service when local access is unnecessary.

If local execution is enabled, review the proposed command, working directory, and affected files before approving it. Local access expands the security boundary beyond Morph.

Frequently Asked Questions