FAQ

Yes, for explicitly configured bundled Node workflows using supported operations. Run npx agenttwin init with Node.js 22.12+, review discovery, prepare your real files and execute in a fresh hosted sandbox. The dashboard supports individual AgentTwin accounts; users can also configure their own E2B account for direct CLI execution.

No. Discovery finds dependency and code signals. Supported services use synthetic state and fresh test credentials. A catalog entry does not imply a working vendor adapter. Provider-native account provisioning and arbitrary production-environment cloning are not implemented.

No. The product addresses workflows and agent side effects across systems. Timeout-after-write is one fault class; refund scenarios are historical examples.

The operator’s E2B key stays on the API server. Dashboard account tokens remain in tab memory. Sync sends reviewed metadata, not source bodies or credential values. Execution uploads explicitly reviewed application files and fixtures; those files can themselves contain sensitive values, so review the bundle. No production OAuth session is reused.

No. Init offers agent-assisted analysis and exports workflow candidates. Inputs, invocation, dependency mappings and assertions need review. Fix & retest exports recorded evidence for your coding agent; a rebuilt bundle and fresh execution are required to verify a repair.

Manual declarations, map layout and preferences persist in browser storage. Imported discovery and receipts stay in memory. Account-owned discovery and jobs persist on the API. Tokens are cleared on disconnect or reload.

The separate prototype is scripted and uses fictional scenarios. The dashboard and CLI operate on actual imported/synced discovery and hosted run receipts. Engineering examples are not customer references.