Skip to content

Issues with the no_proxy env vars using Kits #218

@cdr-chakotay

Description

@cdr-chakotay

Not sure whether this belongs here or to Mistral, but I'll try :)

I am currently building a Kit for Mistral Vibe.

Inside the sandbox, two no_proxy environment variables are exposed:

no_proxy=localhost,127.0.0.1,::1,[::1],gateway.docker.internal
NO_PROXY=localhost,127.0.0.1,::1,[::1],gateway.docker.internal

However, the Mistral's vibe CLI seems to choke on the [::1], which causes the CLI to fail.

File "/home/agent/.local/share/uv/tools/mistral-vibe/lib/python3.14/site-packages/httpx/_urlparse.py", line 411, in normalize_port\n    raise InvalidURL(f"Invalid port: {port!r}")\nhttpx.InvalidURL: Invalid port: ':1]'

Since Mistral Vibe uses HTTPX internally, this could happen with other agents as well.

For now, omitting the braced statements works, but I don't know whether this is a good idea and if this would break other setups.

no_proxy=localhost,127.0.0.1,::1,gateway.docker.internal
NO_PROXY=localhost,127.0.0.1,::1,gateway.docker.internal

Happy to receive some feedback on this. So long!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions