Working with collaborators

Invite up to two people to build a project with you. Every AI run they start spends your credits, not theirs.

Inviting someone

Open Collaborators — the share icon in the workspace header, or Settings → Collaborators.

1. Type the person's address in the email field, which prompts you with [email protected].
2. Click Invite.
3. They get an email with an accept link.

The panel reports seats as 1 / 2 seats used. A seat is taken by an active collaborator or by a pending invite. When both are used the form is disabled and reads Seats are full. Remove a collaborator or cancel an invite to add another.

Two invites are refused outright: your own address (You can't invite yourself.) and someone already on the project (This person is already a collaborator.). Re-inviting the same address just issues a fresh link, without taking a second seat.

Accepting an invite

The link opens the accept page. The person has to be signed in, and signed in with the same email the invite was sent to — the invite is matched to the account's address, not to whoever opens the link.

If the addresses differ, the page shows the invited one beside the one they are using and keeps Accept invite disabled. Signing in with the right account fixes it; if they have no account yet, signing in creates one.

After they click Accept invite, they land in the project as an editor.

Links are valid for 7 days. After that the page reads This invite has expired. and you send a new one.

What an editor can do

Almost everything you can. An editor can:

• Send prompts, approve plans and designs, stop and retry runs.
• Start the preview and read the code.
• Publish, view deployment history, roll back, and edit environment variables.
• Browse the database, run SQL, and change API settings.
• Rename the project and edit its description.

These stay with the owner:

Editors do not see those controls, carry an Editor badge in the header, and have the Pending invites list hidden. Anyone who reaches an owner-only action another way gets Only the project owner can do this.

Runs are billed to the owner

Every AI run on the project is charged to the owner's credit allowance, no matter who pressed Generate. That covers prompts, each step of a plan, design rounds, mobile screens, and retries. The collaborator's own allowance is never touched.

Two consequences:

• A collaborator can spend your entire monthly allowance.
• When it runs out, it runs out for both of you — their composer is disabled too and reads Out of credits this period. Top-up credits are yours as well, so they keep both composers working.

Invite people you trust with the bill. There is no per-collaborator cap and no way to give someone a separate budget.

More in how credits work.

Working at the same time

Everyone can have the project open at once. The other people's avatars appear in the header, and an avatar grows a pulsing ring while that person's prompt is running. A toast tells you when someone opens the project or starts a run.

In the chat, prompts you did not send are labelled with the sender's name and a collaborator chip, so the history stays readable.

Runs on one project are serialised: a second prompt waits for the first to finish. There is no file locking, though — two people prompting the same files in turn can still undo each other's work. Agree who is doing what.

Removing someone, and leaving

• Owner — click the remove icon on a collaborator's row, then Remove to confirm.
• Owner — a pending invite has a Cancel button that kills the link.
• Editor — Leave project at the bottom of the panel, then Yes, leave.

Access ends immediately. If the person had the project open, they are dropped out of it. A run already in flight finishes, and is still billed to the owner.

The owner cannot leave their own project — that returns The owner can't leave their own project. There is no ownership transfer: to hand a project over, export it and let the other person start from that code.

Limits & notes

• Two collaborator seats per project, on every plan. Pending invites hold a seat until accepted or cancelled.
• Invite links expire after 7 days and are only accepted by the exact address they were sent to.
• Collaborators are editors. There is no read-only or comment-only role.
• Every run a collaborator starts is billed to the owner.
• Removing someone does not undo their work — the code they prompted stays in the project.
• Ownership cannot be transferred.
• Limits may change during alpha.

Related

• How credits work — allowances, pricing, and running low.
• The workspace — presence, the header, and per-role controls.
• Creating & managing projects — renaming, deleting, ownership.
• Publish & deploy — what an editor can ship.