darktable
darktable-org/darktable/AGENTS.md
when GTK3 has the Wayland backend gui/gtk.c calls into libwayland-client directly to detect server-side decoration support, but gtk+-3.0.pc does not list wayland-client. The symbols were
How real projects brief Codex, Cursor and every other agent that reads AGENTS.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
darktable-org/darktable/AGENTS.md
when GTK3 has the Wayland backend gui/gtk.c calls into libwayland-client directly to detect server-side decoration support, but gtk+-3.0.pc does not list wayland-client. The symbols were
debezium/debezium/AGENTS.md
analyze the codebase, DO NOT set up build environments, DO NOT run scripts, or MCP, or skills, DO NOT look things up online, DO NOT make code changes, UNTIL
Steady2 mentions in 2 weeks
No other project uses it yet
openreplay/openreplay/mcp_app/AGENTS.md
OpenReplay MCP App — Agent Guide Reference: https://modelcontextprotocol.github.io/ext-apps/api/documents/Patterns.html --- ## Project Structure ``` server.ts MCP server entry point (stdio transport) lib/ tools.ts All tool registrations (UI + internal) api.ts OpenReplay REST API client
vercel-labs/portless/AGENTS.md
change to a CLI command, flag, output, or environment variable must update the MCP tools in `packages/portless/src/mcp.ts` in the same change. `mcp.test.ts` reads `portless --help` and each tool command
Steady20 mentions in 2 weeks
No other project uses it yet
nearai/ironclaw/tests/AGENTS.md
before durable storage without retaining inline media/blob base64 | `mcp.rs` | | User-registered and bundled hosted MCP servers register, authenticate, project active, restore, and invoke | `hosted_mcp_registration.rs` | | Web search/fetch runs the real
Chainlit/chainlit/AGENTS.md
over keeping legacy code in place. ## MCP-First Approach (CRITICAL) When available, **ALWAYS** prefer MCP servers over manual alternatives. Use **Context7** for docs/API references, **Serena** for code navigation/refactoring/memory, and **GitHub
tw93/Kami/AGENTS.md
WeasyPrint-safe. Pure Python, no Node, ships in the package. - `scripts/mcp_server.py` - zero-dependency MCP stdio server exposing `kami_templates` / `kami_doctor` / `kami_render` / `kami_check` / `kami_deliver` / `kami_screenshot
No other project uses it yet
viarotel-org/escrcpy/AGENTS.md
string | string[]` contract; business code stays untouched across internal changes. - [packages/madb/](../packages/madb/) is an MCP server for AI agent Android device control via ADB and yadb (32 tools
aureuserp/aureuserp/AGENTS.md
important rather than explaining obvious details. === boost rules === # Laravel Boost - Laravel Boost is an MCP server that comes with powerful tools designed specifically for this application. Use them. ## Artisan
cocoindex-io/cocoindex/AGENTS.md
status` to confirm the root is this repo. We register no MCP server on purpose — an `ccc mcp` mode exists, but the CLI costs no context until invoked and behaves
Steady3 mentions in 2 weeks
No other project uses it yet
TencentCloud/Octop/AGENTS.md
agents/`, `api/routers/workspace*.py` | | `infra/connectors/` | Connector catalog, OAuth, MCP gateway, credential crypto | `api/routers/connectors.py`, `internal_mcp.py`, `agents/manager.py` (MCP assembly) | | `infra/control/` | Host control surfaces: `browser/`, `desktop/`, `mobile/` | `api/routers/browser/`, `desktop/`, `mobile/` | | `infra/cron/` | Cron jobs, triggers
rerun-io/rerun/AGENTS.md
output once the notification arrives. ### Driving a running egui UI (for agents) Two MCP servers let an agent see and click a running UI instead of guessing from code: - `rerun
cloudflare/cloudflare-os/packages/mcp-shared/AGENTS.md
portal` (one admin-configured portal). Not a Worker; a library both import, holding the MCP client, the OAuth chain, the account DO base, the resource-URL scope grammar
MoonshotAI/kimi-cli/AGENTS.md
software engineering workflows. It supports an interactive shell UI, ACP server mode for IDE integrations, and MCP tool loading. ## Tech stack - Python 3.12+ (tooling configured for 3.14) - CLI framework: Typer
MoonshotAI/kimi-cli/tests_e2e/AGENTS.md
runs the flow until `END`. - W-36 MCP: use a Python fastmcp test server, load via `--mcp-config-file`, verify tool works. **Resilience and Errors** - W-37 Invalid JSON: malformed
apereo/cas/AGENTS.md
local branch | | [`cas-interrupt-notifications`](.claude/skills/cas-interrupt-notifications/SKILL.md) | `support/cas-server-support-interrupt*` | | [`cas-ldap`](.claude/skills/cas-ldap/SKILL.md) | LDAP modules | | [`cas-mcp-server`](.claude/skills/cas-mcp-server/SKILL.md) | `support/cas-server-support-mcp` | | [`cas-oauth-oidc-authentication`](.claude/skills/cas-oauth-oidc-authentication/SKILL.md) | OAuth/OIDC/UMA client authentication, access-token-protected endpoints, `OAuth20UserProfile
tambo-ai/tambo/docs/AGENTS.md
authentication/** (8 pages including index) - Auth.js, Auth0, Clerk, Supabase, Neon, WorkOS, Better Auth - connect-mcp-servers - Single page (not in subfolder) - **self-hosting/** (9 pages including index) - quickstart, environment-variables
No other project uses it yet
tambo-ai/tambo/react-sdk/AGENTS.md
return rich content including images, audio, or mixed media. This is particularly useful for MCP tools that already return content in the proper format. ### Key Hook System - **`useTambo()`** - Primary hook
No other project uses it yet
langchain-ai/open-swe/AGENTS.md
composing generic capabilities such as plugins, automations, skills, or external MCP servers. First check whether existing capabilities, with small generic additions if needed, can deliver the feature. - Before changing
Steady12 mentions in 2 weeks
No other project uses it yet
microsoft/fluentui-system-icons/AGENTS.md
affected`) instead of using the underlying tooling directly - You have access to the Nx MCP server and its tools, use them to help the user - When answering questions about
Steady13 mentions in 2 weeks
1 project uses a version of this
An open format for instructions to coding agents, read by Codex, Cursor and others. Think of it as a README written for agents.
At the repository root, with more specific files in subdirectories. Agents read the one closest to the file they're editing.
Setup and test commands, code style, and the rules a new contributor would need to know.
Claude Code reads CLAUDE.md. A one-line CLAUDE.md that points at AGENTS.md covers both.