Skip to content

Feat/goal and rea mcp - #34

Merged
AlleyBo55 merged 2 commits into
masterfrom
feat/goal-and-rea-mcp
Nov 2, 2026
Merged

AlleyBo55 merged 2 commits into
masterfrom
feat/goal-and-rea-mcp

Conversation

@AlleyBo55

Copy link
Copy Markdown
Owner

No description provided.

goreleaser builds release notes from commit subjects, so a release with one
commit renders as a single line. The header carries the install command, the
zero-config local-model path, and a link to the full notes.
Two features, plus the protocol fix the REA integration surfaced.

/goal: a persistent, budget-capped objective that drives the agent across
turns until done, blocked, or paused. New internal/goal package (Tracker:
objective, token budget, statuses, JSON persistence, per-turn DrivePrompt
injection, auto-pause on budget). Wired into the REPL as /goal with
set/status/pause/resume/done/blocked/clear and per-turn token accounting.

REA: gocode drives an installed REA (Reverse Engineer Anything) over MCP.
New internal/rea package detects scripts/rea.mjs and a node satisfying REA's
engine range; 'gocode rea setup' registers it in .gocode/mcp.json and
'gocode rea status' verifies the live handshake (234 tools discovered).

Protocol fix: the MCP client only spoke LSP-style Content-Length framing,
but REA's stdio transport is newline-delimited JSON (the MCP stdio
standard), so a naive config hung. Added an additive per-server 'Framing'
field: empty keeps Content-Length unchanged for existing servers, 'ndjson'
serves REA. Verified by new in-memory-pipe tests covering both framings.
@AlleyBo55
AlleyBo55 merged commit 7a981a9 into master Nov 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant