Project / environment

A test world for your agent.

Discover your project. Test what your agent does before it touches production.

Import discovery

Discovery

01
Discover
Find tools and code paths.
02
Review
Choose what needs testing.
03
Run safely
Execute in a fresh sandbox.

Selected resources

No project connected. Import the inventory from your CLI to see its dependencies and workflow candidates.

Environment map

0 resources

100%

Selected resources

No resources selected

Run init in your project, then import .agenttwin/inventory.json. You can also declare a resource manually.

Drag to pan · drag cards to arrange

Scroll to explore · select a name to locate its card

Select software choose what your workflow uses

Runtime coverage

Node workflows, custom HTTP collections, a bounded Slack adapter, PostgreSQL and Redis run in hosted E2B sandboxes. Other provider adapters and browser/desktop execution require implementation. Native macOS apps need a compatible macOS runtime. Production accounts are not copied.

Project / workflows

Workflows

Choose a code path. Define the world it runs in. Check the outcome.

Prepare a workflow

Review the code pathChoose the entrypoint and files from your project.
Define the testMap supported operations, seed records, faults and expected outcomes in preparation.json.
Package and executeRun agenttwin prepare, then upload its bundle below.

Run a prepared workflow

Choose bundle

Run agenttwin prepare --file preparation.json in your project, then select its agenttwin.bundle.json. This packages your actual files and reviewed contracts.

Connect your account in Settings before executing.

No bundle selected. Starter files alone are not a discovered application bundle.

Build a starter configurationOptional scaffolding for supported services. Replace the generated example with your own code.

Runtime services

0 services enabled

Enable the services this workflow needs. Supported services found in your environment are selected automatically. This version requires Custom HTTP or Slack; PostgreSQL and Redis can be added alongside them.

Custom HTTP is an explicit collection contract, not a replacement for every provider API. Other selected apps remain in your environment and need their own adapter.

Session type

Created on demand in E2B. State and generated test credentials reset for every run; the sandbox is deleted afterwards. Reusable sessions are not available yet.

Execution limit (seconds)

1–300 seconds for your workflow.

Name your workflow

Lowercase letters, digits and underscores. Edit the exported code to run your own workflow.

Starting state (JSON fixtures)Synthetic records only

Enable Custom HTTP or Slack to configure JSON records. PostgreSQL seeds use the exported SQL file; Redis starts empty. No production account or data is copied.

Prepare an editable Node workflow, then execute it in your hosted sandbox.

Runtime coverage

A test world for your agent.

Discovery

Selected resources

Environment map

No resources selected

Workflows

Prepare a workflow

Run a prepared workflow

Runtime services

Settings

Workspace

Run preparation

Dashboard

Account connection

About this workspace

Runs

Submitted runs

Loading evidence