Skip to content

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 into
masterfrom
task/285-add-a-browser-automation-rule-to-rule-te
Sep 18, 2026
Merged

getappz merged 3 commits into
masterfrom
task/285-add-a-browser-automation-rule-to-rule-te

Conversation

@getappz

@getappz getappz commented Sep 18, 2026

Copy link
Copy Markdown
Owner

Small, focused diff. Everything's verified.

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.


Opened by claude-code on flared:51bb8de6c33b for item #285 via agentflare.

## 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
@coderabbitai

coderabbitai Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 6 minutes.

Check out review usage here.

View limit details

Limit 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.
You're only billed for reviews past your plan's rate limits ($0.25/file).

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Essentials

Run ID: 53b0064a-1ec3-44f3-8c60-ee42ee2c9f12

📥 Commits

Reviewing files that changed from the base of the PR and between c71ff77 and 7b70958.

📒 Files selected for processing (2)
  • src/components.rs
  • src/rule_text.rs

Comment @coderabbitai help to get the list of available commands.

@getappz
getappz merged commit c1cacf9 into master Sep 18, 2026
16 checks passed
@getappz
getappz deleted the task/285-add-a-browser-automation-rule-to-rule-te branch September 18, 2026 08:13
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