> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ancha.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These docs describe the Ancha CLI, npm package @ancha-labs/cli version 0.1.4, and the hosted workspace at app.ancha.io. Coding agents should start at https://docs.ancha.io/coding-agents. Run the CLI as `ancha` after `npm install -g @ancha-labs/cli`, or as `npx -y @ancha-labs/cli@0.1.4` without installing. Pass --json for machine-readable output, or set ANCHA_JSON=1. Every command ends with a `next:` line naming the next command. Exit codes: 0 pass, 1 a check failed or a comparison regressed, 2 usage, config or authentication error, 3 infrastructure error, 4 unimplemented endpoint with --strict.

# Worlds

> A world is the set of tools and starter data an attempt begins with. Every attempt gets its own copy, built from the same seed.

A world is the starting point for an attempt: which tools exist and what data they hold. Ancha builds a fresh copy of the world for every attempt, so one attempt's writes never reach another.

## Starter data

Every tool ships with versioned starter data for one fictional company, Acme, which sells warehouse analytics, and its customers: Ridgeway Robotics, whose pilot starts this week, Pinecrest Health, Bluefield Logistics, Kestrel Credit Union, Summit Freight, Harbor Foods and Helix Manufacturing. The records are linked across tools: the Ridgeway Robotics account in Salesforce, the deal in HubSpot and the discovery call in Gong describe the same customer, and the same people, Ben Carter, Rachel Moore, Mike Turner and their colleagues, appear in Slack, GitHub and PagerDuty.

