Skip to main content

​
What is a clone?

A clone is a service-shaped test environment for agents. Mature clones keep objects, relationships, and constraints close enough to the real service that your agent can use normal tools without touching production. Architecture previews are narrower: they may combine stateful overlays with fixture or recording-backed compatibility while the service-specific behavior model is still being built. Use clones when correctness depends on state changing across several calls: create an issue, read it back, comment on it, close it, and verify the final state without touching the real service.

​
Clone catalog

Pick the service your agent already talks to. Public clones have behavioral coverage evidence and production smoke coverage. Preview clones are accurate on the implemented surface, but their declared coverage is still narrower.

​
Public clones

  • GitHub: repos, issues, pull requests, branches, and commits.
  • Linear: issues, projects, teams, cycles, and workflows.
  • Slack: channels, messages, threads, users, and reactions.
  • Supabase: SQL, migrations, logs, branches, and project metadata.

​
Preview clones

  • Apify: actors, runs, datasets, key-value stores, and request queues.
  • Cal.com: event types, schedules, availability slots, bookings, calendars, and webhooks.
  • ClickUp: teams, spaces, folders, lists, tasks, comments, tags, time tracking, and checklists.
  • Customer.io: messaging automation across campaigns, broadcasts, transactional email, segments, customers, and message delivery.
  • Datadog: observability REST API for metrics, logs, monitors, dashboards, SLOs, incidents, teams, users, and service definitions.
  • Discord: guilds, channels, messages, webhooks, threads, commands, and interaction responses.
  • GitLab: projects, branches, commits, issues, merge requests, pipelines, labels, milestones, releases, and webhooks.
  • Google Workspace: Gmail, Calendar, Drive, Sheets, and Contacts.
  • HubSpot: CRM contacts, companies, deals, tickets, and engagements.
  • Jira: issues, projects, boards, sprints, and versions.
  • OwnerRez: vacation-rental PMS for properties, bookings, guests, quotes, financial reads, tags, fields, and webhook subscriptions.
  • PriceLabs: dynamic pricing for listings, overrides, neighborhood data, rate plans, and reservations.
  • Ramp: cards, funds, expenses, reimbursements, bills, and travel.
  • Sentry: error monitoring across organizations, projects, teams, issues, events, releases, and DSN keys.
  • Stripe: customers, payments, subscriptions, invoices, and refunds.
  • Tavily: search, extract, crawl, map, research, usage, and API key operations.
  • Unipile: LinkedIn and email messaging, accounts, and chats.
  • Webflow: sites, pages, CMS collections, items, assets, forms, and webhooks.
Need something else? Email us.

​
Compatibility matrix

Not every clone supports every workflow. Not every clone supports MCP. Clones with MCP support: Cal.com, ClickUp, Discord, GitHub, GitLab, Google Workspace, Jira, Linear, Ramp, Slack, Stripe, and Supabase. The rest expose a REST or API surface only. Stateful fidelity depends on the clone’s declared surface: some clones are behavioral, while Architecture Preview clones are still replay-backed or overlay-limited. Clones with REST or API fidelity: Apify, GitHub, Discord, HubSpot, Slack, Stripe, Jira, Linear, Supabase, Google Workspace, OwnerRez, PriceLabs, Tavily, Unipile, Webflow, and Datadog. Clones with route mode for both archal run and archal/vitest: GitHub, Discord, Slack, Stripe, Jira, Linear, Supabase, Google Workspace, and Ramp’s primary API domain, plus Apify, Tavily, and Datadog. Use explicit base URLs for GitHub, Discord, Slack, Stripe, Jira, Linear, Supabase, Google Workspace, Apify, Tavily, Datadog, and Ramp’s primary API domain. Ramp is MCP-first outside explicit base URL runs. Route mode lets an existing agent call real service domains, such as api.github.com, while Archal routes that traffic to the clone. Use explicit base URLs when you want the simplest integration path.

​
Three ways to use clones

  • archal run: run a scenario or task against clones and get a satisfaction score.
  • archal clone: start persistent clones for debugging or manual integration work.
  • archal/vitest: use supported hosted clones inside your existing Vitest test suite. Route mode currently supports Discord, GitHub, Google Workspace, Jira, Linear, Ramp’s primary API domain, Slack, Stripe, Supabase, Apify, Tavily, and Datadog.