Codex local-first apps and idempotent imports
Keep SQLite data and files local. Verify repeat imports, empty states, and the boundary of filesystem access.
中文Install in Codex
Codex with a local SQLite app and a fixed import fixture.
- Review `.agents/skills/local-first-app/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.agents/skills/local-first-app/` in your project and save the reviewed file as `.agents/skills/local-first-app/SKILL.md`.
- Start Codex from that project's root, then type `$local-first-app` and select the matching skill.
Example task
Check that processing the same local record twice leaves consistent state.
{"recordId":"import-demo-17","title":"April notes","runs":2,"startingCount":0}What to check
After both passes, SQLite contains exactly 1 `import-demo-17` record titled `April notes`. The list has no duplicate.
Original SKILL.md on GitHub · Updated
Frequently asked question
Why should the import flow cover empty states?
An empty database or input affects the first-run experience. Verify the message and check that no unexpected records appear.