Go to file
2026-07-22 19:09:17 +09:00
.yoi chore: untrack yoi tickets 2026-07-22 17:09:14 +09:00
crates fix: share protocol frame codec 2026-07-22 14:03:33 +09:00
docker/workspace/.yoi feat: add local image compose setup 2026-07-22 19:09:17 +09:00
docs fix: remove stale report knowledge wording 2026-07-16 07:54:35 +09:00
resources ticket: use boolean ticket capabilities 2026-07-21 06:13:26 +09:00
scripts dev: harden workspace restart scheduling 2026-07-20 11:35:22 +09:00
tests/e2e fix: align e2e worker metadata root 2026-06-29 05:01:56 +09:00
web/workspace fix: remove console composer click shell 2026-07-22 16:55:28 +09:00
.envrc Update .envrc 2026-05-30 00:40:12 +09:00
.gitignore dev: enable default ticket tools and workdir helpers 2026-07-18 17:32:46 +09:00
AGENTS.md Update AGENTS.md 2026-07-21 15:34:17 +09:00
Cargo.lock feat: surface backend runtime workers in tui 2026-07-21 17:41:50 +09:00
Cargo.toml refactor: remove workflow machinery 2026-07-16 05:45:24 +09:00
compose.yaml feat: add local image compose setup 2026-07-22 19:09:17 +09:00
devshell.nix feat: surface backend runtime workers in tui 2026-07-21 17:41:50 +09:00
docker.nix feat: add local image compose setup 2026-07-22 19:09:17 +09:00
flake.lock docs: reorganize developer documentation 2026-06-01 20:59:32 +09:00
flake.nix feat: build docker images with nix 2026-07-22 18:43:35 +09:00
KNOWN_ISSUES.md fix: align worker rename followups 2026-06-26 00:25:03 +09:00
LICENSE init 2026-04-04 03:30:01 +09:00
package.nix feat: build docker images with nix 2026-07-22 18:43:35 +09:00
README.md chore: remove "nix build" instruction for development 2026-07-13 23:58:36 +09:00

夜居 / Yoi agent

Yoi is an agent runtime for building, running, and orchestrating LLM Workers 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 Worker can keep durable session history, run with explicit tool and filesystem authority, delegate bounded work to child Workers, and be inspected or restored through CLI/TUI surfaces.

Main highlights:

  • Named long-running Workers with durable session and metadata records.
  • Explicit tool permissions and filesystem scopes.
  • Multi-agent orchestration with scoped coder/reviewer Workers.
  • 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-Worker 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 --worker <name>
yoi worker --help

Typical flow:

  1. Configure providers, models, profiles, prompts, and scopes.
  2. Start or attach to a named Worker 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

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.