AGENTS.md · agentjido/jido
AGENTS.md from agentjido/jido: 47 lines covering Intent, Runtime Baseline, Commands, Architecture Snapshot and more.
Template by agentjido
Install
Works with Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Claude Code. Read the repository before you give any tool access to your data.
curl -fsSL https://raw.githubusercontent.com/agentjido/jido/main/AGENTS.md -o AGENTS.md
Read it and adapt it to your project before use.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: code-generation, testing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
What's in it
An AGENTS.md file: instructions coding agents (Codex, Cursor, Copilot, Gemini CLI and others) read before working in a repo.
- For
- Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Claude Code
- Length
- 47 lines
- File
AGENTS.md
Sections
- Intent
- Runtime Baseline
- Commands
- Architecture Snapshot
- Standards
- Testing and QA
- Release Hygiene
- References
First lines (shown under the repo's Apache-2.0 license)
# AGENTS.md - Jido Guide
## Intent
Build reliable agent systems by separating pure decision logic from runtime side-effect execution.
## Runtime Baseline
- Elixir `~> 1.18`
- OTP `27+` (release QA baseline)
## Commands
- `mix test` (default alias excludes `:flaky`)
- `mix test --include flaky` (full suite)
- `mix test --cover` (coverage gate)
- `mix q` or `mix quality` (`format --check-formatted`, `compile --warnings-as-errors`, `credo`, `dialyzer`)
- `mix docs` (local docs)
## Architecture Snapshot
- `Jido.Agent`: pure agent module with immutable state and `cmd/2`
- `Jido.AgentServer`: GenServer runtime for directives, lifecycle, and message flow
- `Jido.Agent.Directive.*`: typed effect descriptors (`Emit`, `SpawnAgent`, `StopChild`, etc.)
- `Jido.Agent.StateOp.*`: internal state transition operations applied by strategy layer
- Plugins/sensors provide capability composition without coupling core agent logic
## Standards
- Keep `cmd/2` pure: same input => same `{agent, directives}` output
- Keep directives for external effects only; do not rely on directives for state mutation
- Use **Zoi-first** schemas for new agent/plugin/signal contracts
- Preserve tagged tuple and structured error contracts at public boundaries
- Keep cross-agent communication on signals/directives, not ad-hoc process messages
## Testing and QA
- Prefer pure agent tests first, then AgentServer/runtime integration tests
- Use helpers from `test/AGENTS.md` (`JidoTest.Case`, `JidoTest.Eventually`) for async assertions
- Avoid `Process.sleep/1` in tests; assert eventual state/event behavior
## Release Hygiene
- Keep semver ranges stable (`~> 2.0` for Jido ecosystem peers)
- Use Conventional Commits
- Do not modify `CHANGELOG.md`; release notes are generated from Git history during release, so keep changes focused on proper Conventional Commits.
## References
- `README.md`
- `usage-rules.md`
- `guides/`
- `test/AGENTS.md`
- https://hexdocs.pm/jidoSignals
- Stars
- 1,896
- Forks
- 122
- Open issues
- 1
- Last commit (this folder)
- Sep 1, 2026 (1 month ago)
- Last release
- Oct 8, 2026 (20 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Repository
- github.com/agentjido/jido
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Cite this page
AGENTS.md · agentjido/jido. Agent Mart. https://agentmart.dev/templates/agentjido-jido-agents-md (last updated 2026-10-24)