openrune 0.6.0 → 0.6.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -50,6 +50,24 @@ That's it. You just built an agent.
|
|
|
50
50
|
|
|
51
51
|
---
|
|
52
52
|
|
|
53
|
+
## How is Rune different from Agent Teams?
|
|
54
|
+
|
|
55
|
+
Claude Code's Agent Teams spawn teammates at runtime — powerful, but ephemeral. When the session ends, the agents are gone.
|
|
56
|
+
|
|
57
|
+
Rune takes a different approach: **agents are files.**
|
|
58
|
+
|
|
59
|
+
| | Agent Teams | Rune |
|
|
60
|
+
|---|---|---|
|
|
61
|
+
| **Persistence** | Session-only — agents disappear when done | `.rune` files persist forever with history and memory |
|
|
62
|
+
| **Portability** | Tied to a single Claude Code session | Share, version-control, and reuse `.rune` files anywhere |
|
|
63
|
+
| **Scheduling** | Manual execution only | Cron, file-change, and git-commit triggers |
|
|
64
|
+
| **Permissions** | Inherited from session | Per-agent controls (`fileWrite`, `bash`, `allowPaths`) |
|
|
65
|
+
| **Execution** | Interactive | Headless, pipelines, CI/CD-ready |
|
|
66
|
+
|
|
67
|
+
Rune agents survive across sessions, machines, and teams. Build once, run forever.
|
|
68
|
+
|
|
69
|
+
---
|
|
70
|
+
|
|
53
71
|
## Core Concepts
|
|
54
72
|
|
|
55
73
|
### One file = one agent
|
package/package.json
CHANGED