upvote

points

by mickeyp5 hours ago |
comments
upvoteby kuboble4 hours ago|
next
[-]
> I do not like terminal tui much as I think it's a poor fit for a coding agent

I recently moved away from using tui to directly interact with claude code.

I still start a session in the terminal but then ask to start a simple jira- like ticketing system.

When I have a request I start a new ticket and claude decides to either do it or launch a sub agent to do it.

When claude is done or has questions- he replies in the ticket. When claude has a side-findings he creates a new ticket for me.

reply
upvoteby mickeyp3 hours ago|
parent|
next
[-]
That's a really interesting workflow.

I also do orchestrator like work that way. The key difference is I'll have a master chat and let it delegate work as needed to sub agents.

I have skills, MCP etc for things that need it, and custom-designed sub agents for a couple of very specific, niche tasks. The rest use generic delegator, explorer, worker sub agents that just take normal instructions.

reply
upvoteby aspect05451 hours ago|
parent|
prev|
[-]
So does it develop a new ticket system every time? I'm not sure I can follow, could you explain?
reply
upvoteby californical4 hours ago|
prev|
[-]
Can you not? I built a custom harness that uses my Claude subscription. You can pass -p I think is the flag, to feed it a prompt. And it’s been a little while so I don’t fully remember how but you can also have it print the output to stdout. I even pass it custom tools as args and it works with the cache, and you can even append messages to conversations
reply
upvoteby mickeyp3 hours ago|
parent|
[-]
You can work around it like that for sure; you can call it from the CLI, and you get free credits also to spend.

But I meant more like, you know: hey just use the whole sub in another harness. That you can't do.

reply