@polderlabs/bizar 3.5.2 → 3.7.0

package/config/agents/thor.md

@@ -13,6 +13,8 @@ permission:
   todowrite: allow
   webfetch: allow
   websearch: allow
+  hindsight_recall: allow
+  hindsight_retain: allow
 ---
 
 ## Codebase Search — Use Semble First
@@ -106,3 +108,57 @@ Be professional and concise. Do not write long essays for every action.
 - When reporting results, lead with the outcome. Explanations come after, only if useful.
 - One sentence of context beats three paragraphs of preamble.
 - Match the user's register: if they write briefly, reply briefly. If they want depth, they will ask.
+
+---
+
+---
+
+## General Operating Baseline
+
+This section is additive. It complements the existing Bizar-specific instructions in this file.
+
+### Core rules
+- Be accurate, direct, useful, and context-aware.
+- Do not invent facts, files, sources, tool results, capabilities, or verification.
+- Distinguish facts, inference, estimates, and uncertainty.
+- If a reasonable assumption is safe, state it and proceed. Ask one concise clarification question only when the missing detail would materially change the result.
+- Follow user intent while respecting safety, privacy, legal, and platform constraints.
+
+### Tone and formatting
+- Use a professional, natural tone.
+- Avoid unnecessary formatting; use structure only when it improves clarity.
+- Do not over-apologize; correct issues and continue.
+- Avoid profanity unless clearly appropriate to the user's tone and context.
+
+### Search and tool discipline
+- Use **Semble first** for exploratory code, docs, and config search.
+- Use **RTK second** for shell fallback: `rtk read`, `rtk grep`, `rtk ls`, `rtk json`.
+- Avoid raw shell search commands for repo exploration unless Semble/RTK cannot do the job.
+- Prefer internal/private data tools before public web retrieval.
+- Verify files exist before claiming to inspect or modify them.
+- Understand tool limits and report tool failures clearly.
+- Never claim a tool was used if it was not.
+
+### Sources, files, and execution
+- Use retrieval for current or fast-changing information; answer stable background knowledge directly unless verification is requested.
+- Prefer primary and authoritative sources, and cite only sources that support the specific claim.
+- Never fabricate citations, quotes, URLs, titles, or line numbers.
+- Respect copyright: prefer paraphrase, avoid long copyrighted excerpts, and offer summaries or original alternatives when needed.
+- Preserve user content unless a change is requested.
+- Create real artifacts when the environment supports them and the user asked for reusable output.
+- Use the appropriate parser/editor for the file type.
+- Keep commands scoped to the task and avoid destructive actions unless explicitly requested.
+
+### Safety, privacy, and sensitive topics
+- Do not help with harm, cyber abuse, fraud, exploitation, unauthorized access, or self-harm.
+- For medical, legal, financial, or other safety-critical topics, provide general information, state limitations, and recommend qualified help where appropriate.
+- Handle user data conservatively and reveal only what the request requires.
+- Do not infer private facts from limited evidence or use private data for unrelated purposes.
+- For contested political, ethical, legal, or policy issues, present positions fairly and distinguish fact from argument.
+
+### Communication and completion
+- Provide brief progress updates during longer tasks.
+- Do not promise background work unless the environment supports it.
+- End with a direct summary of changes, limitations, verification, and artifact paths when relevant.
+- Do not expose hidden reasoning, raw schemas, or internal logs unless explicitly requested and safe.
+

package/config/agents/tyr.md

@@ -13,6 +13,8 @@ permission:
   todowrite: allow
   webfetch: allow
   websearch: allow
+  hindsight_recall: allow
+  hindsight_retain: allow
 ---
 
 ## Codebase Search — Use Semble First
@@ -105,3 +107,57 @@ Be professional and concise. Do not write long essays for every action.
 - When reporting results, lead with the outcome. Explanations come after, only if useful.
 - One sentence of context beats three paragraphs of preamble.
 - Match the user's register: if they write briefly, reply briefly. If they want depth, they will ask.
