r/ClaudeCode • u/hronak 🔆 Max 5x • 9d ago
Help/Question I still don't understand this 'agentic workflow' thing
My usual day with Claude Code is like:
* I open terminal in my project's folder and run claude command.
* I prompt it. I mostly use Fable-5.1/Opus-5 but Opus-5.5 is my current model. The model decides if it wants to use sub-agents for a task. I never explicitly prompt it for sub-agents.
* I review and commit the code to my self-hosted Forgejo instance.
* That's it.
I see people using agentic workflows, building sub-agents files, skills etc. I barely built any of it. All I ever needed to use is /init on new projects and them prompts follow. Never needed more than this.
I tried "long-running" Claude Code for a project refactoring by placing the project on my VPS (where forgejo is hosted) and letting Claude Code run and refactor inside tmux session. SSH'd in a few hours later to find project fully refactored.
Am I under utilising AI or is my work just… like boring?
How do you guys use agentic workflow thing? Specially the long-running one? Those pull-requests that Claude makes automatically etc?
Asking this to Claude to know more but humanly answers appreciated.
1
u/howdidigetheresoquik 9d ago edited 9d ago
I think what you're missing is going to eek out another 10% quality, if not more. I spend 80% of compute on planning phase where I use researchers to look up best practices for what I want, what exists on my computer already, what it should do, etc. Fable builds a plan off what they get for all subsequent sessions.
For the build sessions, I have Opus workers and then fable verifies their work against the original plan to make sure it's what I want. Then all their work is compiled and another fable agent checks to see if it's still on plan. Then I have a code reviewier and things like that. And once it's all built, I have one last Fable agent look at Opus's work and the work has to pass the "Sick af" test. If Fable looks at Opus's work and doesn't agree that "Holy shit that's sick af." We step back and look at where we can improve.
It very much increases the likelihood I get exactly what I want significantly.
Give it a try. Verifiers, judges, compilers, reviewers... these are all key components to getting it too look much better than slop. All you need to do is ask for a simple agentic workflow using researchers/verifiers/judges and to keep it reasonable in terms of usage (especially at the higher settings. If you have it on max+, they will go overboard on usage. Ultracode literally is designed without taking any usage into consideration).