Test multiplayer with two agents

To test with two players at once, you need a second account in a second browser. Fill that seat with a friend, or pair it with its own agent. Then each agent plays and checks the game from its own seat.

One tab is one seat. Two tabs signed in to the same account are still one player, so a second account is the only way to get a second seat. Start with a lobby, as Set up a multiplayer lobby with an agent shows. It's how you'd playtest a board game prototype online with real people, only faster.

What you'll need#

• A second DiceyTable account. A friend's works too.
• A second browser, or a private window, signed in to that account.
• For a second agent: an API key created by that second account, and a second MCP client to use it.

Option 1: Invite a person#

The agent calls lobby_invite_link and gives you the share link. Send it to your friend yourself, since agents can't send invitations. Your friend joins, picks a seat and plays like normal.

This is the quickest way to see how the game feels to a human. It's also the only way to find out if your rules make sense to someone who didn't write them.

Option 2: Pair a second agent#

This gives you two agents playing against each other, each one checking its own side.

1. Sign the second browser in to the second account.
2. In that browser, create an API key in Settings ▸ AI agents.
3. Run a second MCP client with its own bridge, using that key. The simplest way is to set DICEYTABLE_TOKEN to the new key in that client's setup. The bridge command line reference lists the options.
4. In the second browser, open the lobby and pair the tab with the second agent's own pairing code.
5. Both agents join the same room, one seat each.

The two bridges share one connection point on your computer, and each tab pairs with its own agent. DiceyTable refuses to attach a tab signed in to a different account from the key, with ticket-user-mismatch. So the two agents can't cross over.

Why this is useful: two private views#

Each agent sees only its own seat's cards. Agent A can check what's in hand 1, and agent B can check hand 2. Neither can peek at the other's.

That makes this the right way to test hidden cards. A single agent can't do it, because it never sees more than one seat. Hidden cards and AI agents explains the rule. Both agents use the same checks as in a preview, so Play-test your game with an agent still applies.

What do the other players see?#

Everyone in the room sees an AI badge beside the name of any player with an agent attached. It shows in the lobby, the player list, chat, the activity log and on the seat's nameplate, in VR too. DiceyTable's server decides who has an agent, not your browser, so nobody can hide or fake the badge. The AI badge other players see has more.

What changes at a live table?#

A live room is stricter than a preview, because other people are in it.

• table_step_physics is refused. Physics runs at normal speed for everyone.
• table_reset waits for the host's click in the tab. In a preview it only needs confirm: true.
• If you're the host, screenshots use only your own view. See Take screenshots with an agent.
• tier: "ultra" screenshots wait for your click.
• Leaving or resetting the room is always yours. No agent tool kicks, bans or mutes a player at the table.

Next steps#

• Set up a multiplayer lobby with an agent: create the room both agents join.
• Hidden cards and AI agents: what each seat can and can't see.
• Create an API key: one key per account.