oomi-ai 0.7.0 → 0.7.1

package/agent_instructions.md

@@ -338,3 +338,9 @@ Use `oomi routines pause|resume|end <routine-id> --file action.json` with expect
 For instructions in another chat, the user must first grant this connection routineManagementEnabled through Oomi Agent settings or `routines settings` using an authenticated Oomi sourceMessageId. Then routine/response mutations can substitute externalInstruction:{channel,messageId,instruction} for sourceMessageId. Record the actual message reference and instruction. Oomi labels this runtime-attested, not independently authenticated. Never turn on the permission yourself or invent external approval. Ownership, data permissions, and primary selection remain separate.
 
 The running bridge receives routine.approved, routine.due, routine.changed, routine.response_recorded, and primary_agent.changed. Ordinary events sync quietly without a model call; explicitly enabled routine wakes are bounded and are not retried after an uncertain model dispatch. Refresh canonical state before acting on a delayed event. Due events already have notificationHandled:true; do not send another phone alert or message for every event. Persist useful context for the next conversation. If a follow-up is explicitly linked to an event, include relatedEventId in the notification API so Oomi suppresses an extra push. Keep Oomi credentials private; all /v1/routines, /v1/agent_preferences, /v1/routine_occurrences, and /v1/agent_events requests use the saved device bearer token, never a user ID supplied by the agent.
+
+### Reply first, then share routine cards
+
+Always answer the person in your own conversational voice after a routine or Space tool succeeds. Explain what you recommend or what changed, and invite a useful next step when appropriate. A tool result or review card is not the reply. Do not return only routine names, IDs, JSON, or a stock list of chips. Mention the routines that actually belong to this request; do not automatically recreate or list three routines on unrelated requests. Oomi places newly created routine cards beneath the completed reply in that creation turn. Later approvals update the original card in place. Keep talking normally after a user starts or changes a routine; do not require another UI click when their instruction is already clear.
+
+Oomi renders simple Markdown in chat: short paragraphs, bullet or numbered lists, and **bold**. Keep replies brief and scannable, and put long plans in a Space note instead of the chat. A Space link in your reply appears as a card, so share it once rather than repeating the URL or listing IDs.

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "oomi-ai",
   "name": "Oomi Channel Plugin",
   "description": "Oomi connection, Spaces, health context and routines. Run oomi capabilities and oomi instructions; ordinary state updates do not invoke a model.",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "author": "Oomi",
   "license": "MIT",
   "openclawVersion": ">=0.5.0",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oomi-ai",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Connect OpenClaw, Hermes, and other local agents to Oomi with verified runtime adapters",
   "bin": {
     "oomi": "bin/oomi-ai.js"

package/skills/oomi/SKILL.md

@@ -336,3 +336,9 @@ Use `oomi routines pause|resume|end <routine-id> --file action.json` with expect
 For instructions in another chat, the user must first grant this connection routineManagementEnabled through Oomi Agent settings or `routines settings` using an authenticated Oomi sourceMessageId. Then routine/response mutations can substitute externalInstruction:{channel,messageId,instruction} for sourceMessageId. Record the actual message reference and instruction. Oomi labels this runtime-attested, not independently authenticated. Never turn on the permission yourself or invent external approval. Ownership, data permissions, and primary selection remain separate.
 
 The running bridge receives routine.approved, routine.due, routine.changed, routine.response_recorded, and primary_agent.changed. It acknowledges after the runtime accepts each event and retries failures. Refresh canonical state before acting on a delayed event. Due events already have notificationHandled:true; do not send another phone alert or message for every event. Persist useful context for the next conversation. If a follow-up is explicitly linked to an event, include relatedEventId in the notification API so Oomi suppresses an extra push. Keep Oomi credentials private; all /v1/routines, /v1/agent_preferences, /v1/routine_occurrences, and /v1/agent_events requests use the saved device bearer token, never a user ID supplied by the agent.
+
+### Reply first, then share routine cards
+
+Always answer the person in your own conversational voice after a routine or Space tool succeeds. Explain what you recommend or what changed, and invite a useful next step when appropriate. A tool result or review card is not the reply. Do not return only routine names, IDs, JSON, or a stock list of chips. Mention the routines that actually belong to this request; do not automatically recreate or list three routines on unrelated requests. Oomi places newly created routine cards beneath the completed reply in that creation turn. Later approvals update the original card in place. Keep talking normally after a user starts or changes a routine; do not require another UI click when their instruction is already clear.
+
+Oomi renders simple Markdown in chat: short paragraphs, bullet or numbered lists, and **bold**. Keep replies brief and scannable, and put long plans in a Space note instead of the chat. A Space link in your reply appears as a card, so share it once rather than repeating the URL or listing IDs.

package/skills/oomi/agent_instructions.md

@@ -341,3 +341,9 @@ Use `oomi routines pause|resume|end <routine-id> --file action.json` with expect
 For instructions in another chat, the user must first grant this connection routineManagementEnabled through Oomi Agent settings or `routines settings` using an authenticated Oomi sourceMessageId. Then routine/response mutations can substitute externalInstruction:{channel,messageId,instruction} for sourceMessageId. Record the actual message reference and instruction. Oomi labels this runtime-attested, not independently authenticated. Never turn on the permission yourself or invent external approval. Ownership, data permissions, and primary selection remain separate.
 
 The running bridge receives routine.approved, routine.due, routine.changed, routine.response_recorded, and primary_agent.changed. Ordinary events sync quietly without a model call; explicitly enabled routine wakes are bounded and are not retried after an uncertain model dispatch. Refresh canonical state before acting on a delayed event. Due events already have notificationHandled:true; do not send another phone alert or message for every event. Persist useful context for the next conversation. If a follow-up is explicitly linked to an event, include relatedEventId in the notification API so Oomi suppresses an extra push. Keep Oomi credentials private; all /v1/routines, /v1/agent_preferences, /v1/routine_occurrences, and /v1/agent_events requests use the saved device bearer token, never a user ID supplied by the agent.
+
+### Reply first, then share routine cards
+
+Always answer the person in your own conversational voice after a routine or Space tool succeeds. Explain what you recommend or what changed, and invite a useful next step when appropriate. A tool result or review card is not the reply. Do not return only routine names, IDs, JSON, or a stock list of chips. Mention the routines that actually belong to this request; do not automatically recreate or list three routines on unrelated requests. Oomi places newly created routine cards beneath the completed reply in that creation turn. Later approvals update the original card in place. Keep talking normally after a user starts or changes a routine; do not require another UI click when their instruction is already clear.
+
+Oomi renders simple Markdown in chat: short paragraphs, bullet or numbered lists, and **bold**. Keep replies brief and scannable, and put long plans in a Space note instead of the chat. A Space link in your reply appears as a card, so share it once rather than repeating the URL or listing IDs.