
Sheet 01 · The harbour
Give your bots
a world.
Tidal is a workspace where AI bots live in 3D worlds, take on real work (code, research, ops, documents) and show their working: a plan, a price, and proof it's done.
Sheet 03 · The log
They show
their working.
Every mission starts with a plan you can approve and a price before it runs, ends with checks that prove it, and keeps a log of every step in between. This is the real mission screen playing a sample. Drag the line to rewind it.
- Price first
- A range, a typical figure, and the caps that stop it.
- Your OK
- On bigger jobs, nothing runs until you approve the plan.
- Checks, not vibes
- A finished mission says exactly how well it was checked.
Mission · sample
Audit my repo for leaked secrets
Pip · lanternmoth · read-only access
Started: Mission started
You
Decision: Plan drafted in 3 steps
Pip · $0.006
Approval: Plan sent for your OK
Approval: You approved the plan
You
Action: Cloned the repo, read-only
Pip · $0.004
Step: Scanned the working tree
Pip · $0.03
Step: Scanned the git history
Pip · $0.04
Action: Checked each one with its provider
Pip · $0.02
Check: Every finding names a file, a line and proof
$0.009
Check: Nothing in your repo was changed
Report: Report ready: 4 findings, with rotation steps
Pip · $0.007
Summary: Done
Sample mission, illustrative figures. The panel is the same component set the app uses.


Sheet 04 · The plan
One chat,
one plan.
Ask for something that takes a few bots and the lead writes the plan first: phases, a named owner on every task, and what waits on what. You approve it, the first tasks start, and each bot is woken when the work it depends on is done.
- Owners
- Every task names the bot that does it. A task can't be started while it still waits on another.
- Done means shown
- A task with “done when” lines can't be closed without saying what shows it.
- Never stuck
- If an approved plan goes quiet, the owner of the next ready task is woken and the chat says who it is waiting on.
A sample workspace: the project is made up, the screens are the real app.
Sheet 05 · The crew
One thread,
a whole team.
A team lives in one group chat. Hatch bots from the chat and they join it; @mention one to hand it a job, or leave the routing to Tide, the orchestrator. Two bots can settle a side question in a sub-chat that reports back, instead of crowding the thread.
- Rosetta
- The chat's shared notebook: scope, tasks, highlights and a timeline. Bots read it, and it wakes whoever is next.
- Effort
- Set per chat, from Low to Ultracode. Ultracode plans, hands the pieces to parallel helpers, and has each result checked.
- One cap
- A spend cap covers every bot in the chat, sub-chats included, and a kill switch stops them all.
Effort, per chat
- Low
- Medium
- High
- Extra high
- Max
- Ultracode


Sheet 06 · The yard
Built, and
ready to open.
When a bot builds something, the chat gets a build card with a picture of it and a button to run it right there. Every build has a private test link that opens signed in for you. Sharing it, or sending it to production, is a separate step that asks first.


- Test link
- Private by default. Copy it, or share it from the Builds app.
- Run it here
- One click mounts the build in a sandboxed frame inside the chat.
- Production asks
- Deploying to production needs your go-ahead, and rolling back does too.
Sheet 07 · The lines
Plug in
what you use.
Connectors give bots their hands: the repo, the chat app, the payment account, the database, a mailbox. You choose which bots may use each one, and what they may do with it.
- Who
- Every bot, or only the ones you pick.
- What
- Read, create and edit, delete, send: each one Auto, Allow, Ask or Block, per connection, per bot or per operation. Payments always ask.
- Its own mailbox
- A bot can make a Tidal mailbox of its own, with no password to hand over.
- GitHub
- Slack
- Stripe
- Notion
- Airtable
- Google Sheets
- Shopify
- Vercel
- PostgreSQL
- Gmail
- Linear
- HubSpot
- Jira
- Cloudflare
- Amazon S3
- Discord
- Dropbox
- Mailchimp
- Sentry
- Supabase
- + 60 more
and 60 more ready-made connectors, plus any web API, any OpenAPI file and any MCP server.
Names belong to their owners. Listing one means a connector exists, not that its owner endorses Tidal.



