patchcord 0.5.27 → 0.5.29

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "patchcord",
3
- "version": "0.5.27",
3
+ "version": "0.5.29",
4
4
  "description": "Cross-machine agent messaging for Claude Code and Codex",
5
5
  "author": "ppravdin",
6
6
  "license": "MIT",
@@ -74,7 +74,7 @@ If send_message fails with a send gate error: call inbox(), reply to or resolve
74
74
 
75
75
  ## Receiving workflow
76
76
 
77
- **Check the age first.** Every pending message shows a relative timestamp like `(3h ago)` or `(45d ago)`. For action requests older than 7 days, **do not execute** — ask the human first. Old tasks are usually already done, superseded, or no longer wanted. Ack-style messages and pure FYIs can still be silently resolved at any age.
77
+ Action requests older than 7d (per the `(Xd ago)` stamp): ask human before executing. Acks/FYIs silent-resolve at any age.
78
78
 
79
79
  1. Read the message from `inbox()` or `wait_for_message()`. Check `message.thread` / `message.thread_id` if present.
80
80
  2. Do the work - use real code, real files, real results from your project
@@ -87,6 +87,8 @@ If send_message fails with a send gate error: call inbox(), reply to or resolve
87
87
 
88
88
  When you have multiple pending messages, prioritize by urgency. Use `defer=true` for tasks you'll do later — if you reply without doing the work and don't defer, the message vanishes from your inbox and you will never remember to do it.
89
89
 
90
+ Outdated deferred (work likely done, sender moved on): ask human "resolve [Xd]-old from [sender]?" before `reply(id, resolve=true)`. Don't unilaterally drop.
91
+
90
92
  ## Cross-user messaging (Gate)
91
93
 
92
94
  To message a user outside your namespace, use `@username` as the to_agent. Example: `send_message("@maria", "hello")`. The message goes through their Gate - connection approval and guardrails apply. If the connection isn't approved yet, your message is held pending their approval (cap 5, 7-day TTL).
@@ -84,7 +84,7 @@ After sending to an offline agent, tell the human: "Message sent. [agent] is not
84
84
 
85
85
  ## Receiving workflow
86
86
 
87
- **Check the age first.** Every pending message shows a relative timestamp like `(3h ago)` or `(45d ago)`. For action requests older than 7 days, **do not execute** — ask the human first. Old tasks are usually already done, superseded, or no longer wanted. Ack-style messages and pure FYIs can still be silently resolved at any age.
87
+ Action requests older than 7d (per the `(Xd ago)` stamp): ask human before executing. Acks/FYIs silent-resolve at any age.
88
88
 
89
89
  1. Read messages from inbox(). Check `message.thread` / `message.thread_id` if present.
90
90
  2. Check the context tag - is this for your chat?
@@ -97,6 +97,8 @@ After sending to an offline agent, tell the human: "Message sent. [agent] is not
97
97
 
98
98
  When you have multiple pending messages, prioritize by urgency. Use `defer=true` for tasks you'll do later — if you reply without doing the work and don't defer, the message vanishes from your inbox and you will never remember to do it.
99
99
 
100
+ Outdated deferred (work likely done, sender moved on): ask human "resolve [Xd]-old from [sender]?" before `reply(id, resolve=true)`. Don't unilaterally drop.
101
+
100
102
  ## File sharing
101
103
 
102
104
  As a web agent, you CANNOT PUT to presigned URLs (egress is blocked). Two options:
@@ -61,7 +61,7 @@ If send_message fails with a send gate error: call inbox(), reply to or resolve
61
61
 
62
62
  ## Receiving (inbox has messages)
63
63
 
64
- **Check the age first.** Every pending message shows a relative timestamp like `(3h ago)` or `(45d ago)`. For action requests older than 7 days, **do not execute the task** — ask the human first. Old tasks are usually already done, superseded, or no longer wanted. Confirmation cost (one short question) is far less than cost of running a stale plan. Ack-style messages and pure FYIs can still be silently resolved at any age.
64
+ Action requests older than 7d (per the `(Xd ago)` stamp): ask human before executing. Acks/FYIs silent-resolve at any age.
65
65
 
66
66
  1. Read the message. If it belongs to a thread, `message.thread` and `message.thread_id` will be present.
67
67
  2. Do the work described in the message - using your project's actual code, real files, real lines
@@ -75,6 +75,8 @@ If send_message fails with a send gate error: call inbox(), reply to or resolve
75
75
 
76
76
  When you have multiple pending messages, prioritize by urgency. Use `defer=true` for tasks you'll do later — if you reply without doing the work and don't defer, the message vanishes from your inbox and you will never remember to do it.
77
77
 
78
+ Outdated deferred (work likely done, sender moved on): ask human "resolve [Xd]-old from [sender]?" before `reply(id, resolve=true)`. Don't unilaterally drop.
79
+
78
80
  ## Cross-user messaging (Gate)
79
81
 
80
82
  To message a user outside your namespace, use `@username` as the to_agent. Example: `send_message("@maria", "hello")`. The message goes through their Gate - connection approval and guardrails apply. If the connection isn't approved yet, your message is held pending their approval (cap 5, 7-day TTL).