feat(flare-code): restyle statusline badge to Claude Code native hint style - #311
Conversation
… style
Replace the [FLARE-CODE]/[FLARE-CODE:MODE] badge with Claude Code's own
status-line hint convention:
⏵⏵ flare mode on (optimize code) ·
arrow-glyph prefix, lowercase phrase, a parenthetical carrying the active
mode, trailing '·' segment separator, single cyan accent (256-color 51).
full is the unqualified default; every other mode names itself in the
parenthetical (e.g. 'optimize code: ultra'). Supersedes the ultra-amber-173
color signal from #316 — the mode now rides in the text.
Retires the external sed stopgap in ~/.claude/settings.json that only
matched the plain full-mode bytes; agentflare now emits the native style
first-class for every mode. statusline_tests updated.
Agentflare-Agent: claude-code_2-1-218_agent
Agentflare-Branch: fix/statusline-native-317
|
Warning Review limit reached
Next review available in: 14 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…k/<seq> branch (#673) An item created by discover_untracked_prs for a hand-opened PR carries metadata.pr.branch naming that PR's real branch, which has nothing to do with the task/<sequence_id> convention every worktree/branch-name resolver assumed. Dispatching self-repair on such an item created a brand-new orphan branch and pushed to it, opening a duplicate PR instead of continuing the existing one -- reproduced live on image-qc item #19 / PR #311, where self-repair opened duplicate PR #314 on branch task/19-feat-add-images-crate-... instead of pushing to PR #311's own feat/image-conversion-module. resolve_worktree_branch (and everything built on it: create_worktree, resolve_item_task_branch, is_pr_merged, relabel_pr_completed, push, CI-status polling) now prefers an item's tracked_pr_branch over the derived task_branch_name, and accepts it as a valid already-checked-out branch too so a second dispatch doesn't undo the fix. A no-op for items dispatched the normal way, since their metadata.pr.branch is always the same value task_branch_name would have derived anyway. Agentflare-Agent: claude-code Agentflare-Branch: fix/self-repair-duplicate-pr-branch Agentflare-Session: 32183145-c269-4579-ac01-af6c423c2d3f Co-authored-by: shiva <shiva@gosysinfo.tech>
1 participant
Restyles the flare-code statusline badge to match Claude Code's own status-line hint convention (
⏵⏵ auto mode on (shift+tab to cycle) · …).Before:
[FLARE-CODE](green) /[FLARE-CODE:ULTRA](amber) /[FLARE-CODE:MODE](green)After:
⏵⏵ flare mode on (optimize code) ·— arrow-glyph prefix, lowercase phrase, parenthetical carrying the active mode, trailing·separator, single cyan accent (256-color 51).full→⏵⏵ flare mode on (optimize code) ·⏵⏵ flare mode on (optimize code: ultra) ·,… (optimize code: lite) ·,… (optimize code: review) ·FLARE_CODE_HIDE_STATUS) /off/ empty → nothing (unchanged)Supersedes the ultra-amber-173 color distinction from #316 — the mode now rides in the text, so a single accent covers every mode.
Retires a stopgap:
~/.claude/settings.jsoncurrently pipes the statusline through asedfilter that only pattern-matches the plain full-mode bytes and silently no-ops for ultra/labeled modes.statusline_badge()now emits the native style first-class for every mode, so after this merges + an agentflare reinstall, that sed filter gets deleted andstatusLine.commandcalls agentflare directly.statusline_testsupdated to pin the new byte sequences for full / ultra / lite / review. fmt + targeted tests green.Closes item #317.