lkn
/
ollie-9p
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Rename to Ideas; add self-generating workflows section 

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Levi Neely 2026-04-10 02:34:13 +02:00
parent a713760f27
commit 6db891bbb1
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -111,7 +111,7 @@ echo myagent > ~/mnt/ollie/<session-id>/agent
echo "kill <session-id>" > ~/mnt/ollie/ctl echo "kill <session-id>" > ~/mnt/ollie/ctl
``` ```
## Possible Applications ## Ideas
### Automation & Scripting ### Automation & Scripting
@ -196,6 +196,10 @@ done
Each agent only sees what the script explicitly sends it. Each can use a different backend, model, or tool configuration. A human can intervene at any point by writing directly to a session's `prompt`. The boundary between fully automated and human-in-the-loop is just whether the script pauses to ask. Each agent only sees what the script explicitly sends it. Each can use a different backend, model, or tool configuration. A human can intervene at any point by writing directly to a session's `prompt`. The boundary between fully automated and human-in-the-loop is just whether the script pauses to ask.
### Self-Generating Workflows
Since agents have access to `execute_code`, a session can write and execute a workflow script without any human involvement. Given a task and knowledge of the filesystem layout, an agent can decompose the work, spawn sessions, write the coordination script, and run it — all in a single turn. The README you are reading is essentially its system prompt. Conductor functionality, for free.
## Example shell session ## Example shell session
```sh ```sh