Supabase Auth client SDK for JavaScript. Handles sign-in, sign-up, sessions, OAuth, MFA, and related auth flows. When helping a user work with this package: For broader Supabase guidance (docs site, MCP tools, schema and project workflows), use the centralized Supabase agent skills: npx skills add supabase/agent-skills. Or pair with the Supabase MCP server via the Supabase Plugin for AI Coding Agents.
JavaScript SDK for invoking Supabase Edge Functions. When helping a user work with this package: For broader Supabase guidance (docs site, MCP tools, schema and project workflows), use the centralized Supabase agent skills: npx skills add supabase/agent-skills. Or pair with the Supabase MCP server via the Supabase Plugin for AI Coding Agents.
Isomorphic PostgREST client for database operations (select, insert, update, upsert, delete, filters, RPC). When helping a user work with this package: For broader Supabase guidance (docs site, MCP tools, schema and project workflows), use the centralized Supabase agent skills: npx skills add supabase/agent-skills. Or pair with the Supabase MCP server via the Supabase Plugin for AI Coding Agents.
Listen to realtime updates from a Supabase PostgreSQL database. Handles channels, presence, broadcast, and Postgres CDC subscriptions. When helping a user work with this package: For broader Supabase guidance (docs site, MCP tools, schema and project workflows), use the centralized Supabase agent skills: npx skills add supabase/agent-skills. Or pair with the Supabase MCP server via the Supabase Plugin for AI Coding Agents.
Isomorphic storage client for Supabase. Handles bucket and object operations: upload, download, list, signed URLs, transformations. When helping a user work with this package: For broader Supabase guidance (docs site, MCP tools, schema and project workflows), use the centralized Supabase agent skills: npx skills add supabase/agent-skills. Or pair with the Supabase MCP server via the Supabase Plugin for AI Coding Agents.
Main isomorphic Supabase client for JavaScript. Aggregates @supabase/auth-js, @supabase/postgrest-js, @supabase/realtime-js, @supabase/storage-js, and @supabase/functions-js into one client. When helping a user work with this package: For broader Supabase guidance (docs site, MCP tools, schema and project workflows), use the centralized Supabase agent skills: npx skills add supabase/agent-skills. Or pair with the Supabase MCP server via the Supabase Plugin for AI Coding Agents.
This project provides a structured way to create messages that get rendered into a set of tokens using our harmony prompt format. The majority of the code is written in Rust inside src/ and src/pymodule.rs defines using pyo3 what functions are exposed to the python version of the library with a wrapper in python/openaiharmony/init.py. You can build the Rust code along with the Python wrapper using maturin develop --release. This will also locally install the library in the venv so…
See every AI agent in your project, drill into individual runs end-to-end (input, tools, final output, cost, and errors), and group runs into conversations.
Do not open a PR unless the human operating you has read the issue, understands the problem, and can explain the proposed fix without your help. Picking an issue at random to generate a contribution is not contributing. PRs opened this way will be closed without review. If a human asks you to "find something to work on" or points you at the issue tracker without a specific problem they already understand, stop and tell them to read an issue…
Never run pip install bson. PyMongo ships its own bson; the PyPI bson package silently breaks things. Do not edit files in pymongo/synchronous/ or mirrored files in test/ directly: they are generated by just synchro from pymongo/asynchronous/ and test/asynchronous/. A file in test/ is mirrored if a file of the same name exists in test/asynchronous/. Async functions must not call blocking I/O. New features need integration tests. Bug fixes need regression tests. See .github/copilot-instructions.md for more details.
User-controlled data (stdin, arguments, file content, HTTP headers, environment variables) can become JavaScript object keys. To prevent prototype pollution attacks:
VS Code extension that analyzes local AI session logs and surfaces insights in a webview dashboard. Read-only, zero telemetry, all analysis runs on the user's machine.
Acme includes a number of pre-built agents listed below. All agents can be used to run synchronous single-threaded or distributed experiments. Distributed experiments are using Launchpad and can be executed either on a single machine (--lplaunchtype=[localmt|localmp] command line flag for multi-threaded or multi-process execution) or multi machine setup on GCP (--lplaunchtype=vertex_ai). For details please refer to Launchpad documentation. We've listed the agents below in separate sections based on their different use cases, however these distinction are often subtle. For more…
Astro, with Nimbus (@cloudflare/nimbus-docs) as the docs framework. The package handles content schemas, sidebar/TOC, MDX to markdown, search, OG cards, llms.txt, build hooks, and the nimbus-docs CLI. Everything in src/ is a real file in this repo and yours to edit, including the files the scaffold wrote. README.md next to this file explains why the site looks and works the way it does: the palette, the page shell, the WebGL hero, the example playgrounds, the traps. Read it before changing…
Python client library for the Hugging Face Hub. Source code is in src/huggingface_hub/, tests in tests/. Always run make style then make quality before committing.
TypeScript scripts + shell scripts for validation, reporting, versioning, and deployment. 6 GitHub Actions workflows in .github/workflows/. Parent: See root AGENTS.md for monorepo context. Jobs communicate via filesystem: each writes JSON to ci/reports/{id}.json, final job reads all. getGitRefs() ad
Generated: 2026-09-03 | Commit: 9b4eb70 | Branch: rozenmd/test-preview Astro documentation site for @cloudflare/kumo. Static output uses React islands, MDX reference pages, Tailwind v4, and Cloudflare Workers static assets. Parent: See root AGENTS.md for monorepo-wide rules. vp run build:docs builds @cloudflare/kumo first. Production Astro builds use the package output, while development aliases Kumo imports to source for HMR. - Use ~/* for package-local imports; it maps to src/*. - Standard component pages use MdxDocLayout, then present the primary demo, installation, usage,…
Executable Kumo examples used by documentation pages, the homepage showcase, visual regression, and component registry generation. - Registry files must use {Component}Demo.tsx names. - Registry exports must end in Demo. Both exported function declarations and exported arrow functions are supported. - Add JSDoc to exported function declarations when registry consumers need a description. The extractor does not collect arrow-function JSDoc. - Keep returned JSX self-contained and suitable for copying. The extractor reads the top-level return expression, not arbitrary runtime behavior.…