Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
All features

Compute

Computers your agents can drive.

Daemon-connected machines with real filesystems and agent-friendly controls.

Try nowSee pricing

A real machine, not a single run.

Keeps its memory

Files, settings, and what you installed all stay where you left them.

Ours or yours

Spin up one of our machines in a click, or hook in a server you already have.

Every action recorded

See exactly what the AI ran. Undo anything that touched your files.

It can use the screen, too.

Agents aren't limited to the terminal. With computer use they see the desktop, move the cursor, and click through real apps. Opt-in per computer, with every step recorded.

How is this different from "Code execution"?

Code execution is a quick one-off: start clean, run, done. A computer is a place that sticks around: your tools are installed, your files are there, the AI can come back to it tomorrow.

What you get

Pair your machines

Install the Idapt daemon on a computer you control and connect it to your workspace.

Persistent disk

Unlike a sandbox, computers keep state between sessions: your venv, your data, your config.

Commands in chat

Run commands from the conversation with output streamed back into the trace.

Agents can execute

Grant an agent scoped computer access. It executes through the daemon, you observe, the trace is auditable.

File bridge

Mount idapt folders onto the computer. Edit in idapt, run on the VM, push artifacts back.

Who it's for

Developers

Long-running build, real database, real dependencies: the AI works inside your actual environment.

Researchers

Run scripts on a dedicated research machine. The agent monitors, retries, and reports back.

Operators

Production-shape staging environment the AI can poke at without touching prod.

How it works

  1. 1
    Attach

    Install the daemon on the computer you want Idapt to use.

  2. 2
    Wire it up

    Mount the folders you want exposed, set per-agent permissions.

  3. 3
    Hand work over

    Mention the computer in chat: the AI runs commands and gets to work.

  4. 4
    Keep your hands on the wheel

    Audited command traces and computer controls let you interrupt or redirect work.

Frequently asked

Set up a workhorse.

Real machine, ready when you need it. Your AI handles the typing.

Spin up a computerRead the docs

Read the docs

  • Computers overview
  • Commands & files
  • Daemon troubleshooting

Pair with

  • Computer Use
  • Cloud Computers
  • Code Execution
  • Agents
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Voice Mode
  • Voice HUD
  • Web Search
  • Image Generation
  • Video Generation
  • Audio Generation
  • Transcription
  • Drive
  • Credentials
  • Sharing
  • Workspaces
  • Tasks
  • Memory
  • Agents
  • Subagents
  • Automations
  • Skills
  • idapt Code
  • Code Execution
  • Computers
  • Computer Use
  • Computer Assist · Soon
  • Containers · Soon
  • Cloud Computers
  • Local AI
  • AI Gateway
  • API & SDK
  • CLI
  • MCP
  • Tunnels
  • All features →
  • LLM cost calculator
  • Token counter
  • Context window checker
  • Can I run it
  • Model picker quiz
  • Savings finder
  • Video cost estimator
  • Text to speech cost
  • Transcription cost
  • API endpoint tester
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Skills
  • Learn
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)