agentleFS
7xuanlu7xuanlu/wenlan/app/AGENTS.md

wenlan / app

AGENTS.md358 starsChanged 4 months agoApache-2.0View on GitHub

Tauri 2 Rust crate and desktop runtime boundary. This directory owns app startup, Tauri plugins, sidecar declarations, macOS lifecycle helpers, daemon HTTP calls, and eval fixtures used by the app crate. - Debug builds refuse to start outside scripts/dev-runtime.sh. See that script for the variable set; release builds read none of these. - Keep daemon access behind WenlanClient in src/api.rs; do not scatter raw URLs or response-shape parsing through command handlers. Anything that talks to "the daemon" must go through…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. wenlan-app/wenlan★ 351100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository15 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep daemon access behind WenlanClient in src/api.rs.

    line 25
  2. Very specific:

    Prefer module-local Rust unit tests near the behavior under #[cfg(test)].

    line 30
  3. Very specific:

    Use app/tests/*.rs only for cross-module or daemon-backed integration.

    line 31
  4. Distinctive:

    Do not interpret CI's touched sidecar placeholders as real daemon validation.

    line 46
  5. Very specific:

    Do not make remote_access.rs failures silent without a recovery path or log.

    line 47
  6. Very specific:

    Do not change launchd/plist behavior without checking stale Origin and Wenlan migration paths in lifecycle.rs.

    line 48
  7. Distinctive:

    Do not add a new daemon API shape in Rust without updating the frontend wrapper if the UI consumes it.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md - app/

OVERVIEW

Tauri 2 Rust crate and desktop runtime boundary. This directory owns app startup, Tauri plugins, sidecar declarations, macOS lifecycle helpers, daemon HTTP calls, and eval fixtures used by the app crate.

WHERE TO LOOK

TaskLocationNotes
Add/modify Tauri commandsrc/search.rs, src/lib.rscommand body plus generate_handler! registration
Change daemon route usagesrc/api.rskeep typed request/response wrappers here
Startup, tray, window behaviorsrc/lib.rshigh fan-out; verify app lifecycle
Run-at-login or plist repairsrc/lifecycle.rsmacOS persistence and legacy Origin paths
Remote MCP behaviorsrc/remote_access.rs, src/remote_relay/local wenlan-mcp, native reverse transport, relay registration
Sources integrationsrc/sources/source traits, sync, uploads, wire types
Eval fixture editseval/fixtures/data-only TOML scenarios

CONVENTIONS

  • Debug builds refuse to start outside scripts/dev-runtime.sh. See that script for the variable set; release builds read none of these.
  • Keep daemon access behind WenlanClient in src/api.rs; do not scatter raw URLs or response-shape parsing through command handlers. Anything that talks to "the daemon" must go through client.base_url(), never a literal 127.0.0.1:7878 — an isolated dev app selects a different port.
  • Register new Tauri commands in src/lib.rs after adding the command function.
  • Prefer module-local Rust unit tests near the behavior under #[cfg(test)]. Use app/tests/*.rs only for cross-module or daemon-backed integration.
  • app/tests/sources_integration.rs is ignored because it needs a live daemon.
  • tauri.conf.json declares wenlan, wenlan-server, and wenlan-mcp as externalBin; packaging can fail before app code runs. Native reverse transport does not require a tunnel sidecar. Retain legacy process-ownership cleanup without restoring that packaging dependency.
  • A release launch refreshes ~/.wenlan/bin when those copies are older than this bundle: the previous file is renamed aside (.bak.<version>.<time>), then the name becomes a link to the bundled binary (a copy on Windows when the OS refuses the link). Debug builds and any run with WENLAN_DATA_DIR / ORIGIN_DATA_DIR must not touch that directory. See wenlan_core::home_bin.
  • eval/fixtures/gen/ is generated-data territory.

ANTI-PATTERNS

  • Do not interpret CI's touched sidecar placeholders as real daemon validation.
  • Do not make remote_access.rs failures silent without a recovery path or log.
  • Do not change launchd/plist behavior without checking stale Origin and Wenlan migration paths in lifecycle.rs.
  • Do not add a new daemon API shape in Rust without updating the frontend wrapper if the UI consumes it.

COMMANDS

cd app && cargo test
cargo fmt --check --all
cargo clippy --workspace --exclude wenlan-app --all-targets -- -D warnings
pnpm test:all

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.