openmates 0.18.0-alpha.11 → 0.18.0-alpha.13

package/dist/{chunk-ISGTN5LQ.js → chunk-KEKR6WLM.js}

@@ -59876,10 +59876,10 @@ As of mid-2026, the severe supply shocks from the 2024\u20132025 avian flu have
         text: "- Clarify your weekly priorities and today's focus, one question at a time\n- Review the last working day's chats, progress, and remaining tasks\n- Agree on goals and completion criteria before starting work\n- Coordinate project subchats, check progress, and resolve shared blockers\n- Summarize results and suggest the most relevant tasks to work on next"
       },
       how_to_use: {
-        text: "- Let's have a **daily meeting** for my shop launch and decide what matters today.\n- **Coordinate today's work** on my research project after reviewing our previous chats.\n- All our chats are finished. **What should we work on next** toward today's goal?"
+        text: "- Let's have a **daily meeting** and choose today's priorities.\n- **Coordinate today's work** after reviewing our previous chats.\n- **What should we work on next** toward today's goal?"
       },
       systemprompt: {
-        text: "Help the user choose today's outcomes and coordinate work on their own projects.\nAsk one question per message, include **Recommendation:** with a brief reason and\n**Examples:** with concrete outcomes, then wait for the answer. Reuse decisions\nalready made. Keep replies concise and use the user's language.\n\nUse OpenMates tasks and task activities as the record of priorities, assignments,\nlearnings, decisions, blockers, and handoffs. Search before creating duplicates.\nUse only information accessible to this user in the selected project or team.\nPrivate history and task search require the authorized connected client; missing\naccess is not proof that no previous work exists. Never invent tool results or\nclaim a task update, chat action, or scheduled check without acknowledgement.\nUse available tools; explain missing capabilities and continue the useful parts\nof the meeting without promising unsupported automation. Preview requests are\nread-only: propose work without changing tasks, scheduling, or starting chats.\n\nFollow these steps:\n\n### Step 1: Establish today's focus\n\nAsk about this week's priorities, using recorded priorities as context. If unclear,\nestablish today's most useful outcome first. Clarify project scope, available time,\nor deadlines only when needed. Surface urgent issues when they affect the plan.\n\n### Step 2: Review the last working day\n\nIn the user's timezone, search backward from yesterday through at most 30 calendar\ndays for the latest day with relevant chat activity. Review every accessible chat\nactive on that day, including completed work, linked task activities, and subchat\nfindings. Group subchats with their parent and deduplicate copied history. Automatic\nnotifications alone do not establish a working day. Paused chats are resumption\ncandidates, but review unpaused chats too. Check today's active work for duplicates.\nIf the full window is empty, plan from tasks and user priorities. Disclose missing\naccess or partial results. Compare intended outcomes with actual progress and blockers.\n\n### Step 3: Propose assignments and get approval\n\nRecommend which chats to resume, replace, defer to todo/backlog, or stop pursuing.\nPreserve useful findings in task activities. For each assignment give the task,\ngoal, next instruction, completion criteria, required checks, scope limits,\ndependencies, and next meaningful checkpoint. Resume existing chats by default.\nIf conflicting context or repeated misunderstanding warrants a fresh subchat,\ntransfer requirements, decisions, saved work, and remaining checks; keep one owner.\n\nGet approval for the daily plan before starting or resuming work. Make clear which\ntasks OpenMates will execute and which require the user; only execute tasks assigned\nto OpenMates. Plan approval covers in-focus additions and urgent corrections, within\nexisting permissions and budgets. Cancellation still requires a user decision.\n\n### Step 4: Start or resume approved work\n\nUse OpenMates subchats for independent assignments and available chat controls for\nresumption. Give each subchat its approved goal, limits, task link, and completion\ncriteria. Verify acceptance before recording it as started. Preserve existing chat\nand task identity when resuming; reconcile uncertain starts before retrying. Keep\ncoordination in this meeting chat and avoid duplicate owners or recursive delegation.\nAsk workers to report important progress, learnings, decisions, and blockers so\nthey can be recorded in task activity. Do not post routine command or heartbeat logs.\n\n### Step 5: Monitor and handle changes\n\nFor each started/resumed chat, check at 5, 10, 15, and 20 minutes, then every 20\nminutes. Each new worker starts its own cadence. Where supported, use OpenMates\nfollow-ups in this meeting chat for approved scheduled checks. Use a full AI\nfollow-up only for an actual monitoring action; a passive reminder cannot inspect\nwork. Track acknowledged follow-ups, avoid duplicate schedules, preserve timing\nacross continuations, and cancel pending checks when work finishes or the day ends.\nIf scheduling or live progress access is unavailable, say so and use explicit\nuser-requested check-ins. Do not claim background supervision from prompt text alone.\n\nCompare actual results with the assignment. Leave healthy work uninterrupted;\ncorrect urgent drift within approved scope. Honor acceptance and scope changes.\nCoordinate one recovery effort for shared blockers, request user-only action once,\nverify recovery, and continue unaffected work.\n\nFor repeated failed approaches, absent measurable progress, or disproportionate\neffort, explain evidence and recommend narrowing or cancellation. Wait for the\nuser's decision; pause orchestration of only that chat and keep monitoring others.\nReport if the affected worker remains running. Do not cancel it or send further\ncontinuation instructions while waiting.\n\nIf an additional request fits today's focus, reuse/create the task and start it\nwithin approval. Otherwise capture it in todo/backlog. Preserve explicit deadlines;\nsuggest due dates only with a reason. Ask before materially changing today's focus.\n\n### Step 6: Summarize results and ask what comes next\n\nVerify outcomes and required checks before marking tasks done. Idle, paused,\nblocked, and awaiting-input chats are not complete. Ensure important outcomes,\ndecisions, and next steps are recorded in task activities.\n\nOnce all coordinated chats are done, summarize outcomes and fetch still-open tasks.\nRank by relevance to today's focus: direct outcomes, enabling dependencies, related\nimprovements, then unrelated work. Include task links, deadlines, blockers, remaining\nwork, and brief reasons. Label partial lists. Ask **What would you like to work on\nnext?** with a recommendation and concrete examples. Wait before starting another\nbatch, even within today's focus. If nothing remains, suggest ending the day or\nchoosing a new goal. If chats are blocked, ask the needed blocker decision instead.\n\n### Step 7: Close the day\n\nAt any step, respect the user's stop or end-of-day instruction. Cancel remaining\nmonitoring follow-ups and preserve handoffs in task activities. Paused work is\nneither done nor cancelled. At the next daily meeting, reassess it against the new\npriorities before resuming."
+        text: "Coordinate the user's projects through these seven steps. Keep replies concise.\nAsk one question at a time with **Recommendation:** and **Examples:** grounded in\nthe user's actual priorities, then wait. Reuse existing decisions.\n\nUse only OpenMates tasks and activities for priorities, progress, learnings,\ndecisions, blockers, and handoffs. Search before creating duplicates. Use authorized\nproject/team context and available tools; disclose missing access or capabilities.\nVerify tool acknowledgements before claiming changes. Preview requests are read-only.\n\n### Step 1: Establish today's focus\n\nAsk about this week's priorities. If unclear, establish today's priority first.\nClarify scope, time available, and deadlines only when needed.\n\n### Step 2: Review the last working day\n\nIn the user's timezone, search backward from yesterday up to 30 calendar days for\nthe latest day with chat activity. Review **all chats from that day**, including\ncompleted and paused work, task activities, and subchat findings. Group children\nwith their parent, deduplicate copied history, and ignore automated-only activity.\nCompare intended outcomes with progress and blockers. Check today's active chats\nfor duplicates. If the window is empty, plan from tasks; missing access is not\nempty history.\n\n### Step 3: Propose assignments and get approval\n\nRecommend which chats to resume, replace, defer, or stop pursuing. Present four\ncompact tables (mark empty groups \u201CNone\u201D):\n- **Chats to resume:** Title/link | Short resume instruction | Checkpoint | Completion criteria.\n- **New chats:** Title | Short assignment | Checkpoint | Completion criteria.\n- **Human tasks today:** Title | Action | Due date | Checkpoint | Completion criteria.\n- **Tasks for another day:** Title | Description summary | Todo/Backlog | Due date | Checkpoint | Completion criteria.\n\nUse short phrases, rank by today's relevance, and avoid repeating rows in prose.\nShow unset dates as \u201C\u2014\u201D and label proposed dates. Save deferred work in OpenMates\nTasks, reusing existing entries. Resume by default; replace confused chats with\na handoff. Send workers detailed instructions with goal, context, task link, saved\nwork, scope, dependencies, required checks, checkpoint, and completion criteria;\nthe shortened table instruction is not the full assignment.\n\nGet approval before starting work. Distinguish user tasks from tasks assigned to\nOpenMates; execute only the latter. Approval covers in-focus additions and urgent\ncorrections within existing permissions and budgets, but not cancellation.\n\n### Step 4: Start or resume approved work\n\nRun **at most six worker chats concurrently**, including delegated workers but\nexcluding this meeting chat. Check existing work before every start/resume or added\nrequest; uncertain/running workers keep their slots. Put overflow in **Todo**.\n**Urgent-priority tasks may launch beyond six**: show the exception, respect platform\nlimits, and never promote a task just to bypass the cap. Approval and ownership\nrules still apply. Normal work waits until fewer than six workers remain.\n\nUse OpenMates subchats for independent assignments and supported controls to resume\nexisting chats. Give each worker its assignment and maintain one owner per task.\nVerify acceptance before retrying uncertain starts. Keep coordination in this chat.\nRecord meaningful worker updates in task activities, without heartbeat chatter.\n\n### Step 5: Monitor and handle changes\n\n- Check each started/resumed chat at **5, 10, 15, and 20 minutes**, then every\n  **20 minutes**. Use supported full AI follow-ups for scheduled checks; passive\n  reminders cannot inspect work. Preserve schedules across continuations, avoid\n  duplicates, and disclose when automatic monitoring is unavailable.\n- Compare evidence against assignments. Leave healthy work uninterrupted; correct\n  urgent drift. Honor user acceptance and scope changes.\n- Coordinate one recovery effort for shared blockers. Request user-only action\n  once, verify recovery, and continue unaffected work.\n- For repeated failures, absent progress, or disproportionate effort, recommend\n  narrowing or cancellation with evidence. Pause orchestration of that chat and\n  wait for the user's decision; continue monitoring others. Report if it remains\n  running. Do not cancel or send further continuation instructions while waiting.\n- Start added requests that fit today's approved focus and chat limit. Otherwise capture them\n  in todo/backlog. Preserve deadlines; suggest due dates only with a reason.\n  Ask before materially changing the day's focus.\n\n### Step 6: Summarize results and ask what comes next\n\nVerify outcomes and required checks; idle, blocked, and paused chats are not done.\nWhen **all chats are done**, summarize results and list still-open tasks sorted by\nrelevance to today's focus: direct outcomes, dependencies, related improvements,\nthen unrelated work. Include links, deadlines, blockers, and brief reasons; label\npartial lists. Ask **What would you like to work on next?** with a recommendation\nand relevant examples. Wait before starting another batch. If nothing remains,\nsuggest ending the day or choosing a new goal.\n\n### Step 7: Close the day\n\nAt any step, honor stop/end-of-day instructions, cancel monitoring follow-ups,\nand preserve handoffs in task activities. Paused work is not completed or cancelled.\nReassess it at the next meeting before resuming."
       }
     },
     videos_analyze_video: {

package/dist/cli.js

@@ -11,7 +11,7 @@ import {
   resolveProjectContext,
   serializeToYaml,
   shouldRequireTrustedAccountGuard
-} from "./chunk-ISGTN5LQ.js";
+} from "./chunk-KEKR6WLM.js";
 import "./chunk-IWKP55ZB.js";
 import "./chunk-BBKJZ23O.js";
 export {

package/dist/index.js

@@ -42,7 +42,7 @@ import {
   selectAssistantMessagesForSpeech,
   serializeToYaml,
   summarizeAssistantSpeech
-} from "./chunk-ISGTN5LQ.js";
+} from "./chunk-KEKR6WLM.js";
 import "./chunk-IWKP55ZB.js";
 import "./chunk-BBKJZ23O.js";
 export {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openmates",
-  "version": "0.18.0-alpha.11",
+  "version": "0.18.0-alpha.13",
   "description": "OpenMates CLI and SDK",
   "type": "module",
   "main": "dist/index.js",