Christian Gick 17b92f8514 fix(mcp-bridge): unique wire ids to avoid concurrent session collisions ...

LiteLLM opens a fresh MCP session per tool call. Two concurrent sessions
both send id=1 (tools/list + tools/call) which overwrite each other in
the shared pending-map keyed by the inbound id. One of the two calls
never gets a response and times out.

Assign a monotonic demux-N wire id per forwardMcpCall. The caller's
original id is echoed back in the HTTP response by the route handler.

SB-48

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-04-14 09:30:26 +03:00

.gitea/workflows

ci: add Gitea Actions build & deploy workflow

2026-04-10 23:11:19 +03:00

src

fix(mcp-bridge): unique wire ids to avoid concurrent session collisions

2026-04-14 09:30:26 +03:00

.env.example

feat(agiliton-account): per-customer LiteLLM MCP server provisioning

2026-04-10 16:18:02 +03:00

.gitignore

feat(agiliton-account): Phase 1 service scaffold

2026-04-10 16:06:16 +03:00

docker-compose.yml

fix(deploy): correct docker-compose networks to match infra VM

2026-04-10 16:09:13 +03:00

Dockerfile

feat(agiliton-account): Phase 1 service scaffold

2026-04-10 16:06:16 +03:00

package-lock.json

feat(agiliton-account): Phase 1 service scaffold

2026-04-10 16:06:16 +03:00

package.json

feat(agiliton-account): Phase 1 service scaffold

2026-04-10 16:06:16 +03:00

tsconfig.json

feat(agiliton-account): Phase 1 service scaffold

2026-04-10 16:06:16 +03:00

vitest.config.ts

feat(agiliton-account): Phase 1 service scaffold

2026-04-10 16:06:16 +03:00

Description

Agiliton customer account service — SSO auth, conversation history, MCP WebSocket bridge

94 KiB

Languages

TypeScript 99%

Dockerfile 1%