The .guijam directory
GUIJam keeps its working files in .guijam/ at your project root. init adds it to .gitignore, and the dev server's file watcher ignores it.
.guijam/
├── run/
│ ├── daemon.json the daemon's port and session token
│ ├── lock one daemon per project
│ ├── timings.json recent wait times, for the wait estimate
│ ├── candidates/ preview content for Tailwind to scan
│ └── overlays/ previews served to Next.js
├── logs/
│ └── gjd.log the daemon's output
└── journal/
├── 2026-11.jsonl one journal file per month
└── blobs/ previous file contents, by content hashrun#
The running daemon's state. On macOS and Linux, the folder is readable only by you.
daemon.jsonholds the daemon's process ID, port, session token and version. It's written atomically, and on macOS and Linux only you can read it.lockmakes sure only one daemon runs per project.timings.jsonkeeps how long the first variant took on the last 10 runs, for each AI tool, model and kind of request. After 3 runs, the widget quotes the middle one when a drawing takes a while.candidates/mirrors preview content, so Tailwind generates CSS for classes that only exist in a preview.overlays/and thenext-relayfiles exist only in Next.js projects, where previews are served through files.
The daemon stops after 30 minutes with no dev server connected, and is replaced as soon as a dev server starts with a different GUIJam version installed.
logs#
gjd.log collects the daemon's output, appended across runs. For AI requests it records:
- Each answer: the tool, its version, the model, the effort, how long the tool took to start and to answer, the answer's size, and its cost when the tool reports one.
- Each failed run: the tool, its version, the model and the error, with account and session IDs replaced by
redacted. - Each drawing: how long capturing the page, the first variant and all variants took, whether it had a sketch over an element, a sketch in empty space or none, and how many variants were dropped, with a line giving each one's reason. Check it when Troubleshooting asks you to.
journal#
The undo history. Each month gets one append-only .jsonl file. Each change is recorded when it begins, with the files it touches and their content hashes before and after, then again when it commits or aborts.
blobs/ stores the exact previous contents of each file, named by content hash, so undo can restore them byte for byte.
Can I delete it?#
Yes, with your dev server stopped. You lose the undo history; GUIJam recreates the folder the next time it starts.