Skip to content

Using custom provider context remaining 100% always #235

@gh-orange

Description

@gh-orange

Pre-submit Checks

  • I have searched Zap issues and there are no duplicates.
  • This bug is in Zap itself — not in upstream Zap's cloud account, billing, Warpify SSO, or cloud-only features.
  • I have included relevant logs (RUST_LOG=info output, panic traces, etc.). Optional, but greatly speeds up triage.
  • If the bug is in the AI / BYOP path, I have included the provider name, base URL pattern (redacted), and model id.

Describe the bug

Using custom provider context remaining did not decrease after every chat

To reproduce

  1. Open new tab
  2. chat with agent

Expected behavior

No response

Screenshots, videos, and logs

No response

Operating system (OS)

Windows

Operating system and version

Windows 11 23H2

Shell version

No response

Zap version / commit

v2026.06.04.1

AI / BYOP path involved?

No — non-AI bug (terminal, blocks, UI, shortcuts, etc.)

BYOP provider (if applicable)

No response

Regression

No, this issue has existed throughout my use of Zap.

Last known good build / date (if regression)

No response

Additional context

No response

Does this block your daily use of Zap?

No

Reproducible only in Zap?

Only in Zap.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions