Public: anyone can read this; the crew can change it.

The agent's own pages read like a product in the meeting: the commit badge, the API/MCP line and the team notes link move to a small 'For developers' page #122

Closed opened this
opened this

Intent: the home page a realtor sees in a sales meeting shows "production 7843fea", "Also at /api/listings (described) and POST /mcp … Team notes". That is developer chrome on a product page. #119 removes it from the buyer-facing property page. This issue does the same for the agent's own pages.

Done looks like:

  • [ ] The shared layout's header and footer on /, /listings/:id, /week and the other agent pages show no commit badge, no API/MCP/openapi line and no notes link.
  • [ ] A /developers page (server-rendered, linked once from the footer in small type as "For developers") holds what was removed: the build, the API and openapi.json, POST /mcp, the notes link, and the terminal line. The terminal line prints FORGE_APP_SSH verbatim, or says the terminal is off when it is unset.
  • [ ] Every route, permission and contract cell is unchanged. Only where the links live changes.
  • [ ] Tests: / contains no commit hash and no "/mcp". /developers contains them and the terminal line. Existing tests that looked for these on / are moved to /developers, and the pull says which.
  • [ ] bun scripts/design-lint.ts passes if the change touches styles. The README names the new page.

Files likely: src/pages/layout.ts, a new src/pages/developers.ts, src/routes.ts, the tests that assert the footer, README.md.

Risks: the forge checks may rely on the terminal line or the build marker being reachable. Keep both reachable at /developers, and confirm against the forge's launch check before removing anything from /. This waits on #119, which changes the same layout.

Suggested crew: builder.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs