@stratusagent/agents 0.12.2 → 0.12.4

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.
@@ -87,9 +87,9 @@ export type ConversationReader = (input: {
87
87
  * source (`destinationFor`) for the same reason as a send: a durable
88
88
  * per-tool grant would be a standing yes to every conversation the app is
89
89
  * in, which anyone who can talk to the agent could then have it quote
90
- * anywhere. So **Always allow** lasts for this session only, and a
91
- * schedule approved with a destination may read that one conversation
92
- * unattended. The channel's own rule decides which conversations are
90
+ * anywhere. So **Always allow** grants reading this one conversation,
91
+ * until revoked, and a schedule approved with a destination may read that
92
+ * one conversation unattended. The channel's own rule decides which conversations are
93
93
  * readable at all. Output is `external`: the messages are written by
94
94
  * whoever is in the conversation, not by the operator.
95
95
  */
@@ -111,9 +111,9 @@ const optionalId = (input, key, tool = MESSAGE_READ_TOOL_NAME) => {
111
111
  * source (`destinationFor`) for the same reason as a send: a durable
112
112
  * per-tool grant would be a standing yes to every conversation the app is
113
113
  * in, which anyone who can talk to the agent could then have it quote
114
- * anywhere. So **Always allow** lasts for this session only, and a
115
- * schedule approved with a destination may read that one conversation
116
- * unattended. The channel's own rule decides which conversations are
114
+ * anywhere. So **Always allow** grants reading this one conversation,
115
+ * until revoked, and a schedule approved with a destination may read that
116
+ * one conversation unattended. The channel's own rule decides which conversations are
117
117
  * readable at all. Output is `external`: the messages are written by
118
118
  * whoever is in the conversation, not by the operator.
119
119
  */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@stratusagent/agents",
3
- "version": "0.12.2",
3
+ "version": "0.12.4",
4
4
  "type": "module",
5
5
  "main": "./dist/index.js",
6
6
  "types": "./dist/index.d.ts",
@@ -18,7 +18,7 @@
18
18
  "node": ">=22.13 <23 || >=23.4"
19
19
  },
20
20
  "dependencies": {
21
- "@stratusagent/core": "0.12.2"
21
+ "@stratusagent/core": "0.12.4"
22
22
  },
23
23
  "devDependencies": {
24
24
  "@types/node": "^24.6.0",
@@ -34,7 +34,9 @@ Everything is under `~/.stratus/` on the daemon's machine:
34
34
  | `gateway.json`, `gateway-token` | Where the control API is listening, and its bearer token. `0600` |
35
35
  | `stratusd.lock` | The running daemon's claim on this home: one daemon per home |
36
36
 
37
- Deleting a soul file takes the agent off the roster but keeps its `agents/<id>/` state, its standing approvals included (a new agent given the same id inherits them), and its schedules in `fleet.db`. Deleting `agents/<id>/` erases its history, memories, grants, and files.
37
+ Souls and workspaces are normally links into a visible agents folder in the home directory: `agents/<id>.md` points to `~/Agents/<id>/soul.md` and `agents/<id>/workspace` to `~/Agents/<id>/workspace/`. That is where a person edits a soul or finds an agent's files. The folder is `~/Stratus` instead when `~/Agents` already belonged to something else. There is none (everything stays in `~/.stratus/agents/`) when both names are taken, when `~/.stratus` is on a different disk from the home directory (the Docker image), or with `STRATUS_AGENTS_DIR=off`; `STRATUS_AGENTS_DIR=<path>` chooses one outright, and `stratus doctor` names the one in use. A soul or workspace still kept as a real file under `~/.stratus/agents/` is moved there by the next `stratus serve` or `stratus update`. `fs.*` refuses every soul, under either name.
38
+
39
+ Deleting a soul file takes the agent off the roster but keeps its `agents/<id>/` state, its standing approvals included (a new agent given the same id inherits them), and its schedules in `fleet.db`. Deleting `agents/<id>/` erases its history, memories, and grants; the files in `~/Agents/<id>/workspace/` stay until that folder is deleted too. Deleting or renaming `~/Agents/<id>/` takes the agent off the roster (its state is untouched) until the folder is put back.
38
40
 
39
41
  ## Your soul
40
42