Skip to content

Define reasoning and cached-token translation for cloud harness adapters #99

Description

@sanchitmonga22

Overview

Anthropic translator maps prompt/completion usage but not reasoning_content or cache_read_input_tokens; OpenCode config provides input/output prices only. Custom-provider usage-meter UI was explicitly deferred.

Priority: P2 / post-mvp. Impact: roadmap improvement. Initial planning estimate: Medium; refine after inventory. This issue does not add a release blocker.

Current evidence

Anthropic translator maps prompt/completion usage but not reasoning_content or cache_read_input_tokens; OpenCode config provides input/output prices only. Custom-provider usage-meter UI was explicitly deferred.

Design and implementation plan

Define supported reasoning and cache semantics by upstream/downstream protocols; preserve billing truth separately from optional display.

  1. Reconcile the current implementation and any already completed work with the evidence above.
  2. Record the owner, selected scope, dependencies and unresolved decisions before implementation.
  3. Implement or execute the selected scope using existing components and artifacts.
  4. Attach reproducible validation or outcome evidence and record any deferred work.

Acceptance criteria

  • Test streaming/nonstreaming reasoning and cache fixtures including absent fields, fragmented deltas and zero counts.
  • Do not double count cached tokens or expose hidden reasoning contrary to model protocol.
  • Document intentionally unsupported fields and keep backend billing independent.

Related work and deduplication

No existing issue has this acceptance scope; existing release defects remain separate.

Requirement provenance

Reconciled September 13, 2026 against WALLY_CLOUD_PRODUCT_SOURCES.md (SHA-256 e601b7b154b750965fa8d25d4533d3542621bd00b3bb30038c1fae553a549e7b) and the consolidated requirements report. Historical proposals are not evidence of current delivery, customer agreement or approved pricing.

Source records and physical line references

Records: C13-050, C01-045.

Lines: 35345–35352, 1019–1035.

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

    P2Follow-up priority: important improvement or deferred scope.enhancementNew feature or requestpost-mvpDeferred performance, portability, or out-of-scope work; not a Monday release gate.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions