Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Team Chat UI in Front of Agent Gateways

    1

    Securely integrate team chat UIs with agent gateways using per-user session isolation and grant-based access control.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Team Chat UI in Front of Agent Gateways

    Team Chat UI in Front of Agent Gateways

    Example session with this skill installed

    Set up per-user session isolation for an Open WebUI container fronting my agent gateway, ensuring users don't see each other's chat history.

    • Read your context and instructions
    • Compiled the team chat ui

    The session isolation configuration has been generated for your container deployment. This setup uses environment variables to forward user identities as unique headers, which your gateway must be configured to read as session keys.

    Container Configuration

    
    # Add these environment variables to your Docker Compose or run command
    services:
      chat-ui:
        image: ghcr.io/open-webui/open-webui:v0.12.5
        environment:
          - ENABLE_FORWARD_USER_INFO_HEADERS=true
          - FORWARD_USER_INFO_HEADER_USER_ID=X-Agent-Session-ID
          - BYPASS_ADMIN_ACCESS_CONTROL=false
        networks:
          - agent-net
        deploy:
          resources:
            limits:
              cpus: '2'
              memory: 2G
    

    Integration Steps

    Identity Mapping: The FORWARD_USER_INFO_HEADER_USER_ID is set to X-Agent-Session-ID. Ensure your gateway is configured to use this header for session partitioning.
    2.

    Admin Gating: BYPASS_ADMIN_ACCESS_CONTROL is explicitly disabled to ensure admin accounts are subject to the same model visibility grants as standard users.
    3.

    Snapshot Verification: Before deploying, run docker inspect on any existing container to back up current wiring.

    Next steps

    • Verify the gateway's session store shows unique keys for different users after they send their first message.
    • Test the LAN path using curl http://<lan-ip>:<port>/api/version from a separate machine.
    • Implement a whitelist filter for display names to prevent prompt injection via identity headers.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    You want to give your team a clean chat interface to your agent stack — without open signup chaos, blended session memory, or an intern stumbling into the admin lane. Off-the-shelf tutorials show you how to start a container. This skill shows you how to run one in production behind agent gateways, where the real failures live: firewalls, registry quirks, and access leaks nobody notices until a user mentions them.

    Everything in here was learned the expensive way: deployments verified on loopback but unreachable from the LAN for a day, a second gateway silently overwriting a lane in the model registry, wildcard access grants leaking an admin-only model to the whole team, and an agent greeting every employee by the founder's name. The fixes are encoded as checkable steps, so your next deploy ends green instead of with an apology — and so the next operator who touches the box finds the wiring intact, documented, and verifiable from outside the machine.

    What you get

    • The args-snapshot update recipe — recreate containers from a full docker inspect snapshot instead of hand-listed env vars, so your session-tagging wiring survives every upgrade. Data and wiring backups, sub-two-minute downtime.
    • Per-user session isolation — the two environment variables that forward identity headers to your agent gateway, plus the identity-injector filter pattern (task-call gating, name sanitization, opaque session keys) that stops cross-user memory bleed.
    • Grant-based access control done right — why admin roles never gate model visibility, how wildcard grants leak lanes silently, and the per-account verification loop that catches it before users do.
    • The verify-from-outside-the-box rule — the verification ladder (version endpoint, health, LAN curl from a different machine, real chat completion) that would have saved that day-long "verified but unreachable" outage.
    • A troubleshooting table of the eight classics — first-boot embedding downloads, model-ID collisions, registry listings that lie, lost mid-stream replies, and their exact fixes.

    Ship a team chat UI in one evening and never explain to a teammate why the agent thinks they are someone else.

    Requires gateway support for session headers. Version-specific behaviors pinned to Open WebUI 0.11.x and 0.12.5. Identity injection may increase token overhead on background tasks.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    Permissions

    Network Access
    Read Files
    Listed1 day ago

    What's inside

    Frequently Asked Questions

    This skill acts as a security and routing layer that prevents 'session bleeding'—where one user's chat history or identity leaks into another's—by enforcing strict per-user header isolation and grant-based access control between your UI and the agent gateway.

    The skill is designed for Open WebUI integrated with any OpenAI-compatible agent gateway (such as LiteLLM or vLLM) that supports session scoping via custom headers.

    You receive a production-ready configuration package including Docker orchestration files, identity mapping templates, and an automated integration test suite to verify your security boundaries.

    Unlike standard documentation, this skill includes a 'verify-from-outside' testing matrix that explicitly tests for negative cases, ensuring unauthorized users are blocked from sensitive agent lanes before you go live.

    The skill handles identity injection by mapping user-specific context into system messages, allowing agents to recognize and greet team members by name without compromising session keys or security tokens.

    Setup involves configuring your container resource limits, wiring the identity header mapping, and defining your access grants; the included preflight checks ensure your host-network configuration is stable for production use.

    New in Agents & Orchestration