desktop-mobile: Instructions file for Codex

AGENTS.md

Guidance for coding agents working in this repo: the commands to run, the checks a change needs, and the rules the linters don't enforce. README.md lists the services, and ROADMAP.md has what's next.

Commands

• One package: pnpm --filter <package> test (unit tests), test:integration, typecheck or build. These skip Turborepo, so they run against your workspace dependencies' built dist/, which may be stale. Build those first with pnpm turbo run build --filter=<package>^....
• All packages: pnpm turbo run typecheck test --filter=./packages/* is what the pre-push hook runs, and pnpm build builds every package. Turborepo caches both; add --force to rerun a cached pass. Don't run the root pnpm test: it also runs the E2E matrix and every package-test app.
• Lint: pnpm lint runs Biome and ESLint over the whole repo. It doesn't run through Turborepo, so don't pass it --force. A package's own lint script is Biome only and misses rules such as vitest/valid-expect. To check just what you changed, run pnpm exec biome check <files> and pnpm exec eslint <files>, as the commit hook does.
• E2E (e2e/, the pnpm e2e* scripts) needs the fixture app in fixtures/e2e-apps/ built first, and it's slow. CI runs it for the services a PR touches; locally, run the tests of the packages you changed. See docs/e2e-testing.md.
• Rust crates (packages with a Cargo.toml): from the crate's directory, cargo fmt, cargo test and cargo clippy --all-targets -- -D warnings. CI fails on unformatted code and clippy warnings.

Before you push

Husky runs Biome and ESLint on staged files when you commit, and typecheck and test for every package when you push. If you skip the hooks, run those checks yourself for what you changed. New logic needs unit tests.

Gotchas

• Every crate and Rust fixture commits its Cargo.lock. Commit it with any dependency change, and give a new crate one.
• The package tests install fixtures/package-tests/* in isolation, where catalog: doesn't resolve, so those fixtures use explicit versions, never catalog:.
• The package-test fixtures pin @electron-forge/* and electron-builder to exact versions. Bump those in their own PR.
• packages/dioxus-bridge/dist-js/index.js is a committed build of guest-js/. After editing guest-js/, run pnpm --filter @wdio/dioxus-bridge build and commit the result.
• releasekit versions and releases the packages from conventional commits on main, so don't edit versions or changelogs by hand. A breaking change (a ! after the commit type, or a BREAKING CHANGE: footer) merged to main makes that package's next release a major, so breaking PRs stay open until a major is planned. The exceptions are 0.x packages, where it makes a minor, and -next prereleases, where it only advances the prerelease number.