Skip to content

fix(status): recommend ranges view in acp_status prompt snippet - #233

Open
ranxianglei wants to merge 1 commit into
masterfrom
2026-08-26_status-prompt-ranges
Open

fix(status): recommend ranges view in acp_status prompt snippet#233
ranxianglei wants to merge 1 commit into
masterfrom
2026-08-26_status-prompt-ranges

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Problem

acp_status promptSnippet suggested scope:"uncompressed" + view:"messages", steering models to the per-message firehose. Combined with the kernel's ranges view collapsing dense refs into one giant range, the tool's output was not actionable by range - see #193.

Fix

promptSnippet now recommends acp_status({ scope: "uncompressed" }) (the ranges view), which acp-kernel PR ranxianglei/acp-kernel#165 makes actionable: ranges grouped by conversation turn, sorted by size.

One-line change in src/status-tool.ts. typecheck + 428 tests + build all pass.

The promptSnippet suggested scope:'uncompressed' + view:'messages',
steering models to the per-message firehose. The ranges view is the
right default (now grouped by conversation turn and sorted by size in
acp-kernel PR #165), so recommend that instead.
@github-actions

Copy link
Copy Markdown

📦 Built Extension Artifact

Branch: 2026-08-26_status-prompt-ranges (18b276b)

Option A — Install from npm PR tag (recommended)

pi install npm:billion-context-pi@pr-233

Each push to this PR publishes a new version under the pr-233 npm tag.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pi-pr233.tgz
pi install ./package

This comment is automatically updated on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

[bot] Reviewed and verified PR branch 2026-08-26_status-prompt-ranges (commit 18b276b):

  • Diff is exactly the claimed one-line change in src/status-tool.ts:27: promptSnippet now reads acp_status({}) or acp_status({ scope: "uncompressed" }) — steering models to the ranges view instead of the per-message firehose.
  • description still documents view:'messages' as an available option (not a recommendation), which is consistent.
  • No tests assert the snippet text, so nothing stale to update.
  • Local CI run on the branch: npm run typecheck clean, npm test 428/428 pass, npm run build succeeds and the new snippet is present in dist/index.js.
  • No acp-kernel bump needed — this is prompt-only; the actionable ranges view comes from acp-kernel PR 跟踪 acp-kernel#86:pending nudge 半阈值接线 — 升级-only 影响 / 适配方案 / 后果评估 #165 shipping separately.

Ready for merge (human-only per repo rules).

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant