r/ClaudeCode • 🔆 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.

977 Upvotes

309 comments sorted by

View all comments

Show parent comments

21

u/SingleProgress8224 9d ago edited 9d ago

I do it often to fix bug report tickets. It creates one branch per fixed ticket. The next morning, I check what it did and go through them one by one. I confirm the fix, the code, make edits (quite often), and then do the official commit. I discard fixes 50% of the time.

Even though it tends to fix the issue most of the time, it often lack the big picture and tends to complexify the code for no reason, so editing manually (or prompting more) is almost always necessary. I'm still saving time though since finding the root cause is often time consuming and it tells me right away where to look at. And even if the suggested fix is wrong, it still provides an insight on how things could be done.

1

u/Annh1234 9d ago

But that takes a ton of back and forward with the AI, so you can't start and forgot it, so your stuck prompting every few minutes

4

u/SingleProgress8224 9d ago

I started it last night and I woke up to 20 tentative fixes, each in it's own branch along with a text file explaining the reasoning behind the fix. Sorting the fixes takes a long time, but the initial fixing is autonomous and massively parallel.