Agentlink reference

AI coding tools and instruction-file paths

The homepage collects the complete, current support listing. The registry distinguishes tools that read AGENTS.md natively from integrations better handled through configuration, imports, or explicit symlinks.

By Sam RogersPublished September 1, 2026Updated September 5, 2026

Integration modes

Native: the tool reads AGENTS.md at the stated scope.
Configurable: configure the tool to read the shared source rather than creating another alias.
Import: keep a real tool file and import the shared source.
Symlink: use a filesystem alias when the tool expects a distinct filename.
Unsupported: Agentlink detects the tool but does not claim a safe AGENTS.md integration.

Preference, not automation: agentlink detect --generate --prefer-native reports the least invasive known option. Agentlink itself creates symlinks only; it does not rewrite another tool’s settings or import files.

Complete support listing

The homepage support listing is the single complete reference for operating systems and AI tools. It includes project and global instruction paths, preferred integration modes, vendor documentation, and review dates. The listing follows the v0.6.0 registry; older binaries may contain different detection and integration metadata.

Paths describe instruction files only. Do not point a Markdown source at a tool’s YAML or JSON settings file. Environment overrides, client differences, and precedence can change which file a tool reads. Check the vendor reference for your installed client, then confirm that it actually loaded the intended instructions.

Nested discovery is a separate capability

A tool reading a root instruction file does not prove it discovers the same filename in nested directories. Agentlink enables nested scan aliases only when the registry includes a public behavior reference. In v0.6.0, Claude Code and Gemini CLI have documented nested discovery metadata. Other and unknown integrations remain root-only during scan --nested.

Keep the reference honest

The Go registry in internal/registry/tools.go is the source for detection paths and integration metadata. A generation check keeps the homepage listing aligned with it. Tool behavior can change independently, so confirm the current vendor documentation before relying on a non-native integration in a sensitive workflow.