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…
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 31,542 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 repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- benchmark/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- package-gale/AGENTS.mdAGENTS.md
- package-grog/AGENTS.mdAGENTS.md
- package-jade/AGENTS.mdAGENTS.md
- package-loam/AGENTS.mdAGENTS.md
- package-re/AGENTS.mdAGENTS.md
- package-wadopoet/AGENTS.mdAGENTS.md
- wado-cli/AGENTS.mdAGENTS.md
- wado-compiler/AGENTS.mdAGENTS.md
- wado-from-idl/AGENTS.mdAGENTS.md
- wado-host/AGENTS.mdAGENTS.md
- wado-lsp/AGENTS.mdAGENTS.md
- wado-manifest/AGENTS.mdAGENTS.md
- wado-run-webgpu/AGENTS.mdAGENTS.md
- wado-vscode/AGENTS.mdAGENTS.md
- benchmarkSkill
- ci-timingSkill
- code-review-responseSkill
- coverage-investigationSkill
- crSkill
- debuggerSkill
- distillSkill
- git-upstream-syncSkill
- jcoSkill
- markdownSkill
- on-task-doneSkill
- optimizer-debugSkill
- profiling-wado-compilerSkill
- pull-requestSkill
- rust-renameSkill
- rustSkill
- vendor-submodulesSkill
- wado-cliSkill
- wado-performanceSkill
- wasm-optSkill
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
- Very specific: line 23
Every plugin call goes through Plugin::enter, on the plugin's thread, never on the fiber a guest runs on.
≈ “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.
Files
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
--pluginorWADO_PJRT_PLUGIN, so no build depends on one.mise run test-pjrtfetches the pinned CPU plugin andlibtpu.so(scripts/fetch-pjrt-plugin.sh) and runs the#[ignore]d tests on them. xla/pjrt/c/pjrt_c_api.his the one part of XLA that may be read.src/ffi.rsfollows 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,guestandoptionshold 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
SIGSEGVandSIGABRT, 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.mdlists 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.
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
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.

