pull down to refresh
Not trying to avoid question or be snarky, but i use it for everything.
My interactions with a agent start with a fairly big prompt from me and a big resonse from the agent.
This 1st reponse is the bulk of the stuff what we we go back and forth on.
So i want to have a very easy and fast way to reference things from this and other parts of the chat.
I found this to be the case for codings stuff, but also non-coding things.
I still am very involved in how I use agents and like to micro-manage hance why I do this often.
This is ofcourse more usefull in the planing/brainstorming/back and forth stages as thats where you want to reference things.
Btw since I wrote the OP, I already vibe coded somethign that works in vs-code will share later :)
I still am very involved in how I use agents and like to micro-manage hance why I do this often.
Same for me.
My interactions with a agent start with a fairly big prompt from me and a big resonse from the agent.
This 1st reponse is the bulk of the stuff what we we go back and forth on.
So i want to have a very easy and fast way to reference things from this and other parts of the chat.
I built a little framework around forgejo to tackle this, to not have to deal with chat. I wrote a single skill for repo interaction with issues, comments, PRs and attachments (and later a second one for REST API interaction with my data lake.) And a little kanban board so I can backfill it, multitask and prioritize things. Oh and it's multi-framework so I can assign to codex/gpt or claudecode/opus or opencode/<ppq/local>... it's all one mechanism and I often let different models interact on the same subject.
I have repos for everything, from idea scratchpads to deep research to code repositories... all these have RBAC (so I can control what for example Anthropic or OpenAI are allowed to see - i.e. I don't need Anthropic spookware to know everything I am working on.)
But, there is one specific thing you mention that I never do: I don't argue with a bot. Ever. If I get something inferior, it means I didn't break down the job very well (or it hallucinated, which happens also on the "frontier" crap.) So I just rewrite my instructions.
Because of this, I do not talk to bots. I instruct the tool what to do. I do not argue. I relentlessly throw away crap and improve the approach to getting what I want. But never, ever do I waste my time arguing with a bot. It's already outrageous that I get billed for bad answers.
That's a nice setup, and I considered something similar, but I figured the time getting to work and debugging is not worth it, though the more time passes the better an investment seem to have been.
Man as you say this never argue with a bot, kinda makes me think I should re-evaluate the way I use LLMs.
Thing is that if 1st answer is not ok, chances are rest of convo will be hair pulling and force steering of model.
Thing is that if 1st answer is not ok, chances are rest of convo will be hair pulling and force steering of model.
Exactly. And remember, you're feeding it the wrong narrative that you wanted to get rid of in context when you argue, so you basically pre-poison the outcomes.
I think that once I got rid of synchronous interfaces (because it's all queued up) I got wayyy more happy with LLMs, because it didn't cosplay a human anymore, but instead I just have an army of agents now that get orders and what I say gets executed.
When your commanding officer tells you to do something, it isn't a conversation, it's an order. So the mindset is: I am the commanding officer of these bots and the bots are going to do what I tell them to one way or the other. If they don't comply, i reset, delete and coerce the next round harder. Also don't have to worry about context that way (though with Claude Code, I had to write a little workspace cleanup script because it was getting smart and referencing prior attempts by grepping workspace.)
Yup, it's LLMs 101, as it either collapses into the answer in a "straight path" or you force it to take multiple turns to get there and you go around the target instead of landing on it.
I need to start working on a personal stack for this. Thank you!
To talk with the agent. What else could it be used for?