agentleFS
wado-langwado-lang/wado/wado-run-pjrt/AGENTS.md

wado / wado-run-pjrt

AGENTS.md120 starsChanged 14 days agoMITView on GitHub

The wado run-pjrt subcommand: it compiles a Wado program with wado and runs the component on a wasmtime host that serves core:pjrt from a PJRT plugin. - A plugin is loaded at run time, from --plugin or WADO_PJRT_PLUGIN, so no build depends on one. mise run test-pjrt fetches the pinned CPU plugin and libtpu.so (scripts/fetch-pjrt-plugin.sh) and runs the #[ignore]d tests on them. - xla/pjrt/c/pjrt_c_api.h is the one part of XLA that may be read. src/ffi.rs follows it. An argument struct…

The file

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:

    Every plugin call goes through Plugin::enter, on the plugin's thread, never on the fiber a guest runs on.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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

wado-run-pjrt

The wado run-pjrt subcommand: it compiles a Wado program with wado and runs the component on a wasmtime host that serves core:pjrt from a PJRT plugin.

Rules

  • A plugin is loaded at run time, from --plugin or WADO_PJRT_PLUGIN, so no build depends on one. mise run test-pjrt fetches the pinned CPU plugin and libtpu.so (scripts/fetch-pjrt-plugin.sh) and runs the #[ignore]d tests on them.
  • xla/pjrt/c/pjrt_c_api.h is the one part of XLA that may be read. src/ffi.rs follows it. An argument struct must be at least the plugin's size, so each struct is declared in full, whatever a call uses of it.
  • A program behaves the same here as under wado run, which is the only reason to have both. wado_host::runner, guest and options hold what makes that so, and a divergence is a defect, not a variant.
  • A plugin's fault ends the process, so crashes.md records each SIGSEGV and SIGABRT, fixed or not, with the top of its backtrace.
  • A plugin reads as far as a guest's values say, so the host checks what reaches it through a pointer before the call. crashes.md lists what a plugin refuses on its own.
  • Every plugin call goes through Plugin::enter, on the plugin's thread, never on the fiber a guest runs on.

Download now (ZIP)

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.