Skip to content

fix(models): do not advertise Pi routes isolated execution cannot run #131

Description

@drewstone

Reproduction

At CLI Bridge 0bb4ec63547050a48e607548830d8d91cdb1f039 with Pi 0.83.0:

  1. Start CLI Bridge with only the Pi backend.
  2. GET /v1/models returns pi/openai-codex/gpt-5.6-luna.
  3. Submit that exact model through the required isolated Pi path (BRIDGE_JAIL_MODE=fs-jail).
  4. The request fails before inference with: backend pi provider openai-codex has no explicit entry in ~/.pi/agent/models.json; define its baseUrl, api, and model there so isolated forwarding cannot guess.

Observed in a packed Braid run: 0 input tokens, 0 output tokens, $0 reported cost. Cleanup removed all three temporary directories and stopped CLI Bridge. A configured pi/tangle-router/glm-5.2 request succeeds through the same path, so this is model admission/catalog drift rather than a general Pi failure.

Expected

/v1/models should only advertise Pi routes executable by the mandatory isolated transport, or expose explicit readiness metadata that callers can use to reject unavailable routes before admission. The health response should not report Pi fully ready when the selected advertised model is known to be unusable.

Related Braid live-path correction: tangle-network/braid#7.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions