Go to file
2026-06-03 10:11:59 +09:00
.yoi rename: adopt yoi identity 2026-06-01 18:49:23 +09:00
crates fix: unify reasoning block persistence 2026-06-03 10:11:59 +09:00
docs fix: harden peer pod registration 2026-06-02 22:23:13 +09:00
resources fix: harden peer pod registration 2026-06-02 22:23:13 +09:00
work-items task: plan reasoning block lifecycle implementation 2026-06-03 09:51:12 +09:00
.envrc Update .envrc 2026-05-30 00:40:12 +09:00
.gitignore docs: reorganize developer documentation 2026-06-01 20:59:32 +09:00
AGENTS.md chore: fix package.nix 2026-06-01 21:37:04 +09:00
Cargo.lock rename: adopt yoi identity 2026-06-01 18:49:23 +09:00
Cargo.toml rename: adopt yoi identity 2026-06-01 18:49:23 +09:00
devshell.nix cli: remove insomnia-pod binary output 2026-05-31 14:59:22 +09:00
flake.lock docs: reorganize developer documentation 2026-06-01 20:59:32 +09:00
flake.nix rename: adopt yoi identity 2026-06-01 18:49:23 +09:00
KNOWN_ISSUES.md chore: audit known issues 2026-05-30 15:06:42 +09:00
LICENSE init 2026-04-04 03:30:01 +09:00
package.nix chore: fix package.nix 2026-06-01 21:37:04 +09:00
README.md Update README.md 2026-06-01 22:24:42 +09:00
tickets.sh chore: audit known issues 2026-05-30 15:06:42 +09:00

夜居 / Yoi agent

Yoi is an agent runtime for building, running, and orchestrating LLM Pods while preserving explicit history, scoped capabilities, and developer-controlled workflows.

Runtime surfaces use yoi, .yoi, ~/.yoi, and YOI_*.

Documentation map

Start with docs/README.md. The repository documentation is intentionally small: it should explain current design intent and development workflow, not preserve every old plan or external research note.

Important entry points:

Development

This repository dogfoods Yoi to develop Yoi. Work is tracked through work-items/ and ./tickets.sh; git history plus work item files are the authoritative record of state changes.

Common local checks:

./tickets.sh doctor
git diff --check
cargo test --workspace

E2E testing with real spawned processes is not yet designed. Avoid adding compatibility layers or broad formatting churn only to reduce short-term edit size; prefer clear boundaries and type safety.