Skip to content

WIP: add context budget UI groundwork#5

Draft
YumaKakuya wants to merge 1 commit into
hatch-gen1from
fix/task-role-description-fallback-hatch-gen1
Draft

WIP: add context budget UI groundwork#5
YumaKakuya wants to merge 1 commit into
hatch-gen1from
fix/task-role-description-fallback-hatch-gen1

Conversation

@YumaKakuya
Copy link
Copy Markdown

Summary

  • Add shared context budget helper, assistant context snapshots, footer groundwork, and /context dialog with /ctx alias.
  • Wire route-aware context metadata into processor, overflow, and compaction paths.
  • Preserve this as WIP because QA found blocker findings H1-H4.

Verification

  • cd /home/yuma/hatch-v3/packages/opencode && bun typecheck passed.
  • QA verdict: FAIL.

Known Blockers

  • H1: snapshot denominator diverges from live/overflow denominator.
  • H2: usable calculation ignores reservedCompaction for safe input path.
  • H3: footer fallback infers auth route from provider_auth available methods.
  • H4: footer fallback hardcodes 32_000.

Notes

  • This PR intentionally preserves the WIP for follow-up Senior remediation and QA/Reviewer review.

Add the shared context budget helper, assistant context snapshots, footer changes, /context dialog, and compaction route plumbing as WIP. QA found blocker findings H1-H4, so follow-up Senior remediation is required before acceptance.
@github-actions
Copy link
Copy Markdown

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

  • PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

@github-actions
Copy link
Copy Markdown

Hey! Your PR title WIP: add context budget UI groundwork doesn't follow conventional commit format.

Please update it to start with one of:

  • feat: or feat(scope): new feature
  • fix: or fix(scope): bug fix
  • docs: or docs(scope): documentation changes
  • chore: or chore(scope): maintenance tasks
  • refactor: or refactor(scope): code refactoring
  • test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant