What is Agent Honeypot?
Agent Honeypot installs a text checkpoint and guestbook on a computer so AI agents that encounter the files can be asked to stop exploring and report their visit. It is for people who want to make that request visible in common discovery locations, while exempting their own agents from the message. Installers support macOS, Linux, and Windows, and the project is available under the MIT licence. The flag is a prompt-level checkpoint, not a security boundary.
Agent Honeypot Features:
Checkpoint File: The installer creates a canonical flag.txt in the home directory with instructions for a visiting agent to stop discovery, avoid secrets, remediate only what it can identify confidently, and report back.
Own-Agent Exemptions: The flag names agents such as opencode, Claude Code, Codex, Cursor, and Grok as exempt from interruption and tells them not to sign the guestbook.
Append-Only Guestbook: A world-writable guest-book.txt lets a visitor add one line with a UTC timestamp, its claimed identity, and how it arrived.
Common Discovery Paths: The installer places links to the canonical flag in commonly checked locations, including temporary directories, system paths, and root locations, with Windows-specific targets too.
Cross-Platform Installers: Shell installers cover macOS and Linux, while a PowerShell installer handles Windows, with elevation needed for some protected paths and symlinks.
Customise and Remove: The flag can be edited before or after installation, and uninstall scripts remove links while keeping the flag and guestbook unless purge is requested.
Agent Honeypot Benefits:
Visitor Context: Guestbook entries can give an administrator a quick record of who or what claims to have visited and the route it says it took.
Fewer False Alarms: Exempting named in-use agents helps keep the checkpoint message from interrupting the owner's usual agent setup.
One-File Updates: Keeping links pointed at one canonical flag means edits can update the message across linked locations without changing each link separately.
Flexible Deployment: Platform-specific installers and options let users choose a setup suited to a workstation, Windows machine, or container environment.
Clear Limits: The explicit checkpoint-not-boundary distinction helps users avoid treating a text prompt or self-reported guestbook entry as proof of protection or identity.
Use Cases:
Local Agent Testing: Install the checkpoint on a development machine to see whether an agent exploring the filesystem encounters the message and follows its request to stop.
Shared Workstations: Use the guestbook on a machine accessed by multiple local users or sandboxed agents to collect their claimed visit details in one file.
Container Setups: Add the home-directory checkpoint in a container or CI environment where system-root placement is unnecessary.
Windows Deployment: Run the PowerShell installer on Windows to place the flag in likely discovery locations, using elevation where protected paths or symlinks are needed.
Agent Discovery Research: Place flags in common recon locations to examine whether visiting agents check home, system, or temporary directories without assuming the flag will attract them.

