@homingbird/mcp 0.1.3 → 0.3.0

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 CHANGED
@@ -40,7 +40,7 @@ npx -y @homingbird/mcp --server https://<server> --desk
40
40
 
41
41
  `--desk` makes this client your desk: the one session that holds the event stream, checks the inbox
42
42
  when it starts and answers the notes that arrive: a draft, a holding reply when it cannot answer yet, or
43
- `skip_note` with a reason only you see. What it relied on (`basis`) is shown to you on the draft in the web client and kept in the audit log; the colleague never sees it. Keep only one desk; every other session drafts only when you ask it.
43
+ `skip_note` with a reason only you see. What it relied on (`basis`) is shown to you on the draft in the web client; the colleague never sees it. Keep only one desk; every other session drafts only when you ask it.
44
44
 
45
45
  ## Run your desk from your MCP client
46
46
 
@@ -65,7 +65,7 @@ or `--desk`, not both.
65
65
  - **One desk.** It claims your desk on this computer, as `homingbird run` does. When another one
66
66
  holds it, such as a second app with the same configuration or a runner in a terminal, this one waits,
67
67
  says so in `status`, and takes over when that one stops. Only runners take part: a desk on another
68
- computer, a client started with `--desk`, or the Claude Code mod's pane is not seen, so do not run
68
+ computer, a client started with `--desk`, or the Claude Code plugin's pane is not seen, so do not run
69
69
  one of those as well.
70
70
  - **Pausing.** The `desk` prompt with `on` or `off` sets the desk on or off; asking twice changes
71
71
  nothing more, and it takes no command. Clients that offer prompts as slash commands show it: in