Activity — what ran, where, and what it decided
Needs you answers "what needs me?" Activity answers "what ran, where, and what did it decide?" Use Activity to look into a finished task, or a message that seems to have gone to the wrong agent.
Activity is a page of the Hub, the dashboard's home. It lists every run of every agent on your machines, newest first, with its result, what started it, how long it took and what it cost. A run is one task an agent worked on.

Scripted demo data; your team's names and machines will differ.
See the runs
- Browser: open the dashboard. The Hub opens.
- In the nav on the left, select Activity, under Work. On a phone, select More in the bottom bar, then Activity. The page's address is
/hub#page=activity. - Pick the result with the tabs under the title (All, Done, Failed, Running, Stopped) and the period with 24 h, 7 d or 30 d.
- Select a row to open it in place: its result, what it was asked and where it ran. Open the run opens its Task page with the full conversation.
One agent's runs are on its profile, under Activity. Old links to an agent's classic history page open that tab. The full steps are in Hub › See what the agents ran.
The timeline and the Map
The lane timeline and the Map are not on the Hub yet. They are still on the classic Activity page: on the Hub's Activity page, select Timeline next to Feed beside the title. The rest of this page describes them.
Each bar on the timeline is one run. Small marks on a run show what it recorded: a decision, a warning, friction (something that slowed it down), or something to do later. A cross marks a canceled run.

The three scripted runs appear on the agent timeline.
Find a run on the timeline
- Browser: on the Hub's Activity page, select Timeline beside the title.
- Pick how far back to look: 6h, 24h, 3d or 7d.
- Next to Lanes by, pick how to group the runs: Agent, Client, Project, Channel, Person or Node (machine).
- Find the lane you care about and the bar at the time you expect.
- Select the bar. Its details open below the timeline: the route the message took and the outcome.
- To pick up runs that finished since you opened the page, select Refresh.

Grouped by Client. Runs whose chat isn't linked to a client land in unmapped.

Grouped by Channel: where each message came from.
Grouped by Person, each lane is someone in your people list, or Owner for work you start at this computer's own voice, phone app or dashboard when you list no owner. Every other run shares the lane no known person: schedules, work an agent starts on its own, outside systems, and senders that match nobody in the list. A run's details name the person on a Started by line. AgentX never guesses a person from a display name. As on the map, the person is who the run is recorded under, not proof of who asked: an agent that posts with your account from outside AgentX lands in your lane.
The Map view, next to Timeline, draws the whole team as a transit map: projects are lines, agents are stations, and work in progress moves along them.

Dana's merge request event comes in through GitLab and reaches CX, which asks Builder, which asks Scout on another computer. The work ends on the Shop line.
Read the map from left to right. The first column is the initiator: who or what started each piece of work. The second column is the channel it came in through: GitLab, GitHub, Telegram, Voice, Cron and so on. Each piece of work (a train) then passes every agent that handed it on, in order, and ends on its project's line.
An initiator is one of three kinds:
- A person (a plain box). This is someone in your people list, or Owner for work you start at this computer's own voice, phone app or dashboard. A sender that matches nobody in the list reads Unknown. AgentX never guesses a person from a display name.
- AgentX (a filled box). This is work the system starts itself: a schedule (cron), a workflow step, or an agent acting on its own.
- An external system (a dashed box). This is an outside service that is not a person, named after where it came in: a webhook, a call to the Web API, or a bot account on GitHub or GitLab.
The initiator is who the work is recorded under. It is not proof of who asked. An agent that posts with a person's account from outside AgentX (the gh command, for example) reads as that person. A hand-off names the person its first run recorded, and a program that calls this computer's API can write that name.
A hand-off keeps the initiator of the work it belongs to. If Dana's merge request passes three agents, all three hops still start at Dana.
A hop is one agent asking another agent for help. When one agent asks a second, and the second asks a third, the map draws each hop. That holds when the agents run on different computers in your mesh (the computers linked together): the map reads each computer's own records. An agent only appears on a route when it really handled the work. For example, an agent that asks about a merge request later does not become its starting point.
The dotted line from a channel ends at the agent that received the work. It goes around every other agent, so it never looks like a hand-off that did not happen.
A chat you start in the phone app, typed or spoken, comes in from Phone app and names you (operator) as the person who started it. That holds when the agent runs on another computer in your mesh too. In its details, a spoken message says Voice and a typed one says Phone app. Work that one agent hands to another, with no earlier channel on record, comes in from Mesh (A2A).
When an agent hands work off and gets the answer later, the answer shows as a hop back to the agent that asked. It is marked ↩ on the train's list of hops. It never starts a new train.
See how a piece of work travelled
- Browser: open Activity and select Map.
- Select a train (a pill on a line, such as !48). A card opens on the right.
- Read the route at the top of the card: the initiator, the channel, every agent in order, then the line.
- Under Hops, read each hand-off with its time and the computer it ran on.
- Select a hop in that list to see the message that agent sent, its time and its result.
- Select Show more to read a longer message, or Open run details for the full run.
- Press Esc, or select ✕, to close the card.


