Repository navigation
Work Tracebook 1.1
Work Tracebook 1.1 makes sure your agents can actually reach it: it checks they can find the factorylog command, lets Codex write its reports, and sends a test report on request.
What's new
- PATH check. Agents get their
PATHfrom your login shell, so setup now asks that shell whether it can findfactorylog. If you use zsh and it can't, Add to PATH adds~/.local/binto~/.zshenv. Other shells get the steps to fix it. - Codex can write its reports. Codex's sandbox only lets commands write inside the project. Connect Codex now also adds the Work Tracebook folder to its writable roots in
~/.codex/config.toml. If you connected Codex in 1.0, Settings shows it as not connected until you click Connect Codex again. - Send a test report. One click runs the command the way an agent does, so you can check the setup without waiting for an agent.
- Clearer setup. The welcome screen says what gets logged: work that changes something, not answers to questions. The README covers other agents and what to check when reports don't show up.
Install
Download Factory-Log-1.1.0.zip, unzip it, and drag Work Tracebook to your Applications folder. It runs on macOS 15 Sequoia or later, on Apple silicon and Intel Macs. If you have 1.0, Work Tracebook offers the update on its own, or use Work Tracebook → Check for Updates….
Work Tracebook isn't signed with an Apple Developer ID or notarized, so the first time you open it, macOS says it "could not verify Work Tracebook is free of malware". Click Done, then either:
- open System Settings → Privacy & Security, scroll down to Work Tracebook, and click Open Anyway.
The README has the details, including what to do on a work laptop.
Everything Work Tracebook records stays on your Mac, in a plain JSONL file, and it never reads your code, diffs or terminal.
SHA-256 of the zip: f75988fa34897b2e11ef311c23823f5d695dcd40e837e842d641bca5a852aae5