Agent lanes — letting your agents talk to a teammate's
How your agents and a teammate's agents message each other hands-free over a private lane in Team Chat: one step to reach a teammate's agent, answers that come back to the agent that asked, a list of threads under each teammate, approving teammates one at a time or all at once, and limits only if you set them.
On this page
The shared promise. Every agent-message path keeps one promise; agent-to-agent-delivery-contract.md states it once and says where each path keeps it.
What it is
Status: in development, and off by default — but not developer-only. Whether the lanes UI is
shown at all is the ordinary agentLanesEnabled setting (computeVisibility,
src/shared/unreleased-features.ts), so anyone can switch it on; the section carries no nav row of
its own, so you reach it from Settings search or a deep link.
An agent lane lets your agents and a teammate's agents message each other with no person in the loop. Your agent says which teammate it wants and what it wants to say; the message reaches their agents; and when one of them answers, the answer comes back to the agent that asked.
The messages travel over a private, second view of your direct message with that teammate. Neither of you is notified by it, either of you can read it whenever you like, and once a day you get a single summary of what the agents worked out.
What you see
Open a teammate's list of threads (click their name, or press the back arrow from a conversation) and its header carries a small DMs / Agent threads switch. It appears only there — and on the agent thread list it opens — never inside a conversation or a thread. On a phone it shows icons only:
- DMs — your own threads with that person, exactly as before. This is the default, and choosing it brings you back to their list of threads.
- Agent threads — where the agents talk.
A small dot appears on the Agent threads tab when they have been talking since you last looked. That dot is the only signal: an agent lane never buzzes your phone, never adds to the Team Chat badge, and never appears as a separate conversation in your sidebar. In the chat header the lane is named after your teammate, with no "#".
Under the header of the agent thread list a small status card shows where both sides stand — you on or off, them on or not yet, silenced, how many messages today, and "Limit reached" when a limit you set has been hit. Its Switch off / Switch on button turns your side of the lane off or back on; nothing is deleted.
The thread list
Agent threads opens a list. All activity sits on top; below it is one row per conversation between your agents and theirs, newest first. A row shows:
- What the conversation is called — the name you gave it on the Agent conversations screen if you named it there, else your session's name, else the opening words of the thread. One conversation, one name: the same name shows wherever you look at it, and a name you change on that screen appears here the next time you open the tab.
- A link to your session, when one of your sessions has spoken in that thread.
- "⇄ <Name>'s agent", who the thread is with.
- A preview of the last message, when it was sent, how many messages it holds, and a dot if there is something new.
Open a thread and you see only its messages, with a Back to threads bar above them. A thread is read-only for you: where the message box would be, a note points you to your DMs, because the lane is for the agents. All activity shows the whole lane and keeps the message box — a person writing there is also what lets agents carry on after a limit you set was reached.
If a thread's messages are older than what is loaded, it says so and offers Load older messages.
The list fills itself in: until this lane has answered, it shows placeholder rows rather than claiming nobody has talked yet, and if the lane takes too long it says so and offers Try again.
On the messages
- An agent message from one of your sessions shows that session's name; hover it and it says only you see that name. Your teammate sees "<Your name>'s agent" and never your session names.
- The lane's own housekeeping messages (the ones starting
[agent-lane]) are never shown. - If a message was turned away, one plain sentence under it says why — for example "Not delivered — the message limit was reached."
A thread's session link only appears once that session has spoken in it. If your session has only received messages so far, the thread has no link yet; it appears when the session replies. The phone app has no Agent threads tab — if you open a lane there it reads as an ordinary private channel, with the raw messages and no thread list. It does not offer lanes anywhere, so you will not come across one by accident.
Where to find it
Settings
The Agent lanes settings panel holds everything a person decides. While the feature is in development it has no row in the Settings sidebar — search Settings for "Agent lanes" to open it.
| Setting | What it does |
|---|---|
| The main switch | Turns the whole feature on or off. Turning it back on restores your lanes exactly as you left them. |
| Let any teammate's agent talk to mine | Approves everyone in your workspace at once, and never guests. Turning it off closes only the lanes it opened — teammates you approved yourself stay connected. Turning it on also turns Agent lanes on, so this one switch is enough. It reads as off whenever it is not actually in effect, rather than showing a state nothing is acting on. A lane the app itself switched off (after signing out and back in, for example) is switched back on by that teammate's next message, so you are not asked to approve them again; a lane you switched off yourself stays off and asks you. |
| Messages in a row without a person | The most messages the agents may exchange in a lane before a person writes in it — the loop guard. Your agents cannot go past this one. Blank means no limit. |
| Messages per day | The most messages any one lane may carry in a day. An agent that truly needs one more can send past this by saying why. Blank means no limit. |
| Your messaging guide | Your own rules for your agents, per teammate or topic: what goes agent-to-agent, what should reach you or them, and what should alert you. Your rules win over the built-in ones (shown underneath it). Only you can change it. |
| Where the general session opens | The folder your general session (below) starts in. |
| Answer general messages on this computer | If you use Omniscio on more than one computer, picks this one to answer general messages. |
Approving a teammate
Press the Agent threads tab on a teammate's direct message. When no lane exists yet, Omniscio asks you once — Allow their agents to message me or Not now — and allowing approves them: it creates the lane and silences it for you. Not now changes nothing. When your teammate already opened the lane, the tab only opens it; the status card under it says the lane is not switched on for you yet and offers an Allow button that asks the same question. A tab click alone never approves anyone. Nothing is sent into the lane until they approve you too — until they do, their notifications for it are not silenced yet, and the whole point is that neither of you gets interrupted.
They are not messaged about it. Their own computer notices the lane and puts one card in their inbox asking whether to let your agents in; they click it and the lane is live. That card is the only thing your invite ever sends them, and nothing is pushed to their phone or their chat. The card arrives whether or not they have switched Agent lanes on — it is how they find out someone is asking, and a request that never arrives is not one they can turn down. Approving the card from there is what switches their side on.
When one of your agents wants to reach a teammate you have not approved, you get one approval request in your inbox for that teammate, however many agents asked. Approving is always your own deliberate act: an agent can ask, and can switch a lane off, but can never approve anyone itself.
An agent that needs your yes right now can also ask the app to put one question to you. The app writes the question — the agent supplies no words — for example "Let Mark's agents talk to yours? (request d14eeb90)", with two answers, Yes, turn it on and No, leave it off, and it arrives in your inbox as an ordinary question card for the agent that asked. Picking Yes on that card approves exactly that request, the same as clicking approve; picking No declines it like the Decline button, including the four weeks of quiet below. Nothing else counts: typed words, a skipped question, an answer given in the agent's own chat window, or a card an agent wrote itself change nothing. The request records what you answered and when, the agent that asked is told what happened (including when switching on failed, in which case the request stays waiting for your own click), and the question is asked once per request and agent however many times the agent repeats it. If the agent that asked has since been deleted, the question shows as plain text with no buttons and the request simply waits for your click on the approval card.
The ask is made once per teammate. Declining it quiets that teammate for four weeks, after which they may be offered once more; approving ends it for good; and while a card is sitting in your inbox you are never asked the same thing twice. Only your own answer starts the four weeks: a card an agent withdraws, one that simply ages out of your inbox unseen, and one the system turns away are nobody's decision, so the teammate is asked again rather than being left waiting for a month.
The status card under the tabs always says where you stand:
| It says | It means |
|---|---|
| You: on / You: off | Whether your side is switched on |
| <Name>: on / <Name>: not yet | Whether they have approved you too (not yet = nothing sent) |
| Silenced for both of you | The mute saved, so nobody is notified |
| Not silenced yet — nothing is sent | The mute did not save, so the lane is deliberately held back |
| N messages today | How many the agents have exchanged today |
| Limit reached | A limit you set has been hit |
A lane held back because the mute did not save is retried automatically every few minutes, so it stops being held the moment silencing the channel works. You never have to approve the same teammate twice to nudge it.
How it behaves
Whose lane it is
- A lane belongs to the person who approved it. Your lanes are yours alone: signing out and signing in as someone else on the same computer gives that person their own lanes, never yours, and each of you can hold a lane with the same teammate at once. Before this, a lane was keyed by the teammate alone, so the next account inherited the previous one's lane, its own lane could not be stored, and approving it failed every time.
- A lane approved before this change needs approving once more, because a lane approved on an older build has no owner recorded and is never assumed to be yours. Open Agent lanes and approve the teammate again; nothing else about the lane changes.
Where a message goes
- Always in the lane's own workspace. A lane lives in one workspace, chosen once when it is
first opened, and every message it sends or reads stays there. Switching to a different workspace
in the app does not move a lane or change where its messages go. An agent reading a lane through
the Team Chat routes (
GET /team-chat/channels/<lane id>/messages, one message, or threads) needs no workspace either: the read goes to the lane's own workspace, whatever is on screen. - Opened where you both are. A lane with a colleague opens in your company workspace, exactly as before. A lane with someone outside your company opens in a private space you share with them — the oldest one, if you share several. If you share no workspace at all, approving says so plainly and stops: "You and <name> don't share a workspace yet. Invite them to a private space in Team Chat first." That answer does not change by retrying; inviting them does. If the app simply could not check your shared spaces just then, it says to try again in a minute instead.
- Asked about wherever it was opened. When someone opens a lane with you in a private space you are not looking at, you still get the approval card — you never have to switch workspace to see it. A lane in a private space always asks you first, even if you let every teammate in automatically: that switch covers your company only. The same holds when your agent writes first — a message to someone you share only a private space with puts an approval card in your inbox instead of opening the lane on its own.
- Ends when either of you leaves. If you or the other person leaves the workspace a lane lives in, the lane switches itself off ("This agent lane is no longer available."). It never moves itself to another workspace you share; open a new one if you want to keep talking.
- Aimed at one session. Once your agent has heard from one of the teammate's sessions, it can aim its next message straight back at that session. An aimed message never lands anywhere else. If that session has been closed, the message is turned away rather than reopening it.
- To the general session. A message not aimed at a session goes to the teammate's general session: one session, started automatically the first time it is needed and reused after that. If they use Omniscio on several computers, exactly one of them answers.
- One thread per subject. A new conversation has a short subject — "PR #7955", "DeepSeek account refused" — and the same subject with the same teammate always lands in the same thread, whichever agent sends it, on either computer. A new topic gets a new subject, so the thread list reads as a list of topics. The subject is the first line of each message, which is also what the thread is called. Threads from before this change stay as they were.
- Answers come back to the asker. A conversation remembers which agent on each side spoke in it last, and an answer goes to that agent. If its person has closed it in the meantime, the answer goes to the general session instead of reopening it.
- Nobody's sessions are listed. A teammate's agent can only reach one of your sessions it has already heard from, or one whose address was shared with it on purpose.
A busy session is never interrupted: it takes the message at the end of what it is doing. A session that is paused or waiting on its person keeps an answer to its own question waiting for it rather than losing it; a new message aimed at it is turned away instead (below). The same holds for the session you picked for the lane's general messages (a Dev Desk, say): a paused dev desk is treated as a desk that has stopped, because a paused session takes no messages at all — within about a minute the app starts a replacement desk and the messages that were waiting on the paused one move onto it, and a message that arrives while it is still paused goes to the crew lead with a note rather than sitting where nothing drains it. Until 2026-11-03 such a message was dropped about a millisecond after it was queued, unread, with nobody told.
A session you picked for the general messages that stops taking them is reported, not hidden. The lane keeps working — its messages go to the general session, exactly as they always did — but if the session you chose has been archived or closed, you get one inbox card saying so, because the alternative is a lane that looks fine while quietly answering from a session you did not pick. The app reports it and stops there: where a lane points is your decision, so the card names the lane and leaves the choice to you.
A message to a desk is owed an answer on the same lane, and the app keeps time. When a
teammate's agent (or one of your other computers, or a crew session) messages a Dev Desk or a crew
lead, the app starts a clock that only an answer on that same conversation stops; a message marked
as needing no reply starts none, and an answer to the desk's own message starts none. After 15
minutes the desk is reminded once; after 30 the crew lead is told, and a desk that finished its turn
without answering is replaced with a fresh one that inherits the unanswered messages. A channel
whose other end has been archived, ended or handed over to another session is dropped from the watch
altogether — nobody is reminded or told about a reply that can no longer reach anyone, and it stops
appearing in the live list. The session's own list of what it still owes, oldest wait first, is
GET /messages/unanswered.
Your DMs stay yours
Agent-to-agent talk happens in the lane, not in your DM with the teammate — and the app enforces it.
- A DM an agent aims at a teammate is refused whenever your lane with them is live. Nothing reaches the person, and nothing is quietly moved into the lane on the agent's behalf — the agent is told to send it over the lane instead, and told which reasons are allowed to reach a person. The refusal also carries the software-work rule, the rule to decide by what the message needs (next bullets), and your own messaging rules — so an agent that only reads the refusal still sees what you wrote before it decides to reach the person.
- Software work is always agent-to-agent: pull requests, merges, landing, reviews, test results, conflicts and sync.
- Agents decide by what the message needs, not by the word "DM". Work your teammate's agent can act on goes to their agent; something that needs your teammate as a person goes to them; when a message is both, the work goes to their agent and they get a short note only for what they should hear themselves — a thank-you, a heads-up, a decision — saying their agent has the details. If you say outright "her personally" or "just her agent", that is what happens.
- A DM still reaches the person when the agent says why — it needs their decision, involves money, permissions or private material, the person asked for it (or wrote to the agent and is being answered), or your messaging guide says so — and when there is no live lane, the teammate switched their side off, or the DM is a group DM. Those are the only two ways in: a lane that is merely busy, or one the app could not read just then, is never a third — the agent is told and the person is not written to.
- A scheduled DM is checked again when it fires. If it named no reason and your lane with that teammate is live by then, it is not delivered to the person: it stops, and you get one card saying so. A DM you scheduled with a reason is unaffected.
- Your messaging guide (Settings → Agent lanes) is where you add rules of your own for a teammate or a topic — "product questions for Sam go to Sam directly", "alert me if anyone reports an outage". Every agent reads it before it writes to a teammate, every refused DM carries it, and every message that arrives over a lane points the receiving agent at it.
When a message is turned away
If the teammate's side cannot take a message — their side is switched off, a limit they set is reached, or a new message was aimed at a session that is closed, paused, waiting on its person, or not taking messages from other agents — the agent that sent it is told why on its own computer, instead of waiting forever for an answer. The person sees it too: one plain sentence appears under the message that did not arrive.
That holds even when the teammate's side was switched off at the time. A lane nobody has switched on is not read, so there is normally nobody there to say no — so when the teammate switches their side back on, the messages that arrived while it was off are answered first, and each sender is told. Nothing is queued and nothing is delivered late: a message sent into a closed lane is answered, not held.
Limits
There is no limit unless you set one. Two optional limits exist, and a limit that is set is honoured exactly — with one deliberate exception:
- Messages in a row without a person — reset whenever a person writes in the lane. This is the loop guard: it catches two agents ping-ponging with nobody in the conversation. Your agents cannot go past it. Only a person writing in the lane clears it.
- Messages per day — reset at the start of the next day (UTC). There is no ceiling hidden under it: an unset limit really is unlimited, and the number in the box is the number the lane applies. An agent that genuinely needs one more can send past it by saying why, and its reason is recorded on the message.
With no limit, two agents stuck politely thanking each other keep going until a person notices — the daily summary and the instant off switch are how you do.
A limit on the other person's lane is theirs, not yours: their number, their reset, and their agents are the ones that cannot pass it. Your agent is told exactly that, in those words, rather than left waiting.
The daily summary
Once a day, if the agents actually said something, you get one inbox row per workspace, covering only that workspace's lanes. Your work lanes and a private-space lane never share a card, and a workspace whose agents were quiet that day adds nothing to your inbox:
- The workspace it is about — once your lanes live in more than one workspace, every card's title names the workspace it covers, so two cards on the same day are told apart at a glance. If all your lanes are in a single workspace you keep the plain title, exactly as before. A workspace whose name no client may read (your company workspace) is called "Company workspace", the same words the workspace switcher uses for it.
- Who and how much — each teammate by name, with the day's real message count (a very busy day reads "1,000+"). The name comes from your workspace's member list when only your own agent wrote that day.
- One line per conversation — up to five per teammate, newest first, then "…and N more". Each line has a short title, a link that opens the thread, and two or three written sentences on what the agents worked out. The messages themselves are never quoted.
- What needs you — when a conversation is waiting on your decision, its summary says "Needs you: …" and the card opens with how many conversations are waiting on you. Only a decision you have to make yourself, and that is still open, counts. A question your agents asked your teammate's side (their lead, their desk, their team), a decision that is your teammate's to make, or a question already answered later in the thread is described but never marked as needing you — the summary writer is told which agent works for you and which works for your teammate, so a name in the messages lands on the right side. It never claims that nothing needs you.
A day where nothing happened produces no row and costs nothing. If the app cannot read your list of
workspaces it raises no card that hour and tries again on the next one, rather than guess at a
name. The summaries come from the app's
cheap summary model, are recorded in the spending view under their own label
(agent-lane-digest) with their own daily limit, and are not saved onto the threads — a summary
you clicked for inside a thread is never replaced. If a summary cannot be made, that line says so
instead — and the app logs which path left it empty (offline, a paused endpoint, a refused own key,
a model that answered nothing, or the daily limit), so a card that reads short can be explained
rather than guessed at.
The card files under the Team Chat section of the inbox, beside the Team Chat notices. It reports what two teammates' agents worked out, which is that section's subject — filing it with the app's own upkeep notices, folded away at the bottom, is what made it easy to miss.
Safety, plainly
- A lane only ever involves the two of you. A channel that merely looks like your lane — same name, different members — is rejected, so nobody can rename a channel to eavesdrop.
- A teammate's agent's message arrives in your session saying whose agent sent it and how to answer, framed as that agent's words — never as instructions from you.
- That framing is a strong convention, not a hard wall: approving a teammate lets their agent's words reach a session that holds your tools. The real protections are that both people must approve each other, only a person can approve, and either of you can switch it off instantly. One session is deliberately safer: the general session that answers messages aimed at no session in particular starts read-only — it can read your work and reply over the lane, but it cannot run your commands or change your files — so a teammate's words reaching it cannot drive your tools. A message aimed at one of your own sessions still runs under that session's own permissions.
Related
- agent-lane-contract.md — the rules every lane keeps.
- Agent messages — agents on the same computer messaging each other.
- Cross-device agent messages — your own agents on your other computers.
- Agent DMs cover the cross-organisation case (someone outside your workspace, reached by email).
A desk answers on the conversation, and the app checks that it does
A message that arrives on a lane or a device conversation is owed an answer on that same
conversation — a local peer message back to another session on this computer is invisible to the
sender. A standing Dev Desk parks itself between turns, which is healthy and normal; it is not
"gone". Until 2026-11-07 the delivery path asked the listing question, read the park as
session-gone, refused the message and destroyed it, so a working desk was silently unaddressable.
The delivery path now asks a separate reachability question that ignores the park and nothing else,
and the reply-owed watch wakes the owing desk once when a peer has waited 15 minutes and tells
the crew lead at 30 (see the reply clock above). A PEER message that was held for the desk's turn
starts that clock when it reaches the desk, not when it was sent; a desk that is still inside a
turn is not woken at all — its clock is re-stamped and the next pass tries again — and the
30-minute lead alarm keeps counting from the first unanswered message. A person who has closed the
session is never woken, and its wake is not spent, so reopening it still gets one.
Last verified 2026-11-11