| Tool | Starter data (dataset `<tool>-starter`, version 1.1.0) |
| - | - |
| [Slack](https://docs.ancha.io/tools/slack.md) | Workspace "Acme", a bot and nine people, ten channels (#general, #support, #growth, #orders-incident, #product, #sales, #customer-success, #data-platform, #random and a private #leadership), 52 messages with threads. |
| [GitHub](https://docs.ancha.io/tools/github.md) | Three repositories: `acme/orders` with seven commits, six pull requests and seven issues, plus `acme/web` and `acme/warehouse-sync`. |
| [Datadog](https://docs.ancha.io/tools/datadog.md) | Seven monitors, three dashboards, five events, eight metric series and seventeen log lines across six services. |
| [PagerDuty](https://docs.ancha.io/tools/pagerduty.md) | Four users, two escalation policies, four services and five resolved incidents. |
| [HubSpot](https://docs.ancha.io/tools/hubspot.md) | Nine companies, thirteen contacts, eight deals and the default sales pipeline. |
| [Salesforce](https://docs.ancha.io/tools/salesforce.md) | Seven accounts, six contacts, four leads, six opportunities, two campaigns and two campaign members. |
| [Gong](https://docs.ancha.io/tools/gong.md) | Two users, two workspaces and seven calls, six with transcripts. |
| [Google Analytics](https://docs.ancha.io/tools/google-analytics.md) | Two properties and nineteen sessions of historical traffic. |
| [Google Ads](https://docs.ancha.io/tools/google-ads.md) | A manager account with one client account, a separate restricted account, and a search campaign with a budget, ad group, ad, keyword and two days of reports. |
| [LinkedIn Ads](https://docs.ancha.io/tools/linkedin-ads.md) | Two ad accounts, a campaign group, two campaigns, two creatives and daily analytics. |
| [ChatGPT Ads](https://docs.ancha.io/tools/chatgpt-ads.md) | Two ad accounts, two campaigns, an ad group, two ads and hourly insights. |
| [Open-Meteo](https://docs.ancha.io/tools/open-meteo.md) | Ten places (San Francisco, New York, London, Berlin, Tokyo, Sydney, Portland, Chicago, Toronto and Singapore) with a synthetic climate. |
| [Gmail](https://docs.ancha.io/tools/gmail.md) | The support mailbox with four labels, nineteen messages in threads, a draft and an attachment, plus Laura Kim's mailbox. |
| [Google Drive](https://docs.ancha.io/tools/google-drive.md) | Thirty files in company, customer, engineering, finance and leadership folders, with permissions, comments and a trashed copy. |
| [Microsoft Word](https://docs.ancha.io/tools/microsoft-word.md) | Contracts, policies and templates as `.docx` files, one with an earlier version and one shared with a customer. |
| [Notion](https://docs.ancha.io/tools/notion.md) | Engineering and product pages with blocks and comments, a customer feedback database and meeting notes. |
| [Dropbox](https://docs.ancha.io/tools/dropbox.md) | Sales, marketing, customer upload and team folders with a revision, a deleted file, a public link and a shared folder. |
| [Resend](https://docs.ancha.io/tools/resend.md) | Two domains, two segments, six contacts, five sent emails with outcomes and two broadcasts. |
| [Better Stack](https://docs.ancha.io/tools/better-stack.md) | Six monitors, two heartbeats, four incidents, two on-call rotations and a status page. |
| [Linear](https://docs.ancha.io/tools/linear.md) | Two teams, two projects, five labels and seventeen issues. |
| [Jira](https://docs.ancha.io/tools/jira.md) | Three projects, thirteen issues, three sprints and two issue links. |
| [Okta](https://docs.ancha.io/tools/okta.md) | Twelve users across every lifecycle state, nine groups, eight SAML apps and ten System Log events. |
| [Amazon S3](https://docs.ancha.io/tools/amazon-s3.md) | Four buckets with read-write, read-only and no access, holding customer exports, a sync staging area, backups and web assets. |
| [Clerk](https://docs.ancha.io/tools/clerk.md) | Twelve users in five customer organizations, with pending invitations and sessions. |
| [Attio](https://docs.ancha.io/tools/attio.md) | Seven companies, nine people, five deals, a renewals list, two notes and three tasks. |
| [Stripe](https://docs.ancha.io/tools/stripe.md) | Three products, five customers with test cards, four subscriptions, six invoices, two payments and a refund. |
| [PayPal](https://docs.ancha.io/tools/paypal.md) | A product with three plans, four subscriptions and five checkout orders. |
| [Shopify](https://docs.ancha.io/tools/shopify.md) | A store with two locations, five products, seven customers and eight orders. |
| [Lob](https://docs.ancha.io/tools/lob.md) | Nine addresses, two bank accounts, three templates, two letters, two postcards and a check. |
| [Kalshi](https://docs.ancha.io/tools/kalshi.md) | Three series with twelve markets and an account with five orders. |

Some starter records exist to test boundaries. For example, Slack's #leadership channel is private and the bot is not a member, and Salesforce and HubSpot each hold one account, Helix Manufacturing, that the agent's token cannot read.

## Presets

A preset is a ready-made set of tools whose data fits together. List them with `ancha sandbox presets`.

| Preset | Name | Tools |
| - | - | - |
| `operations` | Engineering workspace | Slack, GitHub, Datadog, PagerDuty |
| `b2b-salesforce` | Salesforce revenue workspace | LinkedIn Ads, Salesforce, Gong, Google Ads, ChatGPT Ads, Google Analytics |
| `b2b-hubspot` | HubSpot revenue workspace | LinkedIn Ads, HubSpot, Gong, Google Ads, ChatGPT Ads, Google Analytics |

A new hosted workspace also starts with a **Support workspace** world: Slack and GitHub with the starter data above.

## Naming records with refs

Starter records have refs, short names that start with `$`. Checks and scene files use refs instead of generated IDs, for example `$slack_support` for the #support channel or `$github_orders` for `acme/orders`. Each [tool page](https://docs.ancha.io/tools/overview.md) lists the refs its starter data declares. In a scene file, you declare your own refs with `ref:` and use them with `$`. See [Test file](https://docs.ancha.io/reference/test-file.md).

## Time

Each world runs on a simulated clock. A scene's `start_time` sets when the world begins, and `time_scale` sets how fast simulated time runs. Starter history sits before the start, for example a Slack message posted 35 minutes earlier. Because the clock is simulated, the same world gives the same timestamps on every attempt.

## Static and living worlds

| Kind | Behavior |
| - | - |
| `static` | Nothing happens unless the agent acts. The starter scene is static. |
| `living` | The world has rules that act on their own while the agent works: a person posts in Slack after two minutes, a fault keeps a metric high until a fix is deployed, a monitor alerts and pages PagerDuty. This is the default for scene files. |

Living-world rules are written in a scene's `world_rules`. See [Test file](https://docs.ancha.io/reference/test-file.md#world-rules).

## Versions

Worlds you save in the hosted console or with `ancha world create` are versioned. Editing a world creates a new revision. A test keeps the revision it was saved with until you choose a newer one, so old results stay comparable. Archiving hides a world from normal lists and keeps its history.

## Where worlds come from

| You use | Define the world with |
| - | - |
| `ancha run` | A scene file: `twins`, `seed` and optional `world_rules`. See [Test file](https://docs.ancha.io/reference/test-file.md). |
| `ancha playground` | `ancha world create --tools slack,github`. See [`ancha world`](https://docs.ancha.io/cli/world). |
| Hosted console | The **Worlds** page. |
| Exploring by hand | `ancha sandbox create --preset operations`. See [`ancha sandbox`](https://docs.ancha.io/cli/sandbox). |


## Related topics

- [ancha world](https://docs.ancha.io/cli/world.md)
- [World lifecycle](https://docs.ancha.io/cli/world-lifecycle.md)
- [ancha world gen](https://docs.ancha.io/cli/world-gen.md)
- [CLI overview](https://docs.ancha.io/cli/overview.md)
- [Troubleshooting](https://docs.ancha.io/troubleshooting.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.