Live data from Hacker News

My Agent Setup

chad.cm

41–50 of 69 posts

Re: My Agent Setup

#41
post #33

Earlier quoted context omitted.

$48/month for the droplet (could probably be cheaper on Hertzner) and $100/month for OpenAI plan. so ~$150/month but again this could be cheaper with a different VPS and using Terra/Luna. I also have a claude max plan for coding but like I mentioned in the article coding is still separate from the agents.

[flagged]

ya i'm sure there are lower cost options. My droplet is 8 gigs mem which I found necessary for 6 agents.

Re: My Agent Setup

#43
post #9

Earlier quoted context omitted.

interesting.. does that bloat the context window? I imagine Hermes already struggles with context window size.. been meaning to look into that.

Couple of notes on this First, it matters how well the MCP is written; a well-written one won't be so massive Secondly, different sessions should load different MCPs. Load only what is needed Thirdly, if you're finding you need a dozen MCPs, you need to consolidate that into a single service that does the work and then presents a single, unified API (via MCP) to your agent Finally, start using models with 1M context…

ya all makes sense. hoping the harness can manage some of the MCP noise. I'm using 5.6-Sol so context window is 1M.

Re: My Agent Setup

#44

tried similar setups in the past, but messages is just not my jam, so built a html wrapper on top of claude code and open code that runs on a small-ish instance. looks like this https://i.imgur.com/lj9Fgco.png (screenshot anonymized with chatgpt) and allows multiple conversation per project, and has a few conveniences like scheduled tasks. one of the project in the list is the project itself, so I can add features wh…

Ya I'm starting to see that agents are just "input + llm + some memory + tools + lots of cron jobs".

Re: My Agent Setup

#45

I actually went down a different path and set it up so my friend and I can use the same agent with approval-gated turns. He's more technical than I am, but I believe I'm better at marketing. We can see both of our prompts and be on the same page. There is also a mode where we can branch off with our own agents. Watching his prompts made me better at producing my own and using the agent effectively.

That's neat. You could do this with Buzz by just having open room conversations with agents.

I checked it out, looks pretty cool. The tool I built is pretty similar, usepoly.co if you want to take a peek!

Re: My Agent Setup

#46
post #37

tried similar setups in the past, but messages is just not my jam, so built a html wrapper on top of claude code and open code that runs on a small-ish instance. looks like this https://i.imgur.com/lj9Fgco.png (screenshot anonymized with chatgpt) and allows multiple conversation per project, and has a few conveniences like scheduled tasks. one of the project in the list is the project itself, so I can add features wh…

That looks really useful You haven't put this on github have you?

No it is a vibecoded mess. Bet if you show the screen to a agent of your choice you will have yours in no time. The benefit is that if you give it self installing scripts you can just ask itself to add features

Cgroup and nice it so you never lose control of the machine tho

Re: My Agent Setup

#47
post #9

Earlier quoted context omitted.

interesting.. does that bloat the context window? I imagine Hermes already struggles with context window size.. been meaning to look into that.

Couple of notes on this First, it matters how well the MCP is written; a well-written one won't be so massive Secondly, different sessions should load different MCPs. Load only what is needed Thirdly, if you're finding you need a dozen MCPs, you need to consolidate that into a single service that does the work and then presents a single, unified API (via MCP) to your agent Finally, start using models with 1M context…

Do you not use any context pruning?
Post reply on HN