11–20 of 24 posts
How do I know this won't just eat through my token budget? It's hard to understand from the website how "done" is derived in the loop. If it's not deterministic then it seems like it would be prone to over-engineering.
How do I know this won't just eat through my token budget? It's hard to understand from the website how "done" is derived in the loop. If it's not deterministic then it seems like it would be prone to over-engineering.
Would this be where llm/agentic observability come into play?
I think the actual loop engineering lives in skills and workflows. The trigger is the creation of a ticket, manual or programmatic; e.g., through an incident.
Regarding skill and workflows, I don’t want to make you couple your way of work to the routine, if you want to load the the workflows and skills feel free, in the end of the day the routine is only a scheduled prompt.
Would love to hear more about your way of working with event driven actions
I find it kind of hard to follow/read whatever theme/style it is, something about the big blocks breaks up the flow of reading.
# at 3am every day..
* * * 3 0 cd ~/src; claude -p "find and fix bugs and commit"