[P0] Surface build_stream output to diagnose BUILD_FAILED #2
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Gap
redeploy_projectandcreate_projectcallbuild_streamfire-and-forget and discard the response. When a build ends in BUILD_FAILED, there is no way to see why.Container Manager equivalent
The UI shows the live build log during project build/create.
Suggested approach
build_streamis a streaming (SSE) endpoint — the build log is almost certainly contained in the stream that the connector currently discards. Instead of fire-and-forget, read the stream and capture the build output. On BUILD_FAILED, return the relevant log lines so the failure reason is visible. Must respect the ~4 min Claude Desktop tool-call limit — consider bounding capture by size/time, or a separateget_project_build_logtool.Reverse-engineering effort
Medium — investigate the build_stream SSE payload format.
Priority
P0 — during live testing we were repeatedly blind on BUILD_FAILED and had to guess.