Skip to main content

Documentation Index

Fetch the complete documentation index at: https://ade-app.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

Overview

ADE does not perform computer use directly. Instead, it acts as the control plane — the orchestration layer between your AI agents and external automation backends. This architecture means:
  • ADE works with any computer-use backend, not just one vendor.
  • Agents can request browser or desktop actions through a unified API regardless of which backend is active.
  • All proof artifacts (screenshots, traces, recordings) are normalized, stored, and linked to the relevant mission, chat, PR, or Linear issue.
  • Backend health, capability coverage, and proof requirements are visible at a glance in Settings.

Backend Agnostic

Connect Ghost OS, agent-browser, or use the built-in ADE Local fallback. Switch backends without changing automation code.

Proof Collection

Every computer-use action can be required to produce proof — screenshots, video recordings, browser traces, or DOM verifications.

Artifact Ownership

Artifacts are linked to lanes, missions, chat sessions, PRs, and Linear issues. Review and publish them from a single panel.

Policy Control

Per-session policies control when computer use is active: Off, Auto, On, Fallback, or Proof-required mode.

Supported Backends

Backend Capability Matrix

CapabilityGhost OSagent-browserADE Local
Browser automationYesYesNo
Desktop automationYesNoNo
Screenshot captureYesYesYes
Video recordingYesYesNo
Browser traceYesYesNo
DOM verificationYesYesNo
Console log captureYesYesNo
Multi-displayYesNoNo
Native app controlYesNoNo

Next Steps

Connecting Backends

Step-by-step setup guides for Ghost OS and agent-browser, plus computer use policy reference.

Proofs & Artifacts

Proof kinds, artifact ownership, and how computer use integrates with missions and chat.

Configuration

Proof requirement profiles and troubleshooting common issues.