bro it isnโt generally intelligent bro its only read every book and paper ever written and just making connections between them bro. its only thinking for twenty hours bro itโs just brute force thinking bro. its only solving erdos problems bro it could never be an accountant bro
if you are building knowledge worker agents that require more setup than the equivalent of "here's a laptop in the mail show up to the office Tuesday at 8:30am" you're ngmi
@cosmastech@josephkerkhof@laravelphp Another reason I was exploring this: say you need to call an external service that could take hours or days. Workflow kicks it off, pauses. Whenever the service is done, it sends a webhook back, signal fires, workflow picks back up. No polling, no job sitting there waiting.
I built a workflow POC around a similar concept with "signals"
A workflow can pause at any step and persist its wait state in the db. When a matching signal fires (event or webhook), it picks up right where it left off ... even if that's a year later!
Human-in-the-loop was the main use case (an approval or rejection fires the signal to resume the workflow)
An easy win for you today...
Update Laravel Boost to the latest version, which includes the new "laravel-best-practices" skill.
Then, prompt your agent to use that skill to perform an audit of your entire codebase.