Activity
Cmdop does not have one activity feed. Each record stays where it was made: what an agent did is in that machine’s session history, permission decisions are on the machine, relay events are in the web console, and plan and payment events are in the account console. This page tells you which one to open.
What happened, and where the record of it lives:
Where to look
| You want to know | Look at |
|---|---|
| What an agent did on a machine | That machine’s session history, in the web console |
| Whether a request was allowed, asked, or denied | cmdop permissions audit on the machine — see Audit and logs |
| What the relay itself did | Server → Logs in the web console |
| Whether a scheduled task fired | Armed schedules, or the session it reported back into |
| Plan and payment events | The account console |
Records stay where they were made. Cmdop does not consolidate them into a single retained archive, so export what your organization needs to keep into your own logging system.
Common questions
Does Cmdop have one activity feed?
No. Cmdop keeps records where they are made: session history, machine permission audit, relay logs, schedules, and account-console billing records.
Where do I see what an agent did?
Open that machine’s session history in the web console. Agent work is recorded with the session that ran it.
Where do I see permission decisions?
Use cmdop permissions audit on the machine, or the machine audit surfaces in
the web console.
Cmdop