Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity
7f9b6c01b5
yoi/crates/worker
History
Hare 88c2edefd4
merge: prepare llm engine for publish
2026-07-16 01:45:09 +09:00
..
examples refactor: remove old pod crates 2026-06-29 04:44:55 +09:00
src merge: prepare llm engine for publish 2026-07-16 01:45:09 +09:00
tests refactor: separate worker workspace identity 2026-07-11 09:58:20 +09:00
build.rs refactor: rename pod crate to worker 2026-06-26 00:05:57 +09:00
Cargo.toml refactor: fold provider crate into engine 2026-07-15 00:58:29 +09:00
README.md refactor: remove old pod crates 2026-06-29 04:44:55 +09:00

README.md

worker

Role

worker turns an llm-engine Engine into a named runtime entity with manifest configuration, scoped tools, session persistence, protocol handling, and Worker metadata integration.

Boundaries

Owns:

  • Worker lifecycle and socket protocol serving
  • Engine construction around a resolved Manifest
  • session-store and session-store worker metadata coordination
  • built-in tool registration under scope/policy
  • spawned-child orchestration hooks

Does not own:

  • provider-specific wire formats (provider / llm-engine clients)
  • product CLI parsing (yoi)
  • TUI display authority (tui)
  • current-state storage schema outside Worker metadata (session-store worker metadata)

Design notes

A Worker is runtime authority, not UI state. It should commit model-visible events through history/session paths and keep current Worker-name state in Worker metadata rather than in transient runtime files.

See also