Collaborators

Collaborators are people who edit your game with you. They can chat with the agent, drag entities in Edit mode, tune Inspector fields, and publish — same access as the owner, minus member management.

When to use collaborators

• You're working with a co-creator — design + code, two devs, etc.
• You're teaching someone — pair-edit a game together.
• You're handing off work — let another person continue the project while you step away.

If the other person should only play (not edit), invite them as a Player instead. See Invite players.

Important: credit cost

Collaborator agent turns deduct from your (the owner's) credit balance. A collaborator can run up your credit usage with no limit unless you set one externally (just talk to them).

If you want to limit collaborator-driven credit use:

• Check the balance regularly via Settings → Credit Usage.
• See the per-turn deduction table to spot heavy-cost turns.
• Have the conversation: "Try to keep your turns small and focused."

We're considering per-collaborator quotas in a future release. For now, trust + visibility is the model.

Inviting a collaborator

Same UI as players, different role:

What the collaborator sees

After accepting:

• The project appears in their Projects page with a Collaborator badge.
• They can open it like any of their own projects and chat with the agent.
• They share the same workspace — the same files, the same chat history, the same edit-mode state.

Single-session lock

Only one person can have an editor session open at a time per project. This avoids two people's chats / edits stepping on each other.

• If you open the editor while a collaborator is in: their session is bumped. They see a "Session open elsewhere" modal with a Reconnect here button — clicking it bumps you back.
• The bump uses a clean WebSocket close code (4001), not a network drop.

In practice this is fine for "we're not both working at the same time" collaboration. For literal pair-editing, talk through what each session is for.

Chat history is shared

Every collaborator sees the full chat history. The chat panel doesn't attribute prompts to specific senders today — you'll just see the prompts in time order without a "who sent this" tag. (We may add this in the future.)

If you want a clear handoff: write a message like "@alice picking up here, going to add the boss fight." at the start of your session so the log is human-readable.

Removing a collaborator

In ≡▾ → Members → Collaborators, hover and click the X. Confirm.

Removed collaborators:

• Lose editor access immediately.
• Keep their Umicat account and any other projects they own or collaborate on.
• Their previous chat / edits remain in your project (the work is yours; the access is theirs).

Leaving a project you collaborate on

If you collaborate on someone else's project and want out, open the project → ≡▾ → Members → Leave. A confirm modal appears. Leaving revokes your access; the project is unaffected.

The owner cannot accidentally remove themselves — leaving is for non- owners only.

Pending invitations

Like player invites, pending collaborator invites show in Members with revoke buttons. They expire after ~7 days.

What collaborators can't do

Use case examples

Two-person team

You're the designer, your friend is the gameplay-tuning person. They
collaborate on the project; you both chat with the agent over time;
you sync on Discord about who's doing what.

Pair learning

You're showing a friend how to use Umicat. Add them as Collaborator.
You both have the editor open; they reconnect to bump you off when it's
their turn to drive.

Async handoff

You start a project, get tired, hand it off to a collaborator who
continues for a week, then hands back. The chat log shows what
happened while you were away.

Next steps