Skip to content

Expand and validate content and hosted-tool parity across both translators #48

Description

@dean0x

The forward adapter does not yet provide full image/content, structured-output, hosted-tool, and opaque cross-provider history coverage. The reverse native tool bridge must not advertise complete feature coverage based only on simple text/file-read tests.

Inventory unsupported content blocks, image-bearing messages/results, structured output, hosted tools, mid-conversation instruction updates, and foreign compacted histories. Add explicit capability reporting and consistent failure/warning behavior, then implement and validate extensions in both directions. Native namespaces/freeform tools required for Codex's basic tool execution remain part of the reverse parity baseline.

This tracks broader extensions outside the current bidirectional parity scope.

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