Wagalo v0.3.0

Wagalo v0.3.0

Wagalo 0.3.0 makes local agent research finite, inspectable, and easier for constrained models to use. A new focused MCP profile exposes three clear tools—search, fetch, and research—while the existing research and action profiles retain all 29 tool names and capabilities.

Research runs now carry a durable run ID, explicit requirements, evidence ledgers, search and fetch budgets, unresolved facts, possible contradiction candidates, and a recorded stop reason. Repeated equivalent queries and unchanged URLs reuse earlier evidence within a run unless the caller explicitly requests a refresh. Bounded research stops when its requirements are resolved, results saturate, its budget is exhausted, or its deadline is reached.

For desktop clients, WAGALO_MCP_MODE=embedded runs the MCP server directly over stdio without requiring the HTTP daemon. Proxy stdio remains the default, and the daemon, Research Desk, HTTP transports, watches, jobs, security controls, provider choices, and action tools remain available.

The Research Desk now shows agent research runs with budgets, unresolved requirements, stop reasons, and evidence details. Focused initialization instructions are shorter and include explicit stop and resume guidance for models with limited context.

Configure focused embedded stdio

Set the MCP command to an absolute node.exe path, pass the absolute bin/wagalo-mcp.mjs path, use the Wagalo repository as cwd, and set:

WAGALO_MCP_MODE=embedded
WAGALO_PROFILE=focused

Existing proxy configurations continue to work without these changes.

Verification

• 95 core tests and 204 sandbox tests passed locally.
• TypeScript checking, the development build, package dry run, dependency audit, current-tree secret scan, and security checks passed.
• Official MCP SDK protocol checks passed for proxy stdio, Streamable HTTP, and embedded focused stdio.
• Native Windows CI, Windows and Ubuntu tests, security matrices, and the optional ColBERT job passed on the release candidate.
• The deterministic DSH fixture completed in 22 ms with one search, three fetches, four total tool calls, all requirements resolved, and the requirements_resolved stop reason.

The deterministic fixture validates convergence and response shape; it is not a live DSH model-quality claim. A credential from older public history remains documented in GAP.md and still requires issuer-side rotation. Windows setup artifacts are unsigned.