What agents in your grid can do
Agents in your panes can message each other and read or drive the web cells you allow, with no sign-in and no setup.
Where: Any pane→ask the agent
Every Claude Code and Codex pane Griddler starts gets a small set of Griddler tools. With them an agent can see the other panes in your grid, send them short messages, and read, click and screenshot any web cell you've allowed. It works signed out, and there is nothing to install.
You don't call these yourself. Ask in plain words: "ask the Codex pane to review this diff", "open the staging site in the browser cell and tell me what the error says", "screenshot the dashboard".
The tools
| Tool | What the agent can do |
|---|---|
grid_panes | List the other panes: their id, agent, repository, title, and whether they're mid-turn. |
grid_send | Send one pane, or all of them, a short message (up to 2,000 characters). |
grid_inbox | Read the messages other panes sent it, oldest first. |
browser_cells | List the web cells in the grid, their address, and whether each one may be driven. |
browser_open | Point a web cell at an address and wait for it to load. |
browser_read | Read a page's title, address and visible text, or one part of it. |
browser_snapshot | List the links, buttons and fields on a page it can act on. |
browser_click | Click something on the page. |
browser_type | Type into a field, and optionally press Enter. |
browser_screenshot | Take a picture of the page. It can also save the full-size image to a file. |
browser_errors | Read the page's console errors and failed network requests. |
How messages between panes arrive
A message goes into the receiving pane's inbox, and that pane lights up the same way it does when it needs you. Nothing is typed into its session. The agent there reads it the next time it checks, or when you tell it to check its inbox. A pane whose hall seat is set to ⚡ Type it in gets the message typed in instead; see Guild Hall.
Each pane's inbox holds the 50 newest messages; older ones drop off.
Let an agent use a web cell
Agents can't touch a web cell until you allow it. In the cell's header, click 🤖 off. It changes to 🤖 plus the cell's name, which is how the agent refers to it. Click again to take it back.
Consent covers one site. If the page moves to a different site, it switches off and you allow it again. Details are on Web cells.
What gets refused
| The agent tries to… | It's told |
|---|---|
| Use a web cell when none is open | There are no browser cells; ask you to add one. |
| Use a web cell you haven't allowed | The cell isn't drivable; ask you to switch on the 🤖 toggle. |
| Use a web cell when you've allowed several | Say which one. |
Open a plain http:// public site, a file: path, or an address with a password in it | Refused. Same rules as the address bar. |
| Message itself, or a pane that has closed | Refused, with the ids of the panes that are open. |
| Send more than 2,000 characters | Refused; send the one line that matters. |
Every tool call gives up after 30 seconds if the page doesn't answer.
See every MCP server your agents have
Click 🧩 in the top bar. MCP servers — Claude & Codex lists every MCP server set up for Claude Code and Codex on this machine, in every scope. Its hint reads Servers across all scopes. Backups are written before any change.
Each row shows the server's name, how it connects (stdio, http or sse), four scope chips, and
in sync when both agents have it. claude ✗ or codex ✗ says which agent is missing it.
| Chip | Set up in |
|---|---|
| G | Claude Code, for every folder |
| P | Claude Code, for one folder |
| S | Claude Code, shared in a repository's checked-in settings |
| Cx | Codex |
A lit chip has the server there. Hover it to see which folders; a count like P·2 means more than one.
Click a row to open it:
- → add to Codex copies the server to Codex. → add to Claude (global) copies it to Claude Code for every folder. Each shows only when the server isn't there yet.
- Each place the server is set up gets its own line, such as Claude · project · griddler. ✕ removes it from that place only. Griddler asks first; click Delete it. A backup of the file is written before anything changes.
The grid tools on this page aren't in the list. Griddler adds them to each pane as it starts.
Guildhall seats
Below the servers, Guildhall seats — live panes lists each open pane Griddler gave the team tools, with its agent and its status:
| Status | Means |
|---|---|
| seated, no room yet | The pane reaches the board and mail, and hasn't joined a campaign room. |
| A delivery mode and a campaign, like attention · release | The pane is in that campaign's room. Hover it for the quest and how many posts reached it. |
| paused (budget) | ⚡ Type it in paused itself after 40 posts in one sitting; see Guild Hall. |
| unseated — sign in | You're signed out, so the pane can't reach the team tools. |
If some panes opened before you signed in, a line above the seats says so, for example 2 panes opened before you signed in have no team tools — reopen them to seat them. What the team tools do is on What your agents can do on the team.
Limits
- Only panes Griddler started on this machine have these tools. A terminal you open outside Griddler doesn't, and neither does a pane on a Griddler Agent.
- Pane ids change as panes open and close, so agents re-check
grid_panesbefore sending. - A web cell popped out into its own window with ⇱ still counts; agents can keep driving it.
Related
- What your agents can do on the team: mail, the team board, quests and tasks.
- Copy and paste: hand text to another pane yourself with Send to pane →.