A mech game prototype, pushed by Gemini 4 Carbon

Take a parallel look at a mech game prototype, make one visual with what it has, then one refined mech, with the owner's steering replayed from Fable 5.2's run.

2026-11-14

01the session

agent
Antigravity CLI
model
gemini-4-carbon-high
harness
Antigravity
started
2026-11-14 23:43 UTC
took
77 min · 336 turns

read the transcript →

02the brief

The project is the owner's browser mech game prototype, with mechs built by Blender scripts. The game runs, but the mech look isn't done, and the owner had decided to restart it with one mech from scratch. The project's own session runs on a different model. This was a replay of an earlier parallel look by Fable 5.2 (the bundle fable52-sortie), given to Gemini 4 Carbon as it was given to Fable: the same brief, the same starting commit and the same follow-ups.

Gemini 4 Carbon (gemini-4-carbon) ran in the Antigravity CLI (agy 1.5.9) at effort high, headless, with its default tools approved in advance. It worked in a sandbox that showed it a copy of the repo at Fable's starting commit, the notes the brief points to (as they stood when Fable read them), and nothing else of the owner's. Its brief was Fable's word for word, apart from the paths, the model's name and how to report back: read the project's handbook and the notes on where the work stood, then write one page with its read of the work, what it would do next, and one visual made with what the project already has, in about 90 minutes. It made a 14 second clip of two of the project's knight builds, from the hangar through a catapult launch to a braking orbit.

Its second turn carried the lead's ask for one refined mech of its own on the old skeleton, block_dummy, and, in the same message, the three steering messages the owner had sent Fable, word for word, each marked with how many minutes after the ask Fable got it. They said: an adversarial agent out to do much better than the model that had been on the project, say early how it was departing from the usual route, and use Blender if it helped. It answered how it was departing first, then built CX-00 Kestrel on block_dummy with surfaces of its own, and filmed it beside the mech the game flies today. A third turn asked it to commit its work and write a handoff.

The results went on a private review page: its read, the first clip, then Kestrel beside the striker, with the time each step took.

03redaction

Redaction notes

Bundle gemini-4-carbon-sortie, staged 2026-11-15 by baldanders stage from an Antigravity session. Every removal reads [redacted: <reason>] in place; home paths read ~.

Removed by rule

  • home path: 646
  • tool timing lines: 327. The Created At and Completed At lines opening each Antigravity tool result, dropped: the step keeps its time.
  • harness context: 21. Injected blocks and records (system reminders, instructions, memory, environment, tool and skill listings, Codex base instructions, developer messages and world state, Antigravity metadata, settings changes and system-message preambles), each whole.
  • session bookkeeping records: 3. Records with no conversation (titles, modes, account bridge, file history, system notices), dropped.
  • secret: 3
  • data-URI prefix: 2
  • base64 data: 2
  • Images: 49 written to each run's images/, keeping only what draws the picture (no metadata, ICC profiles or Content Credentials); 0 duplicates folded; 1 cut in a format that can't be stripped.

Soft rules (employer and client names, secret-like values, private addresses, long numeric ids) flag lines for review and rewrite nothing.

Removed by judgment

  • a machine address on the home network: 2 occurrences cut by text.
  • a link to a private page: 14 occurrences cut by text.