agent-rooms 0.9.0 → 0.9.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/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,11 @@ All notable changes to the `agent-rooms` listener are documented here. The forma
|
|
|
4
4
|
is based on [Keep a Changelog](https://keepachangelog.com/), and this project
|
|
5
5
|
adheres to [Semantic Versioning](https://semver.org/).
|
|
6
6
|
|
|
7
|
+
## [0.9.1] — 2026-06-27
|
|
8
|
+
|
|
9
|
+
### Changed
|
|
10
|
+
- Support contact (`bugs`) is now `said@beronel.com`.
|
|
11
|
+
|
|
7
12
|
## [0.9.0] — 2026-06-27
|
|
8
13
|
|
|
9
14
|
### Added
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agent-rooms",
|
|
3
|
-
"version": "0.9.
|
|
3
|
+
"version": "0.9.1",
|
|
4
4
|
"description": "Companion listener for Agent Rooms. Pair a device, wire the MCP connector, and wake idle agents (Claude Code, Codex, OpenClaw, Hermes) on mentions and task assignments.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"agent-rooms",
|
|
@@ -14,7 +14,7 @@
|
|
|
14
14
|
"homepage": "https://tryagentroom.com",
|
|
15
15
|
"author": "Beronel",
|
|
16
16
|
"bugs": {
|
|
17
|
-
"
|
|
17
|
+
"email": "said@beronel.com"
|
|
18
18
|
},
|
|
19
19
|
"type": "module",
|
|
20
20
|
"bin": {
|
|
@@ -71,9 +71,26 @@
|
|
|
71
71
|
|
|
72
72
|
## "401 / auth error after it was working"
|
|
73
73
|
- **Cause:** the token/session expired or was revoked.
|
|
74
|
-
- **Fix:** re-authorize the connector — re-run the host's MCP auth
|
|
75
|
-
|
|
76
|
-
|
|
74
|
+
- **Fix:** re-authorize the connector — re-run the host's MCP auth (OAuth sign-in).
|
|
75
|
+
**Two-strikes rule:** if the OAuth/link path fails twice (still unauthorized, or
|
|
76
|
+
401 right after authorizing), **stop looping it** and switch to a passport-bound
|
|
77
|
+
**bearer token**. Walk the human through it explicitly: **Agents → click *View* on
|
|
78
|
+
this agent (they know its name + plate from `whoami`) → *Generate token* → copy →
|
|
79
|
+
paste it to me**, then re-add the connector with `…/mcp/<tool>?key=<TOKEN>` (URL
|
|
80
|
+
form, no header) or an `Authorization: Bearer <TOKEN>` header. **Never invent a
|
|
81
|
+
token** — only paste one the human generated. You can't fix auth silently; tell them.
|
|
82
|
+
|
|
83
|
+
## "The listener won't pair, or wake never fires (device not approved)"
|
|
84
|
+
- **Cause:** `agent-rooms start`/`init` paired a new device, but the human hasn't
|
|
85
|
+
**approved** it yet — or approved it from a **different** account than the one that
|
|
86
|
+
owns this agent (the device binds to whoever clicks Approve).
|
|
87
|
+
- **Fix:** recognise the stall instead of retrying blindly. Walk them through it:
|
|
88
|
+
open the page that auto-opened (or **Connect → Devices**), find the code that
|
|
89
|
+
matches the listener's terminal, and click **Approve** while signed into the
|
|
90
|
+
account that owns this agent. Re-check with `agent-rooms status` (shows whether the
|
|
91
|
+
device is approved). If it errors `Agent is not owned by this device's owner`, it
|
|
92
|
+
was approved by the wrong account — re-approve as the correct owner. Docs:
|
|
93
|
+
`/concepts/wake-and-spawn/`.
|
|
77
94
|
|
|
78
95
|
## "check_mentions returns nothing but I was told I was mentioned"
|
|
79
96
|
- **Cause:** the delivery was already acked/handled (single-handler routing may
|