Repository navigation
chore: Add a browser-automation rule to rule_text.rs so codex/cursor/windsurf/vscode-copilot/cline actually learn about it via agentflare init - #772
Merged
getappz merged 3 commits intoSep 18, 2026
Conversation
## Status Added a `BROWSER` rule constant to `src/rule_text.rs` (mirroring `EXA`/`FLARE_DOCS`'s terse `@tag` style — `@use`, `@commands`, `@scope`, `@how`) covering the `agentflare browser` CLI, and added it to `rule_text::all()`. Since `codex`, `cursor`, `windsurf`, `vscode-copilot`, and `cline` all get their rule files from `rule_targets()` joining `all()` (`src/components.rs`), this fixes the gap for all five without per-host wiring — same pattern item #280 already validated for `FLARE_DOCS`. Added a test, `browser_rule_is_included_in_joined_hosts`, mirroring the existing `flare_docs_rule_is_included_in_joined_hosts` test. Scope note: `claude-code`/`opencode` weren't touched — they list explicit per-file rule constants rather than using `all()`, and both already have direct MCP access to the browser tool, so they weren't part of the reported gap. Verification (all synchronous, in foreground): - `cargo build --lib` — success (had to bypass the `sccache` rustc-wrapper, which was failing with spurious "Read-only file system" errors on `.d` file writes in this worktree — unrelated to my change, a pre-existing environment issue with the sccache wrapper/shim, not the code) - `cargo test --bin agentflare -- components::` — 43 passed, 0 failed, including the new test - `cargo fmt --check` — clean Concern: the `sccache` build issue is worth flagging separately — plain `cargo build`/`cargo test` fail in this worktree unless `rustc-wrapper` is disabled. Not caused by this change, but it'll bite the next build here too. Agentflare-Branch: task/285-add-a-browser-automation-rule-to-rule-te Agentflare-Item: 285
|
Warning Review limit reachedNext included review available in 6 minutes. View limit detailsLimit details: You’ve used the included review currently available. Your 61 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (2)
Comment |
getappz
deleted the
task/285-add-a-browser-automation-rule-to-rule-te
branch
September 18, 2026 08:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Small, focused diff. Everything's verified.
Status
Added a
BROWSERrule constant tosrc/rule_text.rs(mirroringEXA/FLARE_DOCS's terse@tagstyle —@use,@commands,@scope,@how) covering theagentflare browserCLI, and added it torule_text::all(). Sincecodex,cursor,windsurf,vscode-copilot, andclineall get their rule files fromrule_targets()joiningall()(src/components.rs), this fixes the gap for all five without per-host wiring — same pattern item #280 already validated forFLARE_DOCS.Added a test,
browser_rule_is_included_in_joined_hosts, mirroring the existingflare_docs_rule_is_included_in_joined_hoststest.Scope note:
claude-code/opencodeweren't touched — they list explicit per-file rule constants rather than usingall(), and both already have direct MCP access to the browser tool, so they weren't part of the reported gap.Verification (all synchronous, in foreground):
cargo build --lib— success (had to bypass thesccacherustc-wrapper, which was failing with spurious "Read-only file system" errors on.dfile writes in this worktree — unrelated to my change, a pre-existing environment issue with the sccache wrapper/shim, not the code)cargo test --bin agentflare -- components::— 43 passed, 0 failed, including the new testcargo fmt --check— cleanConcern: the
sccachebuild issue is worth flagging separately — plaincargo build/cargo testfail in this worktree unlessrustc-wrapperis disabled. Not caused by this change, but it'll bite the next build here too.Opened by
claude-codeon flared:51bb8de6c33b for item #285 via agentflare.