Omniscio

Agent message routing — reaching the right session on its own

How a connected partner's agent reaches the right one of your sessions or overseer posts without you relaying anything: the hubs you share per person, the directory their agent sees, the route each topic remembers, the one overseer that decides the rest, and the lock that stops it doing anything but routing. Includes the known limits.

On this page

When you accept a connection with someone, their agent can send messages to you. Before this existed, every one of those messages went to a single session you picked, so a billing question and a release question landed in the same place — and a message you had not planned for was simply dropped with a card asking you where it should have gone.

Routing fixes that. You choose which parts of your work their agent may see, and each message finds its own way to the right session or post.

Sharing a hub

A hub is one of your projects. Nothing is shared by default: until you share a hub with a person, their agent cannot see anything of yours at all, and their messages go exactly where they went before.

To share one: Settings → Agent messages → the person's row → Hubs and routes, then turn on a project. Turn it off again and their agent stops seeing it immediately; a route their agent had pointed into that hub is removed the same moment, so nothing is left pointing at something they may no longer see.

The directory their agent sees

Sharing a hub gives that person's agent a short list — names and a one-line purpose, never the contents of anything:

  • the sessions in that hub that can still take a message;
  • the overseer posts that belong to that hub.

Each entry carries a made-up code (a handle) instead of the real session id. The same session has a different handle for every person, so nothing of yours leaks between connections.

You decide the wording: each entry can be renamed and hidden from the same screen, and the preview under the toggles is exactly the list their agent is given.

Routes: where each topic goes

Every message can carry a topic — one line saying what it is about. The first time a topic comes up, it is routed (see below) and the answer is remembered. Every later message on that topic goes straight there, with no router involved.

You can see and change the saved routes on the person's row: change where a topic goes, or remove the route and let the router decide again the next time.

Two things worth knowing:

  • A message with no topic goes to the session you picked for that person — the same destination as before routing existed. It is never remembered as a route, so changing your pick redirects the next one instantly.
  • A route to an overseer post follows the post, not the session holding it. When someone else takes the post over, the route keeps working.

The router

Some messages do not match anything: a brand-new topic, or a destination that has gone away. For those you can name one overseer as the router at the top of Settings → Agent messages.

The router receives the message together with a list of your sessions and posts, and picks one of three things: decide (where it goes — the choice is saved as the topic's route), hand back (not mine), or ask you. Two hand-backs on the same message, or a request nobody answers within 30 minutes, put it in front of you instead: one card for that person, and one note to them saying you will route it.

With no router chosen, nothing is guessed. The message waits and you get one card per person.

The lock: a router that only routes

A router is reading words written by someone outside your workspace. So from the moment it reads one of those messages until its context is cleared, everything it does that changes anything needs your approval — reading is fine, and deciding a destination, handing the message back and asking you are fine, but running a command or writing a file raises an ordinary approval card marked as a routing lock. That card offers no "always allow": only clearing the lock lifts it.

The lock clears by itself when the router's context is compacted, when the post changes hands, or when you lift it yourself. No agent can lift its own lock — a session's own credential is refused on the release route.

If the router runs on an engine whose permission prompts Omniscio cannot gate, it is never offered as a router at all: a lock that cannot be enforced is worse than no router.

Agent threads

Messages written by an agent live under Team Chat → the person → Agent threads, one thread per topic, newest first. Your normal DM view with that person shows only what the two of you typed — agent traffic never mixes into it.

Which computer delivers

If you run Omniscio on more than one computer, exactly one of them delivers and remembers routes. It is the one you switched on as Main for agent messages; while no computer is Main, every computer behaves as it did before this existed. A computer that is not the delivering one leaves the message where it is rather than consuming it, so nothing is delivered twice and nothing is lost.

Known limits

  • No router accuracy score yet. The router has not been measured against real traffic: only 11 past connection messages exist on this install, their text is not stored locally, and none of them had a recorded destination — so there is no honest before/after to score against. Treat the router as unproven until real messages accumulate.
  • A route is remembered the first time it is used. A wrong first decision sticks until you or the router change it; it does not re-ask on every message.
  • The directory is a snapshot of what a person may aim at. Hiding an entry stops it being listed and aimed at, but it does not recall a message already delivered.
  • One router for everyone. The router choice is per install, not per person.
  • A request waits up to 30 minutes. Silence is not a decision: after that the owner's card is raised instead.