Live fleet topology
See connected machines, running agents, and open threads together. Offline machines remain clearly marked.
CodexTesting the API
Working
Claude CodeUpdating the sync worker
Working
CursorProtected file action
BlockedEvery agent.
In your control.
Know what your AI agents are doing. Set the boundaries. Keep your work moving.
Your agents. One clear view.
Pick an agent to see what it’s working on.
Your connected fleet
3 machines13 agents
A clear start. On your terms.
Connect a machine. Get the owner’s consent. See the work as it happens.
Pair a machine you administer
Install the observer and connect with a one-time pairing code. Only pair machines you administer.
The owner approves the exact scope
The owner approves collection on their machine. Start with metadata; sharing activity content requires a separate opt-in.
Supervise, review, and enforce
See your connected agents, open their activity, and set Guardian rules in plain language.
The context behind every action.
Follow the work, understand the decisions, and keep your team in sync.
Exact conversation history
Follow each session’s prompts, replies, and tool calls from the original records, within the owner’s approved collection scope.
CodexSample threadAdd a retry when the connection drops.
sync/worker.tsUpdatedRetry handling is ready.
24 tests passed.
Guardian policies
Set allowed actions, block risky ones, and require approval through the managed Guardian gateway.
Action Center
Review and approve a request to stop a running agent on an owner-enabled machine. See the recorded outcome.
Evidence-aware analytics
Understand model use, reported tokens, and action outcomes. Incomplete history stays clearly labeled.
Cortex copilot
Ask about fleet health and prepare a guardrail draft. Cortex uses aggregate counts and leaves enforcement to you.
Set the rules.
Let agents work.
Guardian checks actions that pass through its managed gateway. You decide what can run.
Set up GuardianSample scenario
Cursor wants toDelete release files
Blocked
Protected files stay untouched.
Metadata by defaultShared activitySample
Shared activitySample- Agent
- Codex
- Status
- Working
- Secrets
- Kept private
Your data.
Your choice.
Start with metadata. Activity content requires the owner’s permission. Secrets are redacted on the machine.
- Consent before collection
- Owners can revoke access
- Never used to train models
How we handle gaps in the data
Missing information stays missing. Partial records are labeled, and conflicting sources are shown together. Phigon never fills the gaps with invented activity.
Start free. Scale with your fleet.
Machine limits are enforced at pairing time. Local and offline protections are never an upsell — every plan keeps consent, metadata-first defaults, and local redaction.
Free
$0forever
Every feature, free for up to two connected machines.
- 2 connected machines
- All features included
- Guardian, Actions, and Cortex
- Analytics and conversation history
Pro
$2USD / month, plus applicable tax
All the same features, with a higher connected-machine limit.
- 20 connected machines
- All features included
- Guardian, Actions, and Cortex
- Analytics and conversation history
Business
Contact usannual agreement
Custom machine limits, identity, retention, and deployment requirements.
- Custom machine allowance
- Custom roles and approval policy
- SSO and audit exports
- Contracted local or on-premises options
Straight answers
Which agents does Phigon supervise?
Codex, Claude Code, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Cline, Goose, Hermes, OpenHands, Amp, Pi, and OpenClaw are recognized out of the box. Unknown agent processes are still discovered and reviewed by Guardian.
What does the observer collect?
By default only metadata: agent state, activity types, and lifecycle. The Full activity profile adds supported prompts, replies, reasoning summaries, tool calls, and outputs, with mandatory local redaction. Effective collection is always the intersection of workspace policy and the machine owner's choice.
Can Phigon stop an agent?
Yes. Administrators can review a graceful or force stop of an exact running process. Machines separately enrolled for remote commands also support system inspection, commands, and scheduled power changes. Every action has a stored result.
Does it read hidden chain-of-thought?
No. Phigon renders only source-emitted reasoning summaries when the collection policy allows them. Opaque envelopes are labeled as such and never turned into invented thought.
Is this employee monitoring?
Phigon monitors AI systems, not people. Pairing requires an authorized operator and an informed machine owner, and a system is never attributed to a person without separate authoritative identity evidence.
Where does the data live?
The hosted archive is authoritative and tenant-isolated. Machines keep only source cursors and an encrypted delivery spool needed to survive disconnects.
More possibility. Less uncertainty.
Pair one machine you administer, confirm its privacy boundary with the owner, and make your first evidence-aware review today.