Who is using this computer (the Performance Monitor's "Who is using it" tab)
The "Who is using it" tab of the Performance Monitor lists, biggest first, what is using this computer, who started each one and how much of the processor and memory it takes, now, over the last ten minutes or at a past time. It is an early-access feature that is off by default and works in the desktop app only; turn it on in the Lab. It reads a small local record the Performance Monitor already keeps, so looking at it does not make the computer slower.
On this page
What it is
When the computer feels slow while many agent sessions are running, the usual question is "who is using it?". Before this tab, the answer was spread over several developer readouts. This tab gives one answer in plain words, to a person who does not read terminals.
What the tab shows
- A headline sentence: how busy the computer is ("This computer is 80% busy.") and which kind of owner takes the biggest share. When memory is low or the processor is nearly full it says which one is the tight spot.
- A summary line by kind, biggest first.
- A ranked list of owners, ten shown at first with a "Show all" button for the rest. Each row carries:
- a plain name (a session shows its title),
- what it is in one sentence, when the app knows,
- who started it, for sessions,
- its share of this computer's processing power with a small bar (a share is a percentage of the whole computer, so one program using one of eight processor cores reads 12.5%),
- its memory,
- how many programs it runs.
- Remainder rows under the list, so the parts add up to the busy figure (see below).
- A freshness line, for example "As of 12 seconds ago · covers the last 30 seconds".
Who owns the load: the kinds of owner
Every program on the computer is charged to one owner, and every owner has one kind. The plain names on the screen are:
| Kind | Plain name on screen | What it covers |
|---|---|---|
| session | Agent sessions | One row per session, named by its title |
| app | The app's own background work | Omniscio's own helper programs and background jobs, one row per part |
| gate | Checks and test runs | Check and test machinery |
| ops | Scheduled jobs | The app's scheduled jobs |
| dev | Developer tools | Developer tooling on the computer |
| kernel | Windows itself | Shown as its own "Windows itself" line, not as a ranked row |
| plumbing | Shell utilities | Small command-line helper programs |
| other | Other programs | Programs that are not part of the app; the row carries a "Not part of the app" tag |
| orphan | Programs whose launcher has gone | Programs whose starter has exited, so no owner can be traced; also tagged "Not part of the app" |
Names for the app's own parts and for other programs come from the app's list of known causes, which says what a program is and why it uses the computer. A program the list does not know shows under its program file name, and a part of the app the list does not know shows under its own label with no explanation.
The remainder rows
The list shows only the biggest owners, so the account is closed with these rows, in this order. They exist so a missing number can never hide inside a total, and so what could not be explained is visible rather than dropped.
- All other (N): every owner too small to be stored on the line, summed. N is how many owners it holds. Windows itself is not part of this row.
- Windows itself: the share used by the operating system.
- Short-lived programs, not charged: programs that started and ended inside the 30-second window and could not be traced to any owner. It reads "not measured" when the app's record of ended programs could not be read, and "at least N%" when that record was cut off, because then some ended programs are missing.
- Not yet explained: the busy figure minus everything above, never below zero. It reads "not measured" when how busy the computer is could not be read.
- An overshoot note, only when the parts add up to more than the busy figure: "The parts add up to N% more than the busy figure, because the two readings are taken a moment apart." The excess is shown, never trimmed away.
How large "Not yet explained" is on a real computer has not been measured yet; it needs the feature running on the live app. The design charges each program once for its window (a program alive the whole window for what it used, a program born inside the window for everything since birth, a program that ended for only its in-window part), which is meant to keep that row small, but no figure is claimed here.
Where to find it
- Turn it on: Settings, then Lab, then the "Who is using this computer" switch (the setting is
resourceLedgerEnabled; it is off by default). Turning it off removes the tab and stops the recording described below. - Open it: the Performance Monitor row in the sidebar. With the feature on, the monitor shows a tab strip with two tabs, Who is using it (shown first) and Computer health (the existing blocks, unchanged). With the feature off, or outside the desktop app, the monitor shows the Computer health panel alone, exactly as before.
- Desktop only in this first landing. The phone and the remote web view do not get the tab: all three requests behind it are refused on that bridge. Phone support is planned for a later landing.
- It needs the Performance Monitor itself to be on. That is its own setting (Settings, then Performance, then Performance monitor), with three choices: automatic, on, off. Automatic turns it on only when the computer has enough memory.
How it behaves
Now, the last ten minutes, or a past time
A control row above the list picks the moment to show.
- Now shows the newest recorded line. A line covers the last 30 seconds, and the screen re-reads about every 15 seconds while the tab is open and visible.
- Last ten minutes shows the average of the lines recorded in the last ten minutes. The freshness line says how many readings went into it.
- A past time shows the line recorded at or before the time you choose. A "Show this time" box takes a date and time; it starts at ten minutes ago. The box states how far back the record reaches and refuses an earlier time, saying so. A strip reads "Showing <time>" with a "Back to now" button.
- A time is also refused as "outside the record" when no line sits within five minutes before it, for example in a gap when the monitor was off.
An Order by control sorts the list by share of this computer, by memory, or by file activity (how many file-information operations per second the owner's programs perform). The order is frozen while you look: it only changes when you press Refresh (or the R key when you are not typing in a box), change the time, or change the ordering. Refresh reads again.
How far back the record reaches is the time of the oldest line still kept, and the screen always states it. A line is small, and the record holds up to six files of up to 20 MB each (see below), but how many days that holds has not been measured on a real computer, so no figure is promised here; read the reach off the screen.
A row opens a detail pane
Click a row and a pane opens beside the list. On a narrow window it replaces the list, with a Close button. The pane shows:
- the name and what it is,
- Started by, for a session: a chain ending at the person ("You, <date>"), at a named schedule or automation ("Omniscio, automatically" or the schedule's own name), or at "Not recorded" when the link is missing. A session started by another session lists that session first and keeps going, up to eight links. A session the app started never ends at a person.
- Last ten minutes for this owner: average share, peak share and how many programs it started,
- Running now: the owner's programs, biggest first (up to 50), each with its share, memory and how long it has been running. This takes one live reading of the computer, at most one in eight seconds, and it is the only part of the tab that does.
- One action, for a session: "Open this session".
Keyboard focus moves into the pane when it opens and returns to the row when you close it (Escape also closes it).
At a past time the pane lists the recorded programs at that time instead, from the older, larger program-level record. That record is shorter than the owner record. If the chosen time is older than it holds, the pane says "Program detail reaches back only to <time>." and still shows the name, started-by chain and ten-minute figures. An owner that the owner record lists but whose programs were too small to appear in the program-level record still shows its name, started-by chain, ten-minute figures and action, with no program list. If neither record knows the owner the pane says "This is no longer running."
A program opens its command
In the "Running now" list, click a program to see its exact command text, with a Copy button. This is the one place command text appears, and these promises hold:
- Secrets are removed. The text goes through the app's general secret scrubber, and then every value after a flag whose name contains key, token, secret, pass, pwd, auth, credential or bearer is replaced with
[REDACTED], in the forms--flag value,--flag=value,token=valueandBearer value. A single-dash flag that starts with p is ambiguous, so it hides both its attached tail and its next value:-pSecretand-password Xboth read-p[REDACTED] ..., and a harmlessmkdir -p dirreads-p [REDACTED]. This is on purpose. - It is bounded. At most 256 characters; a longer command carries a "Shortened" note.
- It is live only. The text is read for a program that is running now, matched by its process number and exact start time; a program that has ended says "This program has ended." and one Windows will not describe says "Windows would not show this program's command."
- It is never saved. It is not written to the record, not included in the list, the detail pane or the local route, and not sent anywhere.
- It never leaves the desktop. The request is refused on the phone and web bridge.
- The panel says it in one line: "Secrets are removed. Shown only on this computer and never saved." It also shows the chain of programs that started this one.
What is recorded, and for how long
The Performance Monitor already looks over every program once every 30 seconds and keeps a program-level history. With the feature on, the same 30-second pass also writes one compact line per tick to a rotating file named owner-summary.jsonl in the app's logs folder. Everything on this tab except the "Running now" list, the command and the program list at a past time is read from that one file. That is why looking costs no scan of the computer.
- What a line holds: the time and window length, the number of programs seen, the computer's totals (busy share, kernel share, free memory, commit), the owners it stores (key, label, kind, processor share, the part of it from programs that ended, memory, file-activity rate, program count, programs started), the sum of everything else per kind, the per-kind totals, how many ended programs were charged or could not be, the remainder figures, and how long building the line took. The stored owners are the top 25 by processor, the top 10 by memory and the top 10 by file activity, joined.
- What a line does not hold: no command text, and no list of an owner's programs. A session's label can carry its title (cut at 48 characters) and the first eight characters of its id; this is kept only in this local file, which never leaves the computer.
- How long: the file rotates at 20 MB, keeping five older copies, so at most six files of 20 MB. A new header line starts each file. The oldest line still kept sets "how far back the record reaches".
- When it is written: only while both the Performance Monitor and this feature are on, so it follows the Performance Monitor switch. The first line appears about 30 seconds after the monitor starts, because a line needs a previous reading to measure against. Turning the feature off stops new lines; it does not delete the file.
- A failure never harms the monitor. If a line cannot be built or written, the tick's existing program-level history is unaffected.
Every empty or edge state
| What you see | What it means |
|---|---|
| No tab strip, only the Computer health panel | The feature is off, or this is not the desktop app |
| "The performance monitor is off" with an "Open Performance settings" button | The Performance Monitor is off, so nothing is being recorded. A past time can still be read from older lines |
| "No reading yet" | No line exists for this view yet: about 30 seconds after the monitor starts, or no line in the last ten minutes |
| "The record stopped N ago. These are the last figures it wrote." | The newest line is more than five minutes old. The list still shows those last figures |
| "That time is outside the record" with the reach and a "Back to now" button | No line sits within five minutes before the chosen past time |
| "Not available on this computer" | The detail pane could not take a live reading of the computer. The list itself never shows this state in this landing |
| "Could not read who is using this computer. It retries on its own." | The read failed; the Now view re-reads every 15 seconds |
| Detail: "Could not read the details just now." | The detail read failed |
| Detail: "This is no longer running." | The owner is not in the live reading, and no record knows it |
What the numbers cannot tell you
- Program names and the "what it is" sentences from the known-causes list are in English only, in every display language. The other text on the tab is translated into the app's 35 languages.
- The add-up has been proven with unit cases of known load and a generated input of 3,000 programs, not with a captured real tick.
- It has not yet been seen running on a live computer, so the size of "Not yet explained" and the real reach of the record are not measured.
- It has not been verified on operating systems other than Windows.
The slowness alert names the owners
When the inbox card "Agent tool calls are slower than the 20-second goal" is raised (see Performance Monitor), its body gains one more paragraph from this record, for example: "Right now most of this computer is going to the app's own background work (N%); the biggest users are A (N%), B (N%) and C (N%)." The lead names the dominant kind, and up to three owners follow, each with its share, leaving out owners under 1%. The sentence appears only when the feature is on and the newest recorded line is under two minutes old. With no recent line, the card is exactly what it was.
What is not built yet
This is the first of five landings in the Resource Ledger program. These are not built yet:
- Landing 2: splitting the app's own background work by feature, merging the older attribution readouts into this one record, and phone support.
- Landing 3: a 48-hour record of command text, on this computer only.
- Landing 4: per-owner budgets.
- Landing 5: checks at the door that refuse whole classes of bad actions.
Related
- Performance Monitor: the Computer health tab and the alerts; this tab sits beside it.
- Performance Monitor, every block in detail: the reference behind the Computer health blocks.
- Resources diagnostic panel: the Settings panel where a single program can be stopped.
- Governance control and triage: what the app paces, and why.
- Computer feels slow? A step-by-step fix-it guide: what to try when the computer is slow.
Last verified 2026-11-17