Go to file
2026-06-21 02:00:29 +09:00
.yoi ticket: complete resume cli command 2026-06-21 02:00:29 +09:00
crates fix: update resume guidance 2026-06-21 01:53:32 +09:00
docs plugin: add instance lifecycle surface 2026-06-20 23:15:47 +09:00
resources plugin: fix instance lifecycle blockers 2026-06-20 23:42:44 +09:00
tests/e2e test: measure panel shell startup path 2026-06-19 13:04:45 +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 docs: relax nix build validation policy 2026-06-12 21:59:11 +09:00
Cargo.lock chore: remove daemon crate 2026-06-20 22:41:24 +09:00
Cargo.toml chore: remove daemon crate 2026-06-20 22:41:24 +09:00
devshell.nix fix: restore orchestrator companion notifications 2026-06-18 23:42:07 +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 project: record queued tickets and issue notes 2026-06-08 22:14:49 +09:00
LICENSE init 2026-04-04 03:30:01 +09:00
package.nix chore: remove daemon crate 2026-06-20 22:41:24 +09:00
README.md tui: introduce dashboard console boundaries 2026-06-20 18:12:18 +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.

1. Yoi agent

Yoi focuses on long-running agent operation rather than one-off prompt execution. A named Pod can keep durable session history, run with explicit tool and filesystem authority, delegate bounded work to child Pods, and be inspected or restored through CLI/TUI surfaces.

Main highlights:

  • Named long-running Pods with durable session and metadata records.
  • Explicit tool permissions and filesystem scopes.
  • Multi-agent orchestration with scoped coder/reviewer Pods.
  • Profile, Manifest, and prompt-based runtime configuration.
  • Local Tickets and workflow files for auditable project coordination.
  • TUI and CLI entry points, including the yoi panel workspace Dashboard and single-Pod Console.

Yoi is actively dogfooded in this repository. Public APIs, configuration formats, and workflows may still change.

2. Quick Install

From source:

cargo build --release -p yoi
./target/release/yoi --help

With Nix:

nix build .#yoi
./result/bin/yoi --help

3. Getting Started

yoi --help
yoi
yoi panel
yoi --pod <name>
yoi pod --help

Typical flow:

  1. Configure providers, models, profiles, prompts, and scopes.
  2. Start or attach to a named Pod in the Console, or inspect workspace activity in the Dashboard.
  3. Use explicit tools and scoped delegation for multi-agent work.
  4. Record project work through Tickets, workflow files, and git history.

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

4. Documentation

Start with docs/README.md.

Key docs:

5. Development

This repository dogfoods Yoi to develop Yoi. Work is tracked through .yoi/tickets/ and yoi ticket ...; git history plus Ticket files are the authoritative project record.

Common checks:

yoi ticket doctor
git diff --check
cargo fmt --check
cargo check --workspace --all-targets
cargo test --workspace

Optional Nix validation:

nix build .#yoi --no-link

E2E testing with real spawned processes is not yet designed. Keep changes scoped, preserve durable authority boundaries, and prefer clear type-safe structure over short-term compatibility layers.

License: MIT. See LICENSE.