Web Cabinet

The CMDOP web cabinet at cmdop.com  is where you administer your fleet, pay the bills, and review what your agents have been doing. It is not where you do hands-on operations work.

What the web cabinet is for now

The cabinet covers four jobs that genuinely belong in a browser:

• Fleet administration — invite and remove members, assign roles, audit shared activity, edit fleet policies.
• Billing — manage payment methods, change plans, add seats, monitor usage and quotas, download invoices.
• Read-only observability — see machine inventory, browse session transcripts, review schedule run history, search the audit log.
• Personal account — profile, 2FA enrollment, API tokens, OAuth sign-in providers, support tickets.

Everything else — driving a terminal, asking the agent for help, transferring files — runs faster and more reliably from the desktop app or the CLI.

What moved out of the cabinet

A few features still appear in the cabinet UI but are now positioned as a fallback rather than the canonical surface:

• Web terminal is read-only by default. Use ../desktop/machines-tab or ../cli/connect to actually run commands.
• AI chat in the cabinet is a thin web fallback — the primary chat surface is the desktop Chat tab and cmdop chat.
• File manager stays for casual browsing; for real file work use the desktop Projects tab and the agent file tools.
• Schedule authoring is moving out — author schedules as skills or via ../cli/trigger. The cabinet lists existing schedules and their runs.

See Operational features for the long version.

Sections at a glance

Who should use the cabinet

• Fleet owners managing membership, roles, and policies.
• Billing admins picking plans, adding seats, watching quotas.
• On-call observers checking what agents have been doing.
• Security and compliance reviewers searching the audit log and exporting evidence.

Who should not operate from here

If you are running an incident, authoring a skill, or relying on a stable shell, the cabinet is the wrong surface. Open the desktop app or the CLI:

• Engineers running incidents → ../desktop/machines-tab or ../cli/connect.
• Skill authors → ../skills/getting-started and the desktop Chat tab.
• Anyone needing reliable, low-latency shells → ../cli/connect over the cabinet’s web terminal.

Where the data comes from

The cabinet shows the same data that backs the desktop and CLI surfaces — there is one source of truth across all three:

• Fleets, machines, and sessions — fleet, machine, and session state.
• Schedules, account, audit, and chat history — automations, profile, activity, and chat.
• Skills — the marketplace catalog the cabinet browses (install and run live in desktop/CLI).

Live updates stream in real time, so machine and session state in the cabinet stays current without a refresh.

Related

• Desktop app — your primary work surface.
• CLI reference — the same operations, scriptable.
• Concepts: fleets — what a fleet is and how scoping works.
• Operational features — what stays in the cabinet UI but is now secondary.