Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • 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)
Help Center
🖥️

The computer daemon

Found this helpful? Share it:

idapt-computer is the daemon that connects one of your machines to idapt. It is a separate binary from the @idapt/cli API client: this one runs the machine side, the background service, tunnels, and local inference 🖥️

Install and manage the service

The desktop app installs and supervises the daemon for you, and cloud computers come with it running. To set it up by hand, pair the machine from the in-app "Connect a computer" flow. It installs in user scope by default and is supervised per platform:

  • Linux: a systemd user unit, systemctl --user status idapt-computer

  • macOS: a LaunchAgent

  • Windows: a scheduled task

Two commands work the same everywhere:

idapt-computer service status
idapt-computer service doctor

service status reports whether the daemon is running and connected, and service doctor checks the setup and suggests fixes. See Troubleshooting a computer when it will not connect.

Its config file

The daemon reads $XDG_CONFIG_HOME/idapt/config.json(the legacy path /etc/idapt/config.json still works on older cloud images):

{
  "appUrl": "https://idapt.app"
}

appUrl points the daemon at your idapt environment, and defaultBackendPort sets the local port it serves on. Cloud computers write this file during provisioning, so you rarely edit it by hand.

Turn on machine capabilities

A machine you own starts locked down: local inference, computer use, and tunnel terminals are denied until you allow them on that machine. Enable one, then restart the service:

idapt-computer service policy enable local-inference
idapt-computer service status   # confirm it restarted

This local policy is the real boundary. Enabling exposure in a workspace does nothing until the capability is allowed on the machine itself.

Updates

The daemon updates itself. idapt directs updates over the heartbeat and keeps a last-known-good build to roll back to if one fails, so there is no manual update command to run.

Ports

The daemon dials out to idapt and opens no inbound ports of its own. When you forward a local port, it serves that service at an authenticated public URL. See Ports and port forwarding.

Related articles

🖥️

Computers

Pair your own machine or launch a cloud one, then let your AI run commands and work with files on it.

☁️

Cloud computers

Launch an on-demand cloud machine, understand what it costs per second, and hibernate it when you're done.

🛠️

Daemon troubleshooting

What to do when a paired computer goes offline, fails an update, blocks a capability, or won't reconnect.

Up next

Notifications from the CLI

Read your inbox and notify workspace members with idapt notification.

Was this helpful?