agentleFS
SupabaseKnown publishersupabase/supabase-py/AGENTS.md

supabase-py

AGENTS.md2.6k starsChanged 12 days agoMITView on GitHub

Setup and commands: README.md § Local Development; make help and make <pkg>.help list every target. PR process: CONTRIBUTING.md. <pkg> is the directory under src/. Three import names differ from it: auth → supabaseauth, storage → storage3, functions → supabasefunctions. Adding or renaming a public symbol means updating sdk-compliance.yaml with both the Async* and Sync* names. validate-capabilities.yml checks it against the supabase/sdk capability registry.

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

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Commit and PR title: type(<pkg>): lowercase subject, e.g.

    line 27

≈ “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

AGENTS.md

Setup and commands: README.md § Local Development; make help and make <pkg>.help list every target. PR process: CONTRIBUTING.md.

Packages

<pkg> is the directory under src/. Three import names differ from it: auth → supabase_auth, storage → storage3, functions → supabase_functions.

Async is the source, sync is generated

  • Edit _async/ (source and tests/_async/). Regenerate _sync/ with make <pkg>.build-sync, then make ruff, and commit both trees.
  • build-sync needs GNU sed (gsed is used when present; nix develop provides it). A _sync/ diff your _async/ change does not explain is a generator bug: fix the build-sync recipe, not the generated file.
  • realtime has no build-sync: its _sync/ is a stub and the package is async-only.

Checks

  • make <pkg>.tests runs mypy and pytest. For auth, postgrest, storage and realtime, pytest first starts Docker / Supabase CLI infra; make stop-infra when done.
  • Fast loop for tests that need no infra: from src/<pkg>, uv run --frozen --package <import name> pytest tests/<file>.py.
  • Code must run on Python 3.9 — CI tests 3.9–3.14 (ci.yml).

Public API

Adding or renaming a public symbol means updating sdk-compliance.yaml with both the Async* and Sync* names. validate-capabilities.yml checks it against the supabase/sdk capability registry.

Commits and releases

  • Commit and PR title: type(<pkg>): lowercase subject, e.g. fix(realtime): cap reconnect backoff.
  • release-please owns every version.py, pyproject.toml version and CHANGELOG.md; leave them to it (release-please-config.json).
  • uv run without --frozen (as the Makefiles call it) can rewrite uv.lock; leave it out of the diff unless you changed dependencies.

Download now (ZIP)

Trending

Less talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 3 mentionsFeb 2026: 3 mentionsMar 2026: 1 mentionApr 2026: 1 mentionMay 2026: 1 mentionJun 2026: 6 mentionsJul 2026: 2 mentionsAug 2026: 2 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the supabase/supabase-py repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about supabase/supabase-py

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

See all 48

Talked about on GitHub and Bluesky (48 times).

On GitHub · 47

42 more on GitHub

On Bluesky · 1

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

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.