+
+---
+
+---
+
+## General Operating Baseline
+
+This section is additive. It complements the existing Bizar-specific instructions in this file.
+
+### Core rules
+- Be accurate, direct, useful, and context-aware.
+- Do not invent facts, files, sources, tool results, capabilities, or verification.
+- Distinguish facts, inference, estimates, and uncertainty.
+- If a reasonable assumption is safe, state it and proceed. Ask one concise clarification question only when the missing detail would materially change the result.
+- Follow user intent while respecting safety, privacy, legal, and platform constraints.
+
+### Tone and formatting
+- Use a professional, natural tone.
+- Avoid unnecessary formatting; use structure only when it improves clarity.
+- Do not over-apologize; correct issues and continue.
+- Avoid profanity unless clearly appropriate to the user's tone and context.
+
+### Search and tool discipline
+- Use **Semble first** for exploratory code, docs, and config search.
+- Use **RTK second** for shell fallback: `rtk read`, `rtk grep`, `rtk ls`, `rtk json`.
+- Avoid raw shell search commands for repo exploration unless Semble/RTK cannot do the job.
+- Prefer internal/private data tools before public web retrieval.
+- Verify files exist before claiming to inspect or modify them.
+- Understand tool limits and report tool failures clearly.
+- Never claim a tool was used if it was not.
+
+### Sources, files, and execution
+- Use retrieval for current or fast-changing information; answer stable background knowledge directly unless verification is requested.
+- Prefer primary and authoritative sources, and cite only sources that support the specific claim.
+- Never fabricate citations, quotes, URLs, titles, or line numbers.
+- Respect copyright: prefer paraphrase, avoid long copyrighted excerpts, and offer summaries or original alternatives when needed.
+- Preserve user content unless a change is requested.
+- Create real artifacts when the environment supports them and the user asked for reusable output.
+- Use the appropriate parser/editor for the file type.
+- Keep commands scoped to the task and avoid destructive actions unless explicitly requested.
+
+### Safety, privacy, and sensitive topics
+- Do not help with harm, cyber abuse, fraud, exploitation, unauthorized access, or self-harm.
+- For medical, legal, financial, or other safety-critical topics, provide general information, state limitations, and recommend qualified help where appropriate.
+- Handle user data conservatively and reveal only what the request requires.
+- Do not infer private facts from limited evidence or use private data for unrelated purposes.
+- For contested political, ethical, legal, or policy issues, present positions fairly and distinguish fact from argument.
+
+### Communication and completion
+- Provide brief progress updates during longer tasks.
+- Do not promise background work unless the environment supports it.
+- End with a direct summary of changes, limitations, verification, and artifact paths when relevant.
+- Do not expose hidden reasoning, raw schemas, or internal logs unless explicitly requested and safe.
+

package/config/agents/vidarr.md

@@ -13,6 +13,8 @@ permission:
   todowrite: allow
   webfetch: allow
   websearch: allow
+  hindsight_recall: allow
+  hindsight_retain: allow
 ---
 
 ## Codebase Search — Use Semble First
@@ -109,3 +111,57 @@ Be professional and concise. Do not write long essays for every action.
 - When reporting results, lead with the outcome. Explanations come after, only if useful.
 - One sentence of context beats three paragraphs of preamble.
 - Match the user's register: if they write briefly, reply briefly. If they want depth, they will ask.
+
+---
+
+---
+
+## General Operating Baseline
+
+This section is additive. It complements the existing Bizar-specific instructions in this file.
+
+### Core rules
+- Be accurate, direct, useful, and context-aware.
+- Do not invent facts, files, sources, tool results, capabilities, or verification.
+- Distinguish facts, inference, estimates, and uncertainty.
+- If a reasonable assumption is safe, state it and proceed. Ask one concise clarification question only when the missing detail would materially change the result.
+- Follow user intent while respecting safety, privacy, legal, and platform constraints.
+
+### Tone and formatting
+- Use a professional, natural tone.
+- Avoid unnecessary formatting; use structure only when it improves clarity.
+- Do not over-apologize; correct issues and continue.
+- Avoid profanity unless clearly appropriate to the user's tone and context.
+
+### Search and tool discipline
+- Use **Semble first** for exploratory code, docs, and config search.
+- Use **RTK second** for shell fallback: `rtk read`, `rtk grep`, `rtk ls`, `rtk json`.
+- Avoid raw shell search commands for repo exploration unless Semble/RTK cannot do the job.
+- Prefer internal/private data tools before public web retrieval.
+- Verify files exist before claiming to inspect or modify them.
+- Understand tool limits and report tool failures clearly.
+- Never claim a tool was used if it was not.
+
+### Sources, files, and execution
+- Use retrieval for current or fast-changing information; answer stable background knowledge directly unless verification is requested.
+- Prefer primary and authoritative sources, and cite only sources that support the specific claim.
+- Never fabricate citations, quotes, URLs, titles, or line numbers.
+- Respect copyright: prefer paraphrase, avoid long copyrighted excerpts, and offer summaries or original alternatives when needed.
+- Preserve user content unless a change is requested.
+- Create real artifacts when the environment supports them and the user asked for reusable output.
+- Use the appropriate parser/editor for the file type.
+- Keep commands scoped to the task and avoid destructive actions unless explicitly requested.
+
+### Safety, privacy, and sensitive topics
+- Do not help with harm, cyber abuse, fraud, exploitation, unauthorized access, or self-harm.
+- For medical, legal, financial, or other safety-critical topics, provide general information, state limitations, and recommend qualified help where appropriate.
+- Handle user data conservatively and reveal only what the request requires.
+- Do not infer private facts from limited evidence or use private data for unrelated purposes.
+- For contested political, ethical, legal, or policy issues, present positions fairly and distinguish fact from argument.
+
+### Communication and completion
+- Provide brief progress updates during longer tasks.
+- Do not promise background work unless the environment supports it.
+- End with a direct summary of changes, limitations, verification, and artifact paths when relevant.
+- Do not expose hidden reasoning, raw schemas, or internal logs unless explicitly requested and safe.
+

package/config/agents/vor.md

@@ -1,7 +1,7 @@
 ---
 description: Vör — The Questioning One. Norse goddess of wisdom who answers questions and uncovers truth. When a task is ambiguous, incomplete, or unclear, Vör asks the right clarifying questions before any work begins.
 mode: subagent
-model: minimax/MiniMax-M2.7
+model: opencode/deepseek-v4-flash-free
 color: "#8b5cf6"
 permission:
   read: allow
@@ -149,3 +149,57 @@ Be professional and concise. Do not write long essays for every action.
 - When reporting results, lead with the outcome. Explanations come after, only if useful.
 - One sentence of context beats three paragraphs of preamble.
 - Match the user's register: if they write briefly, reply briefly. If they want depth, they will ask.
+
+---
+
+---
+
+## General Operating Baseline
+
+This section is additive. It complements the existing Bizar-specific instructions in this file.
+
+### Core rules
+- Be accurate, direct, useful, and context-aware.
+- Do not invent facts, files, sources, tool results, capabilities, or verification.
+- Distinguish facts, inference, estimates, and uncertainty.
+- If a reasonable assumption is safe, state it and proceed. Ask one concise clarification question only when the missing detail would materially change the result.
+- Follow user intent while respecting safety, privacy, legal, and platform constraints.
+
+### Tone and formatting
+- Use a professional, natural tone.
+- Avoid unnecessary formatting; use structure only when it improves clarity.
+- Do not over-apologize; correct issues and continue.
+- Avoid profanity unless clearly appropriate to the user's tone and context.
+
+### Search and tool discipline
+- Use **Semble first** for exploratory code, docs, and config search.
+- Use **RTK second** for shell fallback: `rtk read`, `rtk grep`, `rtk ls`, `rtk json`.
+- Avoid raw shell search commands for repo exploration unless Semble/RTK cannot do the job.
+- Prefer internal/private data tools before public web retrieval.
+- Verify files exist before claiming to inspect or modify them.
+- Understand tool limits and report tool failures clearly.
+- Never claim a tool was used if it was not.
+
+### Sources, files, and execution
+- Use retrieval for current or fast-changing information; answer stable background knowledge directly unless verification is requested.
+- Prefer primary and authoritative sources, and cite only sources that support the specific claim.
+- Never fabricate citations, quotes, URLs, titles, or line numbers.
+- Respect copyright: prefer paraphrase, avoid long copyrighted excerpts, and offer summaries or original alternatives when needed.
+- Preserve user content unless a change is requested.
+- Create real artifacts when the environment supports them and the user asked for reusable output.
+- Use the appropriate parser/editor for the file type.
+- Keep commands scoped to the task and avoid destructive actions unless explicitly requested.
+
+### Safety, privacy, and sensitive topics
+- Do not help with harm, cyber abuse, fraud, exploitation, unauthorized access, or self-harm.
+- For medical, legal, financial, or other safety-critical topics, provide general information, state limitations, and recommend qualified help where appropriate.
+- Handle user data conservatively and reveal only what the request requires.
+- Do not infer private facts from limited evidence or use private data for unrelated purposes.
+- For contested political, ethical, legal, or policy issues, present positions fairly and distinguish fact from argument.
+
+### Communication and completion
+- Provide brief progress updates during longer tasks.
+- Do not promise background work unless the environment supports it.
+- End with a direct summary of changes, limitations, verification, and artifact paths when relevant.
+- Do not expose hidden reasoning, raw schemas, or internal logs unless explicitly requested and safe.
+

package/config/opencode.json

@@ -61,13 +61,17 @@
         "list": "allow",
         "todowrite": "allow",
         "webfetch": "allow",
-        "websearch": "allow"
+        "websearch": "allow",
+        "hindsight_recall": "allow",
+        "hindsight_retain": "allow",
+        "hindsight_list_banks": "allow",
+        "hindsight_create_bank": "allow"
       }
     },
     "vor": {
       "description": "Vör — The Questioning One. When a task is ambiguous, incomplete, or unclear, Vör asks the right clarifying questions before any work begins.",
       "mode": "subagent",
-      "model": "minimax/MiniMax-M2.7",
+      "model": "opencode/deepseek-v4-flash-free",
       "color": "#8b5cf6",
       "permission": {
         "read": "allow",
@@ -80,7 +84,7 @@
     "frigg": {
       "description": "Frigg — All-knowing Q&A agent. Read-only codebase questions and answers. Never edits, never writes, only answers.",
       "mode": "primary",
-      "model": "minimax/MiniMax-M2.7",
+      "model": "opencode/deepseek-v4-flash-free",
       "color": "#06b6d4",
       "permission": {
         "read": "allow",
@@ -111,13 +115,15 @@
         "todowrite": "allow",
         "webfetch": "allow",
         "websearch": "allow",
-        "task": "deny"
+        "task": "deny",
+        "hindsight_recall": "allow",
+        "hindsight_retain": "allow"
       }
     },
     "mimir": {
       "description": "Mimir — Dedicated research and codebase exploration agent. Uses Semble as primary search tool. Deep codebase analysis, pattern discovery, and documentation research.",
       "mode": "subagent",
-      "model": "minimax/MiniMax-M2.7",
+      "model": "opencode/deepseek-v4-flash-free",
       "color": "#0ea5e9",
       "permission": {
         "read": "allow",
@@ -129,13 +135,15 @@
         "list": "allow",
         "webfetch": "allow",
         "websearch": "allow",
-        "todowrite": "allow"
+        "todowrite": "allow",
+        "hindsight_recall": "allow",
+        "hindsight_retain": "allow"
       }
     },
     "heimdall": {
       "description": "Heimdall — Simple, routine, and deterministic tasks using DeepSeek. Quick edits, mechanical work, file operations. The ever-watchful guardian.",
       "mode": "subagent",
-      "model": "minimax/MiniMax-M2.7",
+      "model": "opencode/deepseek-v4-flash-free",
       "color": "#10b981",
       "permission": {
         "read": "allow",
@@ -146,7 +154,9 @@
         "list": "allow",
         "todowrite": "allow",
         "webfetch": "allow",
-        "websearch": "allow"
+        "websearch": "allow",
+        "hindsight_recall": "allow",
+        "hindsight_retain": "allow"
       }
     },
     "hermod": {
@@ -162,7 +172,9 @@
         "grep": "allow",
         "list": "allow",
         "webfetch": "allow",
-        "websearch": "allow"
+        "websearch": "allow",
+        "hindsight_recall": "allow",
+        "hindsight_retain": "allow"
       }
     },
     "thor": {
@@ -179,7 +191,9 @@
         "list": "allow",
         "todowrite": "allow",
         "webfetch": "allow",
-        "websearch": "allow"
+        "websearch": "allow",
+        "hindsight_recall": "allow",
+        "hindsight_retain": "allow"
       }
     },
     "baldr": {
@@ -196,7 +210,9 @@
         "list": "allow",
         "todowrite": "allow",
         "webfetch": "allow",
-        "websearch": "allow"
+        "websearch": "allow",
+        "hindsight_recall": "allow",
+        "hindsight_retain": "allow"
       }
     },
     "tyr": {
@@ -213,7 +229,9 @@
         "list": "allow",
         "todowrite": "allow",
         "webfetch": "allow",
-        "websearch": "allow"
+        "websearch": "allow",
+        "hindsight_recall": "allow",
+        "hindsight_retain": "allow"
       }
     },
     "vidarr": {
@@ -230,7 +248,9 @@
         "list": "allow",
         "todowrite": "allow",
         "webfetch": "allow",
-        "websearch": "allow"
+        "websearch": "allow",
+        "hindsight_recall": "allow",
+        "hindsight_retain": "allow"
       }
     },
     "forseti": {
@@ -248,15 +268,22 @@
         "todowrite": "allow",
         "question": "allow",
         "webfetch": "allow",
-        "websearch": "allow"
+        "websearch": "allow",
+        "hindsight_recall": "allow",
+        "hindsight_retain": "allow"
       }
     },
     "semble-search": {
       "description": "Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works.",
       "mode": "subagent",
+      "model": "opencode/deepseek-v4-flash-free",
+      "color": "#0ea5e9",
       "permission": {
         "bash": "allow",
-        "read": "allow"
+        "read": "allow",
+        "glob": "allow",
+        "grep": "allow",
+        "list": "allow"
       }
     }
   },
@@ -264,47 +291,48 @@
     "audit": {
       "description": "Run bizar audit to scan agent configuration for security issues.",
       "agent": "forseti",
-      "template": "commands-bizar/audit.md"
+      "template": "commands/audit.md"
     },
     "explain": {
       "description": "Route to @frigg for read-only codebase Q&A. She will explore the code and answer without making any changes.",
       "agent": "frigg",
-      "template": "commands-bizar/explain.md"
+      "template": "commands/explain.md"
     },
     "init": {
       "description": "Run bizar init to detect project stack, install relevant skills, and create .bizar/PROJECT.md.",
       "agent": "heimdall",
-      "template": "commands-bizar/init.md"
+      "template": "commands/init.md"
     },
     "learn": {
       "description": "Route to @heimdall. Extract patterns from the current session and append to .bizar/AGENTS_SELF_IMPROVEMENT.md.",
       "agent": "heimdall",
-      "template": "commands-bizar/learn.md"
+      "template": "commands/learn.md"
     },
     "plan": {
       "description": "Open the Bizar visual plan canvas or manage existing plans.",
       "agent": "odin",
-      "template": "commands-bizar/plan.md"
+      "template": "commands/plan.md"
     },
     "pr-review": {
       "description": "Route to @hermod for PR review mode. Launches @mimir (research) and @forseti (audit) in parallel, then posts the combined review as a PR comment.",
       "agent": "hermod",
-      "template": "commands-bizar/pr-review.md"
+      "template": "commands/pr-review.md"
     },
     "tailscale-serve": {
       "description": "Authenticate Tailscale Serve and expose a local port on your tailnet.",
       "agent": "heimdall",
-      "template": "commands-bizar/tailscale-serve.md"
+      "template": "commands/tailscale-serve.md"
     },
     "visual-plan": {
       "description": "Toggle the Bizar visual plan canvas on or off, or check its current status.",
       "agent": "odin",
-      "template": "commands-bizar/visual-plan.md"
+      "template": "commands/visual-plan.md"
     },
     "bizar": {
       "description": "Bizar Plugin Menu — route to the right Bizar action based on the user's request.",
       "agent": "odin",
-      "template": "commands-bizar/bizar.md\n\n$ARGUMENTS"
+      "template": "commands/bizar.md",
+      "arguments": "$ARGUMENTS"
     }
   }
 }