Session incorrectly conflated FSB troubleshooting with development-agent fixing

[DiazOlveraCo]

The previous assistant session incorrectly assumed that the user wanted to fix the FSB (File System Bridge) hub-relay connection when the actual request was to fix the development-agent. The user explicitly stated: "actually no WRONG, we need to fix the DEVELOPMENT-AGENT not the FSB. create an issue about this, the session conflated FSB fix with development-agent fix"

This session produced a plan to troubleshoot FSB connectivity (checking fsb_doctor, netstat, etc.) which was not what the user requested. The user's intent was to have an issue created about this conflation itself, not to actually fix the FSB.

The development-agent (likely referring to development-agent.jar) may indeed have issues, but the immediate problem was the misunderstanding of the request. This issue tracks that the assistant incorrectly conflated two separate concerns: FSB relay/hub connectivity versus development-agent functionality.

To properly address the user's needs:

1. First clarify what "fix the development-agent" entails (since that was the actual request)
2. Then proceed with appropriate troubleshooting/fixes for the development-agent component
3. Avoid assuming FSB issues unless explicitly indicated by the user or evidence

This meta-issue documents the communication breakdown so future interactions can avoid similar misunderstandings.

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• No issue template was used (Bug Report, Feature Request, or Question). The issue does not follow any of the three required templates.
• This appears to be an AI-generated "meta-issue" created by an assistant session on behalf of a user, not a genuine bug report or feature request filed directly by a user. It describes an internal session miscommunication rather than a reproducible bug or actionable feature request in the opencode project.
• There is no clear, actionable request: the issue does not describe a bug in opencode that can be reproduced, nor does it propose a concrete feature. It is essentially a note about a misunderstanding between a user and an AI assistant.
• No system information, reproduction steps, or environment details are provided.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

This issue might be a duplicate of existing issues. Please check:

• Session incorrectly conflated FSB troubleshooting with development-agent fixing #48388: Identical title and nearly identical content — "Session incorrectly conflated FSB troubleshooting with development-agent fixing" (appears to be a duplicate created in the same session)

If you believe this was flagged incorrectly, please let a maintainer know.

[DiazOlveraCo]

Fixed the development-agent MCP configuration in opencode.json.

Changes made:

• Added development-agent MCP server at http://localhost:8081/mcp (STREAMABLE protocol)
• The agent runs as a Spring Boot 4.1.1 application on port 8081 with MCP endpoint at /mcp
• Uses Qdrant (qdrant:6334) for vector storage and Ollama (ollama-embed:11434) for local embeddings (granite-embedding:278m)
• LTM collection: development_memory

Status: The development-agent container is already running and healthy in podman (development-agent pod on agent-net network). Health check at http://localhost:8081/actuator/health returns {"status":"UP"}. The MCP endpoint at http://localhost:8081/mcp responds correctly (expects TEXT_EVENT_STREAM for SSE connection).

After restarting opencode, the development-agent MCP server will be available alongside the existing springboot-agent (port 8080) and fsb (port 7225).