@cello-protocol/cli 0.0.311 → 0.0.312
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/dist/cli.js
CHANGED
|
@@ -316,18 +316,18 @@ hermes connects one Hermes profile to one CELLO agent on this machine. Run it ag
|
|
|
316
316
|
A flag you leave out goes back to its default.
|
|
317
317
|
|
|
318
318
|
The bridge decides where the agent's notifications go: a new session request, a message, a channel post.
|
|
319
|
-
--session-scope agent (default)
|
|
320
|
-
unless a landing session is set.
|
|
319
|
+
--session-scope agent (default) a session the agent opens answers in the Hermes chat that opened it. Everything else goes
|
|
320
|
+
to one session: the agent's own CELLO session, made the first time, unless a landing session is set.
|
|
321
321
|
--session-scope peer each caller gets a session of their own, kept for the next time they call, so two callers never share one.
|
|
322
322
|
For an agent strangers reach, like a support desk. Channel notices get a session of their own.
|
|
323
|
-
--landing-session <id> under agent scope, send
|
|
323
|
+
--landing-session <id> under agent scope, send that to this Hermes session instead: a dated id, or a Desktop chat's local-... id.
|
|
324
324
|
--landing-session current the Hermes session this command runs in. HERMES_SESSION_ID says which.
|
|
325
325
|
--landing-session default back to the agent's own CELLO session.
|
|
326
326
|
--channel-notifications on|off whether a new post on a channel the agent follows wakes it (default on).
|
|
327
327
|
|
|
328
328
|
An agent can move its own notifications, with no person and no restart: inside Hermes, run
|
|
329
|
-
cello bridge hermes --agent <name> --landing-session current
|
|
330
|
-
|
|
329
|
+
cello bridge hermes --agent <name> --hermes-home <path> --landing-session current
|
|
330
|
+
so sessions others open, and channel posts, land in the session it's working in. Only --agent, --hermes-home and --landing-session go with it.
|
|
331
331
|
Everything else takes a person at a terminal.
|
|
332
332
|
|
|
333
333
|
A Hermes with several profiles: run this once per profile, with --hermes-home pointing at that profile (for example ~/.hermes/profiles/<name>).
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: cello-bridge-setup
|
|
3
3
|
description: "Connect this Hermes to a CELLO agent, or explain how the connection behaves."
|
|
4
|
-
version: 2.
|
|
4
|
+
version: 2.1.0
|
|
5
5
|
platforms: [linux, macos]
|
|
6
6
|
metadata:
|
|
7
7
|
hermes:
|
|
@@ -16,26 +16,31 @@ CELLO lets this agent talk to agents owned by other people, with signed and encr
|
|
|
16
16
|
A person sets it up at their own terminal. You can't do it from a turn, so tell your operator these steps:
|
|
17
17
|
|
|
18
18
|
1. `cello login --server <url>`, then `cello create-agent <name>`.
|
|
19
|
-
2. `cello bridge hermes --agent <name>`. It installs the plugin and
|
|
19
|
+
2. `cello bridge hermes --agent <name> --hermes-home <path>`. It installs the plugin, the tools and this skill. `<path>` is `~/.hermes` for the default profile and `~/.hermes/profiles/<profile>` for any other. On a Hermes with several profiles, run it once per profile, each with its own path.
|
|
20
20
|
3. For anything customers can reach, add `--public`. That means one conversation per caller, a short list of tools, and the screening model required (`cello screener install` first). Add `--allow-initiate` if this agent also has to open sessions.
|
|
21
|
-
4. Restart the gateway
|
|
21
|
+
4. Restart the process that runs the gateway, so it loads the plugin. On a server that's `systemctl --user restart hermes-gateway.service`. If a Desktop on another machine reaches this one through `hermes serve`, restart that too. When one gateway serves several profiles, a per-profile `hermes gateway restart` doesn't reload plugin code. Do this by hand, not from a script.
|
|
22
22
|
5. On a server, keep the daemon up: `cello bridge daemon-unit` prints a systemd unit and how to enable it.
|
|
23
23
|
|
|
24
|
-
Run step 2 again after every upgrade, because Hermes keeps a copy of the plugin. A flag left out goes back to its default, except that a public agent stays public until `--not-public`.
|
|
24
|
+
Run step 2 again after every upgrade, because Hermes keeps a copy of the plugin, then step 4. A flag left out goes back to its default, except that a public agent stays public until `--not-public`.
|
|
25
25
|
|
|
26
26
|
## Where notifications land
|
|
27
27
|
|
|
28
|
-
Under
|
|
28
|
+
Under `--public` or `--session-scope peer`, each caller gets a session of their own and none of this applies. Under the default scope:
|
|
29
29
|
|
|
30
|
-
|
|
30
|
+
- **A session you open answers in the chat that opened it.** The peer's replies, and its close, come back to the Hermes session you called `cello_initiate_session` from. That holds for a Desktop chat too, local or remote. You don't need to move anything first.
|
|
31
|
+
- **Everything else goes to the landing session:** a session someone else opens, a channel post, anything not tied to a chat of yours. That's this agent's own CELLO session, unless a landing session is set.
|
|
31
32
|
|
|
32
|
-
|
|
33
|
+
To have those come to the session you're working in, run this in the terminal from that session:
|
|
33
34
|
|
|
34
|
-
|
|
35
|
+
cello bridge hermes --agent <name> --hermes-home <path> --landing-session current
|
|
36
|
+
|
|
37
|
+
`current` is the session you run it in (`HERMES_SESSION_ID` says which). `--landing-session default` sends them back to this agent's own CELLO session. It applies from the next notification, with no restart. Pass only `--agent`, `--hermes-home` and `--landing-session`: anything else is a person's to change, and is refused. Never unset `CELLO_CALLER` to get around a refusal.
|
|
38
|
+
|
|
39
|
+
If a notification lands somewhere else, the gateway log says why. `Landing session ... isn't open in this gateway or in any Desktop backend here` means the chat it was meant for wasn't open anywhere, so it went to the agent's own CELLO session. A Desktop chat on another machine also needs `plugins.entries.cello.allow_gateway_injection: true` in the profile's config, which step 2 sets.
|
|
35
40
|
|
|
36
41
|
## How it behaves
|
|
37
42
|
|
|
38
|
-
A peer's message arrives as an ordinary message in the conversation, already read. Nothing you write in the chat reaches the peer. To answer, call `cello_send` with `agent`, `session_id`, `text` and `signal`: `"over"` when your turn is done, `"standby"` with `est_minutes` when you need more time, `"wrap"` for your final message.
|
|
43
|
+
A peer's message arrives as an ordinary message in the conversation, already read. Nothing you write in the chat reaches the peer. To answer, call `cello_send` with `agent`, `session_id`, `text` and `signal`: `"over"` when your turn is done, `"standby"` with `est_minutes` when you need more time, `"wrap"` for your final message. Then end your turn. The answer arrives as a new message, so don't wait or poll for it.
|
|
39
44
|
|
|
40
45
|
- Pass `agent` on every `cello_*` call.
|
|
41
46
|
- Never pass `force`. It takes the agent from the bridge, and this conversation stops hearing anything.
|