Look at an initiator, a channel, a station or a track
Everything on the map opens a card, with the mouse or with Tab and Enter.
- Browser: select an initiator in the first column, such as Dana or AgentX. Its card says which kind it is and lists what it started: each train, the channel it came through, the sender's name on that channel and the time.
- Select a channel in the second column, such as GitLab. Its card lists what came in: the issue or merge request, the event, who sent it and when, with a link to open it.
- Select a station (a round agent marker). Its card shows the agent, the computer it runs on, what it is running now and its recent runs. Select a run to open its details.
- Select a coloured track between two stations. Its card lists every hand-off along that track.



Long chains
When a train passes 4 or more agents, the map keeps it readable. It draws the first agent and the last two, and puts a +n button on the track between them. n is the number of agents hidden there.
- Browser: select +n on the track. The hidden agents appear in order.
- To fold them again, select Collapse long routes at the bottom of the map.
The train's card always lists every hop. On a long chain it shows the first and last hops and a +n hops button for the rest.
The line board, active only, and the idle stations switch still apply. Selecting a line on the board fades the other lines, their hops and their initiator and channel links. On a phone, open a line to see its route from top to bottom, starting with the initiator.

Check it worked
- Browser: send an agent a small task, and wait for it to finish.
- On the Hub, select Activity in the nav, with 24 h picked. The run is the first row, marked Done.
- Select Timeline beside the title. A new bar appears in that agent's lane. Select Refresh if the page was already open.
- Select the bar. Its details show the channel it came from and its result.
- Select Map, then select the train for that task. Its route starts with who started it, then the channel you used, and lists every agent that worked on it.
If something is wrong
- A message never appears: it may not have reached AgentX at all. Go to It's not answering and check whether the channel reached the daemon.
- Runs sit under unmapped when grouped by Client: that chat isn't linked to a client yet. The list that links chats to clients is under Settings › Business, a tab that only appears when the business features are switched on (
business.enabledinagentx.json). Restart the daemon after changing it. - A machine's runs are missing: that machine may be unreachable. The Hub's Activity page names a machine that does not answer above the runs; see also Running now.
- The timeline is empty: widen the window to 7d. Nothing may have run in the last 24 hours.
- A train starts at Mesh (A2A) instead of where it came from: the run that started it is older than the window, or the computer it ran on did not answer. Widen the window, or check that computer under the Hub's Running now. Work handed off by a computer with an older AgentX carries no starting point; update AgentX on every computer in the mesh.
- A run sits under no known person when grouped by Person: nobody in your people list started it, or it ran before that person was listed. Unlike the map, the timeline does not rename older runs. A computer in your mesh with an older AgentX sends no person, so all its runs land there; update AgentX on it. Each computer names people from its own list: give a person the same
idon every computer, or they get two lanes. - You have two lanes when grouped by Person, Owner and your own name: the Owner runs started at this computer before you listed yourself as its owner. Runs since then are under your name. The timeline does not rename older runs; they leave as the window moves on.
- A person shows as Unknown: their login or id on that channel is not in your people list. Add it under
peopleinagentx.json: see Tell agents who is who. The map then names them, including for work already on the map. - Your own voice or phone chats show as Unknown: they were sent before this computer was updated, when AgentX did not yet record who started them. New ones read Owner. If you list two owners, AgentX cannot tell them apart at this computer and shows Unknown. The same holds for AgentX Voice.
- A hop you expected is missing: the map links a hop to the run that was in progress when the agent asked. If both computers' clocks are far apart, the link can fail. Set both computers to set their time automatically.
- A phone chat shows as Mesh (A2A) or Schedule on the map: it ran on a computer with an older AgentX, or it was sent before the update. Update AgentX on the computer that runs the agent and on the one your phone is paired with, then restart it there. New phone chats then come in from Phone app.
