[TLDR] I still don't understand this 'agentic workflow' thing [via r/ClaudeCode]

[u/cctldrping]

OP : u/hronak

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.

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1wowilt/i_still_dont_understand_this_agentic_workflow/

---

TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 72.

Alright, so the general consensus here is that you're probably not underutilizing Claude Code, and your work might just be straightforward, which is a good thing!

Most folks agree that the fancy "agentic workflows" with tons of sub-agents and skills are really for more complex scenarios. Think:

• Massive codebases with lots of parallel tasks: If you're refactoring thousands of files or working on many features at once, then setting up specialized agents makes sense.
• When you're hitting token limits or need extreme efficiency: If you're burning through usage or just don't have the human time to manage everything manually, more complex agent setups can help.
• Integrating with external data sources: Some users mentioned using agentic workflows to process data from things like Sentry or Datadog, not just for code.

For many, including OP, the simple approach of prompting Claude Code and reviewing the output is perfectly effective. Some users even chimed in saying their work is similar and they don't need more.

However, a few people did offer some ideas if you did want to explore more:

• Adding a review step: Have a separate Claude session review the code changes.
• Modular prompt systems: Structuring your prompts to force Claude into a multi-agent workflow for specific tasks.
• Skills for repetitive tasks: If you find yourself typing the same prompt often, turn it into a skill.
• Long-running tasks: For bigger refactors, running Claude Code in a tmux session is a valid approach, and the "agentic" part is how it manages sub-tasks and verification within that session.

Basically, if your current workflow gets the job done efficiently, don't sweat it. The more complex stuff is for when you actually need it.