patchcord 0.5.25 → 0.5.27
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
|
@@ -74,6 +74,8 @@ 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.
|
|
78
|
+
|
|
77
79
|
1. Read the message from `inbox()` or `wait_for_message()`. Check `message.thread` / `message.thread_id` if present.
|
|
78
80
|
2. Do the work - use real code, real files, real results from your project
|
|
79
81
|
3. Reply with the right flag:
|
|
@@ -84,6 +84,8 @@ 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.
|
|
88
|
+
|
|
87
89
|
1. Read messages from inbox(). Check `message.thread` / `message.thread_id` if present.
|
|
88
90
|
2. Check the context tag - is this for your chat?
|
|
89
91
|
3. If yes: do the work, then reply with the right flag:
|
|
@@ -28,7 +28,9 @@ mkdir -p "$STABLE_DIR"
|
|
|
28
28
|
cp "$SRC_STATUSLINE" "$STABLE_STATUSLINE"
|
|
29
29
|
chmod +x "$STABLE_STATUSLINE"
|
|
30
30
|
|
|
31
|
-
|
|
31
|
+
# Write $HOME literally (not expanded) so settings.json is portable
|
|
32
|
+
# across machines/users — Claude Code's shell expands it at runtime.
|
|
33
|
+
NEW_CMD="bash \"\$HOME/.claude/patchcord/statusline.sh\"${EXTRA_ARGS}"
|
|
32
34
|
|
|
33
35
|
# Decide where to write
|
|
34
36
|
USER_SETTINGS="$HOME/.claude/settings.json"
|
package/skills/inbox/SKILL.md
CHANGED
|
@@ -61,6 +61,8 @@ 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.
|
|
65
|
+
|
|
64
66
|
1. Read the message. If it belongs to a thread, `message.thread` and `message.thread_id` will be present.
|
|
65
67
|
2. Do the work described in the message - using your project's actual code, real files, real lines
|
|
66
68
|
3. Reply with what you did, choosing the right flag:
|