fa5828b2d3
Completes the rename started with the 9P file change.
Go API: WorkDir→CWD, SetWorkDir→SetCWD, WorkDirSetter→CWDSetter.
Unexported: workdir→cwd in fields, params, locals.
Template: {{.WorkDir}}→{{.CWD}}.
Docs: ARCHITECTURE.md, PLANNING.md, README.md, IDEAS.md.
|
||
|---|---|---|
| 9p@818ccf2632 | ||
| agents | ||
| core@a035913514 | ||
| doc | ||
| el@44df406c15 | ||
| prompts | ||
| sandbox | ||
| skills@7da6494608 | ||
| toys | ||
| tui@e4d9abbadb | ||
| .gitmodules | ||
| README.md | ||
| mkfile | ||
README.md
ollie
What happens if agent primitives are exposed as an ordinary filesystem? How much can be subtracted from AI agent implementations without reducing their usefulness? These are some of the motivating questions behind ollie.
- The core system provides a public library of AI agent primitives.
- The 9p filesystem server (Go) creates a virtual filesystem exposing the important state and behaviors as ordinary files and operations.
- A reference TUI implementation proves that it is possible to build a functioning and user-friendly terminal front-end using only the Go standard library.
- And, just because I like my Emacs friends, a reference Emacs interface front-end implementation.
Project Structure
core/:tui/:9p/:el/:
Getting Started
Clone with submodules:
git clone --recurse-submodules https://github.com/lneely/ollie.git
Or after cloning:
git submodule update --init --recursive
Building
Build everything from the monorepo root:
mk
Or build specific components:
mk core # Build core library
mk tui # Build terminal UI
mk 9p # Build 9p filesystem server
For Emacs Lisp, copy el/ollie.el into your own Emacs configuration directory, and:
(require 'ollie)
Development
Update all submodules to latest:
git submodule update --remote
Observed Benefits
Crash resiliency — reasoning_plan persists plans to the ollie/pl filesystem by default. If a session crashes or is killed mid-task, recovery is trivial: point a fresh session at the plan that was being executed. The agent's prompting already tells it how to discover plans in pl/, so it can resume cold — reading the plan, seeing which steps are done and which aren't, and picking up where the previous session left off. No context replay, no manual re-prompting, no lost work.
Credits
Many sources of inspiration:
- Plan 9 from Bell Labs — for an interesting system
- @9fans — for the Plan 9 port
- Suckless — for articulating good software development principles
- @simonfxr — for a solid agent baseline to "borrow" from, and other nifty ideas
- @aws — for a solid open-source agent implementation
License
GPLv3