ticlawk 0.1.16-dev.2 → 0.1.16-dev.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticlawk",
-  "version": "0.1.16-dev.2",
+  "version": "0.1.16-dev.4",
   "description": "Local connector that links agent harnesses (Claude Code, Codex, OpenClaw, opencode, Pi) to the Ticlawk mobile app.",
   "type": "module",
   "main": "ticlawk.mjs",

package/src/adapters/ticlawk/index.mjs

@@ -1357,6 +1357,22 @@ export function createTiclawkAdapter(ctx) {
       });
     },
 
+    // Daemon-driven impersonated reply: the runtime never reached
+    // `ticlawk message send` (subprocess died, timeout, etc.), so the
+    // daemon speaks for the agent. Used by reportSubprocessFailure
+    // with visibility='admin' so the notice only reaches owners.
+    async postAgentReply(binding, { conversationId, text, replyToMessageId, visibility }) {
+      if (!conversationId || !text) return null;
+      return api.sendAgentMessage({
+        actingAgentId: binding.id,
+        conversationId,
+        text,
+        replyToMessageId: replyToMessageId || null,
+        runtimeHostId: hostId,
+        visibility: visibility || null,
+      });
+    },
+
     async emitEvent(binding, payload) {
       if (!payload?.event) return;
       await api.postEvent({

package/src/runtimes/_shared/standing-prompt.mjs

@@ -140,7 +140,7 @@ Only top-level group / DM messages can become tasks. Messages inside threads are
 
 ### Conversation etiquette
 
-- **Respect ongoing conversations.** If a human is having a back-and-forth with another person (human or agent) on a topic, their follow-up messages are directed at that person — only join if you are explicitly @mentioned or clearly addressed.
+- **Match your engagement to who the message addresses.** A direct @mention or imperative aimed at you — respond. A broadcast to the whole group (no specific addressee, request implying every applicable member should answer) — your turn to engage, same as a mention; answer the current message as the prompt, don't substitute history for it. A back-and-forth between two specific people on a topic — third parties stay quiet unless @mentioned. Pure agent-to-agent chatter you have no stake in — stay quiet.
 - **Only the person doing the work should report on it.** If someone else completed a task or submitted a PR, don't echo or summarize their work — let them respond to questions about it.
 - **Claim before you start.** Always call \`ticlawk task claim\` before doing any work on a task. If the claim fails, stop immediately and pick a different task.
 - **Before stopping, check for concrete blockers you own.** If you still owe a specific handoff, review, decision, or reply that is currently blocking a specific person, send one minimal actionable message to that person or group before stopping.