cybeeDE

Swiss. Independent. Privacy first.

Your agents are at work.
See what they do.

See the AI tools on your Macs, the services they connect to and their recorded activity. Ask about them in the assistant you already use.

Start in your Chat, CLI, IDE or TerminalmacOS
curl -sSf https://get.cybee.dev | sh
Explore an exampleConnect your assistant
From an agent
to an observed action.
Claude CodeStudio Mac
MCP · project-files
Tool actionwrite_file
/example/workspace/notes.md
AttemptedCompleted

Illustrative record. This page is not connected to a device.

The tool is only
the starting point.

An assistant can connect to a file service, a repository or another tool. Those connections deserve the same attention as the apps on your Mac.

MCP (Model Context Protocol) is a standard way for an AI assistant to connect to tools. cybee maps the agent, server name, connection method and endpoint so you can see what is configured.

Look inside
the record.

Expand a view. All records below are illustrative. Nothing runs when you open them.

Studio MacIllustrative output
AI agents

Identify the agents found on a device. An installed tool is not necessarily running.

AgentObserved on
Claude CodeStudio Mac
Claude DesktopStudio Mac
CursorStudio Mac
CodexStudio Mac
MCP connections

See which agent has each connection configured. stdio connects through a local process; HTTP uses an endpoint address.

Agent / serverConnectionEndpoint
Claude Code
project-files		stdio/example/tools/project-files
Cursor
project-docs		HTTPhttps://docs.example.com/mcp

Scroll sideways to see endpoints →

Recorded activity

Read each action with its tool and recorded time. An attempt and a completed call are different events.

  1. AttemptedClaude Code · write_file/example/workspace/notes.md
  2. CompletedClaude Code · write_file/example/workspace/notes.md

Completed describes the recorded phase of a tool call. It does not prove the intended task succeeded or that the action was safe.

A configured connection is not proof that it was used. A record of activity is not a complete history of everything an agent did.

Read the activity
with the Mac around it.

An unfamiliar tool call is easier to investigate when you can also see the software and settings on the device.

Understand device protection
Software versions
Installed apps and versions, including outdated software.
Browser extensions
Installed extensions and the permissions they request.
Startup items
Software configured to start automatically on the Mac.

Visibility helps you
ask better questions.

Use the observations to investigate. Keep a finding separate from a decision to change access.

Does cybee restrict what each AI agent can do?
Agent discovery, connection mapping and activity records provide visibility. They do not enforce per agent permissions. Separate access limits are planned. See the roadmap.
Does “completed” mean an action was safe?
No. It describes the recorded phase of an action. Read the tool, target and surrounding events before drawing a conclusion.
How does this relate to hardening and proof?
Hardening improves device settings. Agent records add context about AI tools and their activity. The Trust Passport has its own defined scope; it does not certify that every agent action is safe.

Ask about
your own Mac.

Once your assistant is connected, start with a specific device.

Read the assistant guide

Which AI agents and MCP connections are on this Mac? Show their recorded activity and when it was observed.