agentleFS
PydanticKnown publisherpydantic/pydantic-ai/tests/harness/AGENTS.md

pydantic-ai / harness

AGENTS.md21k starsChanged 17 days agoMITView on GitHub

Rules for the pydantic-ai-harness test suite. They add to tests/AGENTS.md and to the package rules in src/pydanticaiharness/AGENTS.md. Where these rules or the harness guides they link differ from tests/AGENTS.md, they apply under tests/harness/. Read testing-capabilities.md before you add or change a capability's tests. For async behavior, follow the harness concurrency.md. - tests/harness/conftest.py sets ALLOWMODELREQUESTS = False for the suite. - Name a capability test class TestCapabilityName, with test<scenario> methods. - Don't import private (-prefixed) helpers into tests. Exercise them through…

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read testing-capabilities.md before you add or change a capability's tests.

    line 7
  2. Very specific:

    Don't import private (_-prefixed) helpers into tests.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

tests/harness/ guidelines

Rules for the pydantic-ai-harness test suite. They add to tests/AGENTS.md and to the package rules in src/pydantic_ai_harness/AGENTS.md. Where these rules or the harness guides they link differ from tests/AGENTS.md, they apply under tests/harness/.

Read testing-capabilities.md before you add or change a capability's tests. For async behavior, follow the harness concurrency.md.

  • tests/harness/conftest.py sets ALLOW_MODEL_REQUESTS = False for the suite.
  • Name a capability test class TestCapabilityName, with test_<scenario> methods.
  • Don't import private (_-prefixed) helpers into tests. Exercise them through the capability's public surface so tests survive internal refactors: drive the behavior through Agent(..., capabilities=[...]), or import the public class re-exported from the capability package's __init__.py (e.g. from pydantic_ai_harness.filesystem import FileSystemToolset, not from pydantic_ai_harness.filesystem._toolset import _content_hash). When a branch is only reachable by calling a private helper directly, mark it # pragma: no cover rather than reaching into the helper from a test.

Download now (ZIP)

Trending

Quiet since August.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 2 mentionsMar 2026: 2 mentionsApr 2026: 29 mentionsMay 2026: 2 mentionsJun 2026: 2 mentionsJul 2026: 3 mentionsAug 2026: 1 mentionSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the pydantic/pydantic-ai repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about pydantic/pydantic-ai

The biggest 5 of 63 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 63

Talked about on GitHub, Bluesky, Hacker News and the web (63 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

On Hacker News · 5

On the web · 1

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

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.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.