Skip to content

Add steward to the per-agent AGENTS map (8627/9627) - #22

Merged
TadMSTR merged 1 commit into
mainfrom
feat/steward-agent-instance
Aug 18, 2026
Merged

TadMSTR merged 1 commit into
mainfrom
feat/steward-agent-instance

Conversation

@TadMSTR

@TadMSTR TadMSTR commented Aug 18, 2026

Copy link
Copy Markdown
Owner

One row in the AGENTS map. Companion to host-forge/scripts#44.

steward is forge's config-owning agent (vikunja#350) — the sole proposer of changes to the root-owned config surface. Its git job is deliberately narrow: branch, commit, push, open a PR on host-forge-scripts carrying a config proposal. It holds no merge, release, tag or publish verb, enforced by a tool_allowlist in steward-agent.yml rather than a denylist, so a future githost-mcp release cannot add a write verb steward silently inherits.

Why this PR exists at all: this map is a registration list the steward build plan did not account for. The plan grants steward githost-mcp but never provisions an instance, and githost-mcp runs one process per agent keyed here. Without this row there is no port for steward's manifest to point at.

Port choice. 8627/9627 rather than the contiguous 8626, which is backrest-mcp. 8625/9625 stay reserved to harlock rather than being reclaimed — that decommission (vikunja#270) is only through Phase 0, and reassigning a port out from under a half-removed agent is how two services end up racing for one bind. Renumber both together when it finishes.

Noted while here, not fixed here: buildApp() overwrites any per-agent GITHOST_MCP_AUTH_TOKEN with the shared value from ~/.secrets/forge.env (line 68), so all agents present the same githost token and identity is separated by port only. The header comment above says the per-agent env file may carry "any agent-specific token overrides", which is not true of this key. That matters more for steward than for the others, since steward's whole premise is an isolated identity — filing separately rather than widening this PR.

node --check passes. Deploy is pm2 start ecosystem.config.js --only githost-mcp-steward after ~/.secrets/githost-mcp-steward.env is in place (already written).

🤖 Generated with Claude Code

steward is the config-owning agent (vikunja#350, build
steward-config-agent-2026-08). Its git job is narrow by design: branch, commit,
push and open a PR on host-forge-scripts carrying a config proposal. It holds no
merge, release, tag or publish verb — enforced by a tool_allowlist in
steward-agent.yml rather than a denylist, so a future githost-mcp release cannot
add a write verb steward silently inherits.

This map is a registration list the steward build plan did not account for: the
plan grants steward githost-mcp but never provisions an instance, and githost-mcp
runs one process per agent keyed here. Without this row there is no port for
steward's manifest to point at.

8627/9627 rather than the contiguous 8626, which is backrest-mcp. 8625/9625 stay
reserved to harlock rather than being reclaimed: that decommission (vikunja#270)
is only through Phase 0, and reassigning a port out from under a half-removed
agent is how two services end up racing for one bind.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

agent-id: sysadmin
@TadMSTR
TadMSTR merged commit 710af61 into main Aug 18, 2026
3 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