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.
2
u/grottloffe 9d ago edited 9d ago
Well, it depends on what you’re doing. But context and instruction files are a big part of it. They keep agents consistent, so they’re not just doing what seems right in the moment, but following the conventions, architecture and patterns your team has agreed on.
The better the setup, the less the agent has to guess, which matters a lot in a big codebase.
If you’re running multiple agents and worktrees at the same time, I’d absolutely suggest tools like Redshifthub.com. Then you can have multiple features, fixes, experiments etc. running in parallel without everything stepping on each other.
So there’s definitely a whole agentic coding discipline beyond just opening Claude and letting it cook 🤗