openvisio-agent 0.3.4 → 0.3.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openvisio-agent",
-  "version": "0.3.4",
+  "version": "0.3.6",
   "description": "Connect your coding agent (Claude Code) to an OpenVisio team — MCP tools + optional autonomy — in one command. No shell scripts.",
   "type": "module",
   "bin": {

package/src/watch.mjs

@@ -11,10 +11,13 @@ import { join, dirname } from 'node:path'
 import { OV_DIR, readConfig, onPath, fail, ok, info, slugify, stripSlash, chmodSafe } from './lib.mjs'
 import { connectAgentWs, assertWebSocket } from './ws.mjs'
 
+// Behaviour prompts. The openvisio-team MCP bridge requires the agent's
+// credentials as ARGUMENTS on every tool call — those are injected at runtime by
+// loopBackendWs (see credNote), NOT baked in here, so nothing needs hunting.
 const CYCLE = 'Run one OpenVisio autonomy cycle.'
-const CYCLE_FAST = 'New chat activity in OpenVisio. Call poll_inbox once, then handle items in .mentions and .followUps ONLY (ignore .tasks/.claimable). Post AT MOST ONE reply per channel: if the same person sent several nudges (e.g. repeated @mentions or "status?"), answer them together in ONE post — never reply once per message. CRITICAL HONESTY RULE: your only tools are the openvisio-team chat/ticket tools. You CANNOT write code, read or clone a repo, or add entries to the API-testing/docs/sheets/flowchart tools — you have no tool for any of that. So NEVER say "On it" or "I will do it" for such work. If asked to do something you have no tool for, say plainly in one short message that you cannot do it yourself and what a human would need to do (or offer to file/track a ticket). Do not invent repo names or progress. Reply in 1-3 sentences, no summary; or react_message to dismiss. Then stop.'
-const CODE_FULL = 'Run one OpenVisio autonomy cycle. Call get_marching_orders and poll_inbox. You have file + Bash tools and a git repo at your working directory. For assigned tickets or mentions asking for real work: FIRST run "git checkout -B agent/work" to work on a branch, make the actual changes with Read/Edit/Write, run tests if present, then "git add -A && git commit -m ...". NEVER git push, merge, or touch main. Then comment_ticket with a short summary + the branch name (and move it to Done only if auto-move is on), and post a brief channel reply. If you truly cannot (missing repo/specs), say so plainly in one message — never fabricate progress or repo names.'
-const CODE_FAST = 'New chat activity in OpenVisio. Call poll_inbox, handle .mentions/.followUps ONLY, AT MOST ONE reply per channel. If a message asks for real work you can do in the git repo at your working directory, DO IT: "git checkout -B agent/work", make the changes with your file/Bash tools, commit locally (NEVER push or merge), then reply briefly with what you did + the branch name. If it needs a repo/spec you do not have, say so plainly — never fabricate progress or invent repo names. 1-3 sentences, no summary. Then stop.'
+const CYCLE_FAST = 'New chat activity in OpenVisio. If a specific mention is given above, post that reply FIRST with mcp__openvisio-team__post_message. Then call poll_inbox and handle any .followUps (thread replies you are part of, even without an @mention) — ignore .tasks/.claimable. Post AT MOST ONE reply per channel: if the same person sent several nudges, answer them together in ONE post. HONESTY: your only tools are the openvisio-team chat/ticket tools — you cannot write code or touch other tools; if asked for work you have no tool for, say so plainly in one short message (or offer to file a ticket). Never invent progress. Reply in 1-3 sentences, no summary. Then stop.'
+const CODE_FULL = 'Run one OpenVisio autonomy cycle. Call get_marching_orders and poll_inbox. You have file + Bash tools and a git repo at your working directory FOR CODE WORK ONLY. For assigned tickets or mentions asking for real code work: FIRST "git checkout -B agent/work", make the changes with Read/Edit/Write, run tests if present, then "git add -A && git commit -m ...". NEVER git push, merge, or touch main. Then comment_ticket with a short summary + the branch name, and post a brief channel reply. Do NOT use Bash to find credentials — they are given to you. If you truly cannot (missing repo/specs), say so in one message — never fabricate.'
+const CODE_FAST = 'New chat activity in OpenVisio. If a specific mention is given above, post that reply FIRST with mcp__openvisio-team__post_message — do this before any Bash. Then poll_inbox and handle .followUps (thread replies you are part of, even without an @mention), AT MOST ONE reply per channel. Only if a message asks for real CODE work in your git repo, do it on a branch (checkout -B agent/work, edit, commit locally — never push/merge) and reply with the branch name. Bash is for git/tests ONLY, never for credentials. 1-3 sentences, no summary. Then stop.'
 
 const CODE_TOOLS = ['Read', 'Grep', 'Glob', 'Edit', 'Write', 'MultiEdit', 'TodoWrite', 'Bash', 'mcp__openvisio-team__*']
 const DENY_TOOLS = ['Bash(git push:*)', 'Bash(git reset --hard:*)', 'Bash(git clean:*)', 'Bash(rm:*)', 'Bash(sudo:*)', 'Bash(chmod:*)', 'Bash(curl:*)', 'Bash(wget:*)', 'Bash(npm publish:*)', 'Bash(pnpm publish:*)', 'Bash(gh pr merge:*)', 'Bash(gh repo:*)']
@@ -154,19 +157,26 @@ function loopBackendWs({ wsUrl, apiKey, identifier, claude, mcpConfig, workdir,
 
   let busy = false
   let queued = null // 'full' | 'fast' — a cycle requested while one was running
+  let handle = null
+  let lastActivityAt = Date.now()
   // Context lines from the events themselves (the WS payload already carries the
   // channel + message / task), so the agent acts on THEM directly instead of
   // hoping poll_inbox re-surfaces the same item. Accumulated across coalesced
   // events and drained into the next cycle's prompt.
   const pending = []
 
+  // The Mastra bridge authenticates per-CALL, not per-connection: every
+  // openvisio-team tool needs agent_identifier + agent_api_key as arguments.
+  // Hand them to the model up front so it never shells around hunting for them.
+  const credNote = `AUTH: the openvisio-team (mcp__openvisio-team__*) tools REQUIRE two arguments on EVERY call — agent_identifier: "${identifier}" and agent_api_key: "${apiKey}". Include BOTH on every openvisio-team tool call (post_message, poll_inbox, react_message, comment_ticket, …). They are given to you right here: do NOT search for them, do NOT run Bash/shell/grep/cat/find, do NOT read memory — just call the tools with these exact values.`
+
   async function drain(kind, context) {
     if (context) pending.push(context)
     if (busy) { queued = (queued === 'full' || kind === 'full') ? 'full' : 'fast'; log('busy — queued a ' + kind + ' follow-up cycle'); return }
     busy = true
     const ctx = pending.splice(0) // take everything accumulated so far
     const base = kind === 'full' ? fullPrompt : fastPrompt
-    const prompt = ctx.length ? ctx.join('\n') + '\n\n' + base : base
+    const prompt = credNote + '\n\n' + (ctx.length ? ctx.join('\n') + '\n\n' : '') + base
     log('running ' + kind + ' cycle…' + (ctx.length ? ' (' + ctx.length + ' event' + (ctx.length === 1 ? '' : 's') + ')' : ''))
     try {
       await runCycle(prompt)
@@ -186,6 +196,7 @@ function loopBackendWs({ wsUrl, apiKey, identifier, claude, mcpConfig, workdir,
 
   function onEvent(k, d) {
     const raw = d && typeof d === 'object' ? d : {}
+    lastActivityAt = Date.now()
     if (k === 'task:assigned') {
       const t = raw.task || {}
       log('task:assigned ' + (t.id != null ? '#' + t.id + ' “' + (t.title || '') + '”' : ''))
@@ -198,7 +209,7 @@ function loopBackendWs({ wsUrl, apiKey, identifier, claude, mcpConfig, workdir,
       const who = senderName(msg)
       log('agent:mention in channel ' + (cid != null ? cid : '?'))
       const ctx = cid != null
-        ? `You were @mentioned in OpenVisio channel ${cid}${who ? ` by ${who}` : ''}: "${text}". Reply DIRECTLY in that channel now with post_message (channel_id ${cid}), 1-3 sentences addressing it. Do NOT depend on poll_inbox to find it — you already have it here. You MAY still call poll_inbox to catch OTHER pending items, but you MUST answer this one.`
+        ? `You were @mentioned in OpenVisio channel ${cid}${who ? ` by ${who}` : ''}: "${text}". Your FIRST action must be mcp__openvisio-team__post_message with channel_id ${cid}, a 1-3 sentence reply, and the agent_identifier + agent_api_key from the AUTH line above. You already have the message here — do NOT poll_inbox to find it. After posting, you MAY poll_inbox once for other .followUps.`
         : undefined
       void drain('fast', ctx)
     } else {
@@ -206,13 +217,24 @@ function loopBackendWs({ wsUrl, apiKey, identifier, claude, mcpConfig, workdir,
     }
   }
 
+  // Follow-up sweep: thread replies you are part of get NO @mention (no WS event
+  // fires), so poll the inbox on a slow cadence to catch .followUps — but ONLY
+  // within a short window after real activity, so an idle agent costs nothing.
+  const FOLLOWUP_MS = 60_000
+  const ACTIVE_WINDOW_MS = 5 * 60_000
+  const sweep = setInterval(() => {
+    if (busy) return
+    if (Date.now() - lastActivityAt > ACTIVE_WINDOW_MS) return // idle → don't spend a cycle
+    void drain('fast', 'Follow-up check: call poll_inbox and reply to any NEW .followUps (thread replies you are part of, even with no @mention) or unanswered .mentions. If there is nothing new, do nothing and stop — do NOT post.')
+  }, FOLLOWUP_MS)
+
   log('up — backend WS watcher on ' + wsUrl + (canCode ? ' [code: ' + workdir + ']' : ''))
-  const handle = connectAgentWs({ wsUrl, apiKey, identifier, onEvent, log })
+  handle = connectAgentWs({ wsUrl, apiKey, identifier, onEvent, log })
 
   return new Promise(() => {
     // Run until killed. Tidy up the socket on termination so a restarting
     // service doesn't leak a half-open connection.
-    const bye = () => { try { handle.close() } catch { /* noop */ } process.exit(0) }
+    const bye = () => { clearInterval(sweep); try { handle && handle.close() } catch { /* noop */ } process.exit(0) }
     process.on('SIGTERM', bye)
     process.on('SIGINT', bye)
   })

package/src/ws.mjs

@@ -95,7 +95,11 @@ export function connectAgentWs({ wsUrl, apiKey, identifier, onEvent, log }) {
 
   open()
 
-  return {
+  const api = {
+    /** Fire-and-forget send (no-op if the socket isn't open). */
+    send(obj) { try { if (ws && ws.readyState === 1) ws.send(JSON.stringify(obj)) } catch { /* closing */ } },
+    /** Show the agent as typing in a channel (docs/WEBSOCKET.md `{type:'typing'}`). */
+    sendTyping(channelId) { api.send({ type: 'typing', channel_id: channelId }) },
     close() {
       closed = true
       clearKeepalive()
@@ -103,4 +107,5 @@ export function connectAgentWs({ wsUrl, apiKey, identifier, onEvent, log }) {
       if (ws) { try { ws.close() } catch { /* already gone */ } ws = null }
     },
   }
+  return api
 }