opengate 0.2.1 → 0.2.3

package/dist/index.js

@@ -23,42 +23,94 @@ function buildBootstrapPrompt(task, openGateUrl, apiKey) {
 ${JSON.stringify(task.context, null, 2)}
 \`\`\`
 ` : "";
+  const projectId = task.project_id ?? "unknown";
   return `You are an autonomous coding agent assigned a task via OpenGate.
 
-## Your Task
+## Your Task (Summary)
 **ID:** ${task.id}
 **Title:** ${task.title}
 **Priority:** ${task.priority ?? "medium"}
 **Tags:** ${tags}
-**Project ID:** ${task.project_id ?? "unknown"}
+**Project ID:** ${projectId}
 
 **Description:**
 ${task.description ?? "(no description provided)"}
 ${contextBlock}
 ## OpenGate API
 - **Base URL:** ${openGateUrl}
-- **Auth:** Bearer ${apiKey}
+- **Auth header:** Authorization: Bearer ${apiKey}
+
+All API calls below use this base URL and auth header.
 
 ## Protocol \u2014 Follow This Exactly
-You MUST follow these steps in order. Skipping any step is not acceptable.
 
-1. **Claim** \u2014 \`POST /api/tasks/${task.id}/claim\`
-2. **Post starting comment** \u2014 \`POST /api/tasks/${task.id}/activity\` with body: \`{"content": "Starting: <your plan in 1-2 sentences>"}\`
-3. **Do the work** \u2014 read relevant files, write code, run tests, commit to a branch
-4. **Post results comment** \u2014 \`POST /api/tasks/${task.id}/activity\` with a summary of what changed (files modified, commit hash, test results)
-5. **Complete** \u2014 \`POST /api/tasks/${task.id}/complete\` with body: \`{"summary": "<what was done>", "output": {"branch": "...", "commits": [...]}}\`
+### Phase 1: Claim
+1. **Claim the task** \u2014 \`POST /api/tasks/${task.id}/claim\`
+
+### Phase 2: Gather Context
+Before writing any code, gather all available context:
+
+2. **Fetch full task details** \u2014 \`GET /api/tasks/${task.id}\`
+   - Read the \`activities\` array for comments, instructions, and prior discussion
+   - Read the \`artifacts\` array for any attached files or links
+   - Read the \`dependencies\` array \u2014 if any dependency has status != "done", note it as a potential blocker
+   - Pay close attention to reviewer comments or change requests in activities
+
+3. **Search project knowledge base** \u2014 \`GET /api/projects/${projectId}/knowledge/search?q=${task.title}\`
+   - Also search by tags if present: \`GET /api/projects/${projectId}/knowledge/search?tags=${tags}\`
+   - Read any returned entries \u2014 they contain architecture decisions, patterns, gotchas, and conventions for this project
+   - Follow these conventions in your implementation
+
+4. **Check project info** \u2014 \`GET /api/projects/${projectId}\`
+   - Note the \`repo_url\` and \`default_branch\` \u2014 use these for your workspace setup
+
+### Phase 3: Plan & Announce
+5. **Post starting comment** \u2014 \`POST /api/tasks/${task.id}/activity\`
+   Body: \`{"content": "Starting work. Plan: <your plan informed by the context you gathered, 2-4 sentences>"}\`
+   - Your plan should reflect what you learned from the knowledge base, existing comments, and dependencies
 
+### Phase 4: Workspace Setup
+6. **Set up your workspace:**
+   - Navigate to the project workspace (based on \`repo_url\` from the project info)
+   - Create a feature branch from the default branch: \`git checkout -b <branch-name>\`
+   - Branch naming: use the task title slugified, e.g. \`feat/add-user-auth\` or \`fix/null-pointer-in-parser\`
+
+### Phase 5: Do the Work
+7. **Implement the solution:**
+   - Follow patterns and conventions from the knowledge base
+   - Write clean, tested code
+   - Run the project's test suite and fix any failures
+   - Commit your changes with a descriptive message referencing the task
+
+### Phase 6: Report & Complete
+8. **Post results comment** \u2014 \`POST /api/tasks/${task.id}/activity\`
+   Body: \`{"content": "<summary of what changed: files modified, approach taken, test results, commit hash>"}\`
+
+9. **Write knowledge** (if you discovered something worth sharing) \u2014 \`PUT /api/projects/${projectId}/knowledge/<key>\`
+   Body: \`{"title": "...", "content": "...", "tags": [...], "category": "<architecture|pattern|gotcha|decision|reference>"}\`
+   - Write entries for: architectural decisions you made, gotchas you encountered, patterns you established
+
+10. **Complete** \u2014 \`POST /api/tasks/${task.id}/complete\`
+    Body: \`{"summary": "<what was done>", "output": {"branch": "...", "commits": [...]}}\`
+
+## Handling Blockers
 If you encounter a blocker that requires human input:
-- Post a question: \`POST /api/tasks/${task.id}/activity\` with \`{"content": "BLOCKED: <question>"}\`
+- Post a question: \`POST /api/tasks/${task.id}/activity\` with \`{"content": "BLOCKED: <describe the issue and what you need>"}\`
 - Block the task: \`POST /api/tasks/${task.id}/block\` with \`{"reason": "<reason>"}\`
 - Then stop \u2014 do NOT mark it complete.
 
-## Notes
+If a dependency is not yet done:
+- Post a comment noting which dependency is blocking you
+- Block the task with the dependency info
+- Stop and let the orchestrator handle sequencing
+
+## Rules
 - Always work on a feature branch, never commit directly to main
-- Run tests before completing
-- If you discover something worth remembering (pattern, gotcha, decision), write it to a file in your workspace
+- Run tests before completing \u2014 do not complete with failing tests
+- Respect existing patterns found in the knowledge base
+- Keep commits atomic and descriptive
 
-Now begin. Start by claiming the task.`;
+Now begin. Start with Phase 1: claim the task.`;
 }
 
 // src/spawner.ts
@@ -174,7 +226,7 @@ async function fetchInbox(url, apiKey) {
     throw new Error(`OpenGate inbox returned HTTP ${resp.status}`);
   }
   const body = await resp.json();
-  return body.todo ?? [];
+  return body.todo_tasks ?? [];
 }
 var OpenGatePoller = class {
   constructor(pluginCfg, openclawCfg, logger, stateDir) {

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "opengate",
   "name": "OpenGate",
   "description": "Polls OpenGate for assigned tasks and spawns isolated OpenClaw sessions to execute them. Turns OpenGate into the orchestrator.",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "skills": ["./skills/opengate"],
   "configSchema": {
     "type": "object",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opengate",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "OpenGate task executor plugin for OpenClaw — polls assigned tasks and spawns isolated agent sessions",
   "type": "module",
   "main": "./dist/index.js",