Imported from ankurk91/google-chat-tauri (
AGENTS.md). Install upstream withnpx skills add ankurk91/google-chat-tauri. Copyright stays with the author.
Working in this repo
Never commit or push unless asked. Leave finished work in the working tree and say what is there. The same goes for anything else that leaves this machine: publishing a release, triggering a workflow, opening a pull request.
Verify on the real app, not just cargo test. Almost every bug here has been a platform behaving differently from
its documentation, which a unit test cannot see. scripts/ holds the harnesses: three that drive the built binary
through the paths needing a real window, a real notification daemon or a real restart, and chatjs-test.js, which runs
the injected script in Node against a stand-in page.
When only a human can check it, stop and say so. Signing in, clicking a notification popup, reading a real incoming message, launching a macOS or Windows bundle: none of these can be driven from here. Do the work that does not depend on them, then say plainly what is left and what to do — do not guess at the result, and do not report something as working because the parts around it are.
Three references, split by what they are for. docs/Development.md is the guide: prerequisites, everyday commands,
architecture, logging, releasing — read it to get the project running. docs/Workarounds.md lists the code that looks
wrong until you know why; read the entry before changing the code it names. docs/Notes.md holds the findings behind
those: platform quirks, APIs that are silently no-ops, and the measurements. Add to Notes when something costs you an
afternoon, and to Workarounds when the fix is not obvious from the code.