Skip to content

feat(sensor): agent joins the Decepticon gateway network for shared LLM config - #8

Merged
PurpleCHOIms merged 1 commit into
mainfrom
feat/agent-gateway-network
Oct 26, 2026
Merged

PurpleCHOIms merged 1 commit into
mainfrom
feat/agent-gateway-network

Conversation

@PurpleCHOIms

Copy link
Copy Markdown
Member

Completes the shared-LLM-configuration wiring for the co-deployed stack: the LiteLLM gateway publishes on host loopback only, so the agent container now joins the Decepticon stack's network and calls the gateway by container name. Gateway env passthrough (DECEPTICON_LLM__PROXY_URL/API_KEY/BLUE_MODEL) added to the service.

Live verification: events -> rule detection (command_injection) -> in-stack blue_cell agent server -> shared gateway -> real model response -> assessment notification delivered to the Blue feed — with the ported prompt-injection shield wrapping the sensor tool output live (the full autonomous cycle on AutoBot's own runtime, closing the 2b-ii verification).

…shared LLM config

The shared LiteLLM gateway (the operator's Decepticon stack) publishes on
host loopback only, which containers cannot reach via host-gateway. The
autobot-agent service now joins the Decepticon stack's network and calls the
gateway by container name (http://decepticon-litellm:4000), with the gateway
env passthrough (DECEPTICON_LLM__PROXY_URL/API_KEY/BLUE_MODEL) added to the
service definition.

Verified live end-to-end on this wiring: events -> rule detection ->
in-stack blue_cell agent server -> shared gateway -> real model response ->
assessment notification (the ported prompt-injection shield wrapped the
sensor tool output live).
@PurpleCHOIms
PurpleCHOIms merged commit 37a4e9d into main Oct 26, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant