You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Task results are dropped: sidecar's /task-result callback has no platform route #43
backend/agent-runtime/server.py:116 POSTs every completed task to {PLATFORM_GATEWAY_URL}/task-result with the agent's bearer token. backend/app/routers/gateway.py has no such route, so the call 404s. The sidecar doesn't check the response, so the failure is silent.
The only copy of a result is the sidecar's in-memory _state["last_result"]. It holds only the latest task and is lost on container restart. Nobody can see what an AI employee actually did: not the UI, not the PR watcher, not someone debugging a review that never posted.
Why it went unnoticed
The sidecar and the platform are each tested in isolation, mocking the other side (tests/test_agent_runtime.py:174: # Patch the platform callback too). Nothing asserted that the sidecar's callback URL is a real platform route.
Evidence
A contract test on branch fix/task-result-callback (backend/tests/test_task_result_contract.py) captures the exact request the sidecar emits and replays it against the platform app:
AssertionError: sidecar POSTs task results to /gateway/task-result, but the platform has no such route
assert 404 != 404
Activity