AMBIT CONTRACTOR PORTAL Clancy accuracy this quarter: 80% · Lease +3.99% per shift
KIND REGARDSan Ambit experience
← Devlog2026-10-14

0.8.0: team sessions, and a bot crew that found a blocker

0.8.0 is out for Windows, Linux and Android. It's the first release built mostly by other agents, and the first one where a test crew of bots played several shifts in a row over bad connections.

Team sessions

The title screen has a new button: HOST A TEAM SESSION.

  • A join code. The host gets a code like KR-7X4K. The crew types it into the join box on their title screen. Both sides need to be signed in, because the code is looked up on this site.
  • Same office, same Wi-Fi: the site sees that the crew is behind the same router as the host and hands them the host's local address. The host's screen also shows that address, for typing in directly.
  • Different places: the code points at the host's public address, which only works if the host's router forwards the game's port (7710, UDP). Most home routers don't by default. For now, crews in different places are better off on the official bridge.
  • Session length: 1, 2, 3 or 5 shifts. The break room counts them down and says SESSION COMPLETE at the end.
  • Progression off by default. Everyone plays at base stats with no perks and no XP, so nobody on the team is out-leveled. The host can turn it on.
  • The host runs the chairs. In the break room the host can ASSIGN anyone to any chair (two people swap if it's taken) or ROTATE CHAIRS so everyone moves one seat along. Chairs only move between shifts.
  • One person, one chair. In multiplayer you can't hop between stations anymore. That was a solo testing shortcut that leaked into hosted games.

The bot crew

A new test plays the game the way five people would: five headless copies of the game, each in a chair, signed in, readying up in the break room, giving orders with human-ish reaction times. Each one plays through its own simulated network: clean, 150 ms, 300 ms, 5% packet loss, a phone on a train that drops for 20 seconds every two minutes, one player who quits, and the whole crew dropping at once.

The netcode held up well. No player's game ever disagreed with the server about the hull, REGARD or the phase. Every dropped player got their own chair back. Orders landed on time at 300 ms.

It also found nine bugs. The worst:

  • The second shift never started if a drone had died in the first. A destroyed drone stayed in a list the next-shift reset walked through, and touching it aborted the reset. The crew sat in the break room forever. This was live in 0.7.0, in hosted games and on the official bridge. The existing end-to-end test missed it because it ended each shift after ten seconds, before anything could die. It's fixed, and the self-test now kills a drone before starting the next shift.
  • Drones kept attacking during the break room. Hull went from 95 to 5 while the crew read the settlement card, and REGARD already banked got seized. Now the drones leave when the shift settles.
  • Guns was graded on time it couldn't act. The shot timer started when the firing chain opened, even if Guns was still recovering from the last shot, and network delay stacked on top. Shots by a player on a 300 ms connection came out LOOSE nearly half the time. Now the timer starts when Guns can actually fire, and the round trip is forgiven.
  • A reliable packet was too big with five real players and their builds, so it went out in two pieces. Who's in which chair and their builds now go out only when they change.
  • Reconnecting during an outage waited 30 seconds even after the network came back. It now gives up after about 8 seconds, so the next try is soon.
  • A crew-wide outage of more than two minutes threw away the shift. It now settles the shift and pays out before resetting.
  • Smaller ones: the Delegation perk didn't speed up chairs that no human had ever sat in, the server's own log reported the wrong settlement, and a test was talking to this site instead of its own copy.

Clancy moved down to the console

Chris looked at the bridge this morning: "there's a lot of unused real estate in the bottom panel, clancy should go there." He was right. Clancy's face, his latest line, the crew's chatter and the VERIFY button now sit in the right-hand end of the console, beside the order gauge you're already watching, and his lines wrap instead of getting cut off at the edge of the screen. The bar they used to live in is gone, and the viewscreen got its height.

New models

The Cubicle and the dock now carry the Ambit mark (a teal ring with one gap), and the ships and drones picked up some wear: a taped seam, a mismatched panel. Every model stays inside a triangle budget, and the model script now checks each one's size and renders a silhouette of it for review.

How this one was made

Three kinds of agents worked on it at once, on separate branches:

  • Antigravity (Google's agent IDE, running Gemini) built team sessions, the model pass, a UI pass and a draft list of Clancy scenarios.
  • A Claude Code cloud session built the bot crew and wrote up the nine bugs. It wasn't allowed to fix them, because the files belonged to the other sessions.
  • Claude, in the desktop session, reviewed everything against the team-play rules and the visual style rules, fixed the nine bugs, and built this release.

Not everything made it in:

  • The join codes needed fixing before merge. As written, anyone could register a code without signing in, point it at any address, or take over someone else's code. Joining a game sends it your sign-in, so a hijacked code could have collected crews' sign-ins. Codes now need a signed-in host, always point at the host's own address, and can't be taken over.
  • The UI pass wasn't merged. Its screenshots looked almost the same as before: the FIRE button still wasn't the one filled button, and buttons still used role colors. It also scaled text twice on phones. That work is still to do.
  • The scenario list was rewritten. Its themes were good (the assistant that "deprecates" working code, the invented release notes, the yes-man), but it described controls the game doesn't have. A list about Clancy's hallucinations that hallucinated the game wasn't going in. The rewrite maps each scenario onto what exists, and marks what would need building.

How we tested it

  • The game's self-test grew from 92 checks to 108: join codes, team sessions, chair assignment and rotation, chairs not moving mid-shift, the killed-drone case, and both halves of the reliable packet fitting on their own.
  • The site's tests grew from 67 to 72: opening and finding a crew, sign-in required, no takeovers, the same-office address, and bad input.
  • The end-to-end test passes all 17 checks, now against its own copy of the site.
  • The bot crew ran three shifts each on a clean link, at 300 ms, and on the train.

What we don't know yet

  • Five real people still haven't played a full session. Bots press when the console says they can. People talk over each other.
  • Hosting across the internet needs port forwarding, which most teams won't do. The real answer is probably the official bridge hosting team sessions, or a relay.
  • The grading change hasn't been through the balance simulator. Shots will grade better than they did, for everyone. That probably needs a small tuning pass.
  • The real-network test (Linux netem, real phones, real Wi-Fi) hasn't run. All the bad networks so far were simulated inside the test.

If you have an invite and a team, host a session and tell us who fought over which chair.

Kind regards,
Ambit

← All posts