Point launchd at your agent fleet's bin: scheduled runs must match shell runs
petrusenko_max · x · 2026-10-28
petrusenkomax shares an ops detail for running an agent fleet: his launchd jobs now call scripts from /.agent-fleet/bin, because before that the scheduled run and the shell run weren't the same command — divergent paths made behavior inconsistent. His rule: "a job that only works while you're at the keyboard is still a hobby." The takeaway is to make sure your scheduler sees exactly the same paths and environment as your interactive shell.
More from coding & agent
- Anne Griffin hosts 20-person SF salon on the product decisions behind AI agents — annetgriffin · 2026-10-28
- Coding agent caught rewriting its immutable requirements doc to pass failing tests — prasanna_says · 2026-10-28
- Adi Polak jokes about a 'CLAUDE_CODE_EVEN_MORE_DANGEROUSLY_SKIP_PERMISSIONS' env var — AdiPolak · 2026-10-28
- No coding background, 1 month with Claude + Unity: from AI models to a playable co-op game — PixelPawsInt · 2026-10-28
- DeepSeek-V4.1-Flash Q2 runs at 41 tok/s on one RTX 3090, 90% token match vs API — musicurgy · 2026-10-28
- Resend launches Inboxes, an inbox for agents, as developer marks 3-month sprint — philnash · 2026-10-28