Skip to content

feat(telemetry): add input/output token rate split to agent contract #167

Description

@xodapi

Источник

Follow-up от #105/#164. Android MVP can use aggregate token_rate, but original #105 also asks for incoming/outgoing token speed. That cannot be honestly implemented until the telemetry source emits separate input/output fields.

Что сделать

Extend the agent telemetry contract and collector/API source so consumers can read separate input and output token rates:

  • top-level input_token_rate
  • top-level output_token_rate
  • optional agents[].input_token_rate
  • optional agents[].output_token_rate

After the producer contract exists, Android can display split rates instead of aggregate-only rate.

Blocker

Blocked until there is a concrete telemetry producer to update: abtop-compatible collector, remote collector endpoint, or VibeMode/API endpoint.

Scope

This issue is contract/producer work, not Android UI polish. Do not fake the split by deriving it from aggregate quota deltas.

Нельзя трогать:

  • .env, API keys, prompts, raw transcripts
  • Android API key handling
  • UI labels that claim input/output split before the data is real
  • new dependencies without separate justification

Acceptance Criteria

  • Telemetry source emits separate input/output token rates at top-level or per-agent level.
  • Consumer contract documents missing-field behavior.
  • No prompts, API keys, paths, tool arguments, raw transcripts, or task titles are exposed in telemetry payloads.
  • Android feat(android): add aggregate agent pulse and live token chart MVP #166 can remain aggregate-only; this issue unlocks a later UI split.

Links

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

    agentГотово к выполнению агентомblockedЗаблокированоfeatpriority:lowНизкий приоритетzone:androidAndroid-specific build, permissions, bridge, APK

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions