Team editing & AI Studio

Build it together, with people and AI

Up to 12 people can edit the same level live. Add AI Studio and nine AI teammates join them, each with a cursor in your world, building in front of you and waiting for your yes.

Team editing

Twelve people, one level, live

Team editing turns Stravyn into a shared workspace. One person hosts, up to eleven teammates join, and everyone builds the same project at once. You see each other's cursors, cameras and selections in each person's colour.

JHostRuns the team server
Host's screen during a team editing session
ATeammateJoined by address
Teammate's screen during the same team editing session

HostLive syncTeammate

How a session works

  1. Host a sessionOpen Team editing (👥) in the desktop app and press Host. Your computer runs the team server on port 7788. Add a password if you like.
  2. Teammates joinThey type your address, for example 192.168.1.20:7788, and press Join. The desktop app and the browser edition can both join.
  3. Build togetherPick a name and one of 16 colours. Changes appear for everyone as they happen, and a team chat keeps everyone talking.
  4. Play it togetherWith multiplayer on, press 🎮 Play together. Stravyn starts a test match in a private room and sends every teammate a Join card.
Team editing window with name, colour, session status, who has joined, the join address and team chatTeam editing window
Selection locksWhatever a teammate has selected is locked for everyone else until they deselect it.
Live drag previewWatch objects slide into place while a teammate is still dragging them.
Jump to a teammateClick their dot in the team bar to fly your camera to them. A 🎮 shows who is play-testing.
Nothing gets lostChanges are checked and synced regularly, and your own edits are never swallowed by incoming ones.
Your project stays safeJoining someone's session keeps the project you had open in Saved versions.
Session fullTwelve seats per session. A thirteenth person gets a clear "this team session is full" message.
LAN or onlineUse your home network, or run the dedicated Linux server so a team can build from anywhere.
Try it on one PCOpen two browser tabs and press Start here and Join from this tab to see how it feels.

AI Studio · nine teammates

A nine-person studio. You direct.

AI Studio puts a full game studio inside your project. The teammates work like people in a team-editing session: each has a cursor and a camera in your world, selects things, drags them and builds in front of you. Every change is tested and waits for your approval.

N
NovaCreative directorOwns the vision: the design pillars, the tone, and the review at every milestone.
S
SamProducerTurns your goal into phases and tasks, keeps the budget and cuts scope when needed.
M
MayaLevel designerBuilds the world: ground, roads, buildings, props, enemies and game rules.
L
LeoWriterWrites every word: names, dialogue, quests, menus and signs.
I
IrisEnvironment & lighting artistSets the mood: palette, lighting, fog and sky, and props that tell a story.
J
JunoUX / UI designerOwns the first five minutes: HUD, menus, prompts and accessibility.
E
EchoAudio designerMusic for each area and moment, ambience, and sounds that guide the player.
K
KaiBalancerTunes the numbers: health, damage, speed, prices and amounts.
T
TessTesterPlays your game in nine styles, tracks bugs, and proves every change.
AI Studio Team tab with all nine teammates ready, an order to Tess and her reply: 11 checks run and everything passedReal capture · Team tab

How it works

  1. Give an orderType it or press Talk and say it. "Maya, build a small village by the lake." "Kai, make it a little easier." Or give the whole team a goal: "Team, make this a zombie survival game."
  2. Watch them workThe teammate travels to the spot, selects the object in its own colour, and moves, builds or deletes one step at a time. Press the eye button and your view follows whoever is working.
  3. Tess proves itTest players run the same seeded runs before and after the change. A crash, a new error or a clear drop in the score, and the change is undone and logged as "tried, did not help".
  4. You decideOpen the report and replay each change before and after in the 3D view. Press "Why?" to see the goal, the reasoning, the evidence and how confident the team is. Then approve or reject.
AI Studio Report tab: Tess's test checklist covering player, goal, start-up, route, enemies, pick-ups and rules, with the list of changes waiting for approvalReport · test checklist and changes to approve

A real production

Big orders run like a studio project

Ask for a whole game and Sam plans it in phases. After each phase there is a gate: automatic checks plus a design review by Nova. You get a milestone review where you can approve, redirect or cut scope.

  1. Pitch
  2. Design document
  3. Greybox
  4. Vertical slice
  5. Content build
  6. Alpha
  7. Beta
  8. Polish
Studio board tab: production phases and the design rubric scoring the level out of 100 on route, landmark, safe start, cover, rewards, pacing, mood, audio and clarity
Studio boardPhases, gates, the design document, and a design score out of 100 for the level.
QA tab: playtest heatmap, intensity over time, results per play style, bug list and performance budget
QA dashboardA heatmap of paths, deaths and stuck spots, results per play style, a bug tracker and a performance budget.
Free AI tab with a 12 GB graphics card chosen: the best model for it and the three set-up steps
Free AIStravyn checks your computer, picks an open-source model that fits it, and sets it up.
Knows about 55 kinds of gameSurvival, racing, tower defence, farming, horror and more. Each comes with its own recipe, test plan and test player. Unknown genres are worked out from first principles.
Ghost previewsBefore a big change you see outlines of what would be added in green, moved in yellow and removed in red, and you say yes or no.
"Show me 3 versions"Ask for variations of a town square or an arena. Each one is built from the same starting point, and you pick the one to keep.
Numbers found by testingKai searches for the damage, health, prices and timers that hit your target, scored by test players on the same runs, and checks the economy over a whole session.
A tester's checklistTess checks that the goal can be walked to, that enemies can reach the player, and every script, menu, item, key, door, shop and dialogue.
They react to each otherWhen Maya adds enemies, Kai is pinged to check the balance. When the layout changes, Tess re-tests it. A shared board tracks who is doing what.
It learns your tasteChanges you approve become examples for next time. Ideas you reject are not proposed again, and repeated mistakes turn into rules for that teammate.
An AI director in your gameThe team can add a live director to the finished game that paces enemy spawns, tested on every play style before it is kept.
Each stays in their laneEvery role has its own list of what it may change, checked before anything is applied. Work outside it is handed to the right teammate.
Hands off what you holdA teammate never changes or deletes an object that you or another person has selected.
Talk to themSay a name, then the order. Each teammate answers in its own voice, and "Stop" always stops the team.
Honest about limitsFor each kind of game the team checks what the engine does well, what needs event sheets or Lua, and what it cannot do, and tells you.

People and AI together

One session, humans and AI side by side

Start AI Studio inside a team-editing session and everyone sees the AI cursors, selections and live drags. Anyone in the session can give orders or stop the team.

  • One computer runs the AI team for the whole session
  • Orders from teammates are labelled with their name in the chat and the notebook
  • In a multiplayer test, add up to 4 AI players that join and play alongside you
  • Watch a test run: see a test player play your level in the normal Play view
Tess playing the level: the status bar shows the test run in progress and her status reads Tess is playing the levelTess running a playtest

Which AI it uses. The free AI runs open-source models on your own PC through the open-source Ollama runtime: no account, no key, no cost, and nothing leaves your computer. You can also add your own AI key for a stronger model. Tess and Kai work right away with no AI at all; the other teammates need one of the two. On a small local model, Nova and Sam merge into one "Lead" and Iris and Echo into "Art & Audio" so the team still works.

AI Studio New in 1.0

Smarter, safer, easier to follow

Version 1.0 gives the team better tools, a memory for your game's world and style, and a clear bar for when a game is ready to ship. The old single AI assistant is gone: AI Studio replaces it.

A full log

The Log tab shows every order, reply, tool call and result. Export it as text or JSON. Your AI key is never written to it.

Is it ready to ship?

Each kind of game has a ship bar: what has to be true before it's ready. Ask the team and they check it point by point.

World bible & style guide

The team keeps notes on your world's names, history and look, and follows them in every change so the game stays consistent.

Pick a model per job

Use a fast model for small jobs and a stronger one for planning and writing. Prompt caching keeps a big session quick and cheap.

Rooms and little scenes

Maya can furnish building interiors room by room, and Iris places small story scenes: a camp left in a hurry, a crashed cart.

Mood by area

Iris sets fog, light and colour per area with mood zones, so a swamp feels different from the town next to it.

Wear, cables and rails

Age and dirty buildings and props, run power lines and string lights, and lay railway track across the land.

Towns, arenas, jump courses

New build tools lay out a whole town, a fight arena or a jumping course in one step, ready to tune.

A director's hand

The team learns the habits you approve and repeat, and uses them without being asked.

Logic and systems tools

The team writes event rules, wires objects, tests logic, and sets up quests, talks, shops, waves, bosses and the HUD.

Thinking tools

Inspect, find, plan, playtest and test scripts before changing anything, and look up the engine's own guides.

What a change touches

A change-impact report lists what else a change affects, and a walk-through camera shows it from the player's height.

Try it yourself

Bring your team. Or direct nine.

Start with the free demo, then pick the plan that fits how many people build with you.