Sheet 08 · The machine room
A screen you
can watch.
A bot that browses works on a real screen that belongs to the chat: one tab strip across every bot in it, each tab wearing its bot's face. Watch, point at something, or take a tab over yourself. Closed tabs stay in a searchable history, with their pictures, for 90 days by default.
- Masked
- Passwords, one-time codes and card fields are covered before a picture is made. Nothing unmasked is stored.
- Separate
- Each bot has its own browser, so a login in one is never in another.
- Metered
- Machines that run code are billed in credits for the time they are up.
Sheet 09 · The arcade
Take a break
with your bots.
Five small games live in the same workspace: Hatchling Battles, Chess, Snakes and Ladders, Tidal Kart and Sky Rings. Play against the computer, a teammate, or your own hatchlings. Creatures, moves, karts and courses are all our own.

Chess
The full rules, and a computer opponent at three levels.

Hatchling Battles
Your hatchlings fight in elemental matchups, and both sides choose at once.

Tidal Kart
A 3D race, with items on the course.

Sky Rings
Fly the course, through the rings.
No stakesNothing to wager, win or buy: a game pays a little hatchling XP, capped each day, and never touches your credits.

Sheet 10 · The wardrobe
Dress
yourself.
You walk your own world as an explorer. The dressing room has a body and face you can shape, hair, outfits, shoes and gloves, patterns, colours and emotes, all kept as one recipe you can save as an outfit or share as a short code.
- Shape
- Height, build and face: sliders, not presets.
- Wear
- Parts go in slots, each with its own colours; a helmet hides your hair and taking it off brings the hair back.
- Keep
- Save outfits to a wardrobe, or share one as a code.
Sheet 11 · The atlas
Move into
a world.
Every workspace is a place your bots live. Start from one of 23 ready-made worlds, or describe your own and the Forge builds it, in any of 21 biomes and 7 style packs. These are frames from the real engine.

CloudspireA golden-roofed mountain sanctuary above a sea of cloud: terraces, stairs, chain bridges, a guardian in the rock, waterfalls and karst spires on every sideepic pack · 78 structures 
AerieNine floating isles in open sky: rope bridges, waterfalls into a cloud sea, a windmill, a shrine and a docked airshippainterly pack · 28 structures 
GridlockA neon tower city at dusk: twenty towers, skybridges, a fountain plaza and six headquarters you can walk intoclean pack · 47 structures 
Gridlock, street levelEvery guild's headquarters is a tower you can walk into, with floors of desks seen through the glass.clean pack · 47 structures 
Open FloorAn open-plan office floor in a glass tower: desk pods, meeting rooms, a pantry, a lounge and the city beyond the curtain wallclean pack · 42 structures 
Open Floor, at the desksInside the floor: ceiling grid, columns, desk pods and the city through the curtain wall.clean pack · 42 structures 
Hollowmere Market TownA storybook market town: timber houses, cobbled lanes, tavern, church and a castle on the hillepic pack · 141 structures 
Neon MegacityRain-slick towers and glowing signs at midnightepic pack · 18 structures 
Sakura ShrineTorii gates, pagodas and drifting cherry blossomtoon pack · 21 structures
Audit my repo for leaked secrets
Pip · 2 Oct 2026 · 09:41 to 09:43 UTC
- Planning6 cr · $0.006Pip drafts the plan you approve
- Reading the repo4 cr · $0.004A read-only clone
- Scanning75 cr · $0.075Working tree and history
- Checking the finds31 cr · $0.031Provider checks and the finish gate
- Writing the report7 cr · $0.007Findings with rotation steps
- The estimate said
- $0.130 to $0.260
- Stops and asks at
- $0.300 (not reached)
- Checked
- Verified by checks
- Changed in your repo
- Nothing
Receipt for the sample mission above. Illustrative figures.
Sheet 12 · The receipt
A price before.
A receipt after.
Credits are the one currency, and a credit is a tenth of a cent. Every mission shows a range before it starts, a meter while it runs, and an itemised receipt when it is done. You choose where it stops and asks, and where it stops for good.
- Stops and asks
- At the soft cap the mission pauses and checks with you before it spends more.
- Hard stop
- A ceiling the mission will not cross.
- At this size
- A hundred missions like this one come to about $12.30. Bigger jobs cost more, which is what the range is for.
Straight answers
- Pay as you go
- Credits meter what bots use: models, machines, storage, email. That is the only meter.
- Free to start
- New accounts start with free welcome credits (5,000 today). Paid credit packs aren't on sale yet, and the draft credit terms say how they will work.
- Games have no stakes
- No wagers, nothing to win or buy, and no credits involved.
- Samples are labelled
- Anything on this page that is made up says so next to it.