Top
Best
New

Posted by eggbrain 1 day ago

Ask HN: What's your current AI agentic setup?

I'm curious how people on HN are using AI day to day, and came up with a list of questions I thought could be interesting to know. No need to answer every question of course, just wanted to get a gut feel how people are using AI.

1) What AI subscriptions are you personally paying for? (Claude, ChatGPT/Codex, Cursor, etc)

- Which tiers?

- Have you purchased multiple subscriptions from the same provider (eg two Claude accounts)?

2) Are you using models outside (or instead) of those subscriptions? For example, pay-as-you-go APIs, OpenRouter, or locally hosted models.

- Which models and providers?

3) What coding harnesses and interfaces are you using? Are you sticking with the default CLIs or IDE integrations, or using alternatives like OpenCode, Pi, Aider, Muse Code, or custom-built harnesses?

- What made you switch harnesses (if you switched)?

4) Are you using any agent orchestration or swarm tools?

- For example, Munder Difflin, Gas Town, Ruflo, or something custom.

5) Are you using broader agent platforms like OpenClaw / Hermes Agent / Grok bot / Dots / Muse?

- If you are using them, what are your main use cases?

-----

I know my workflow has differed significantly from a year ago, and so it would be interesting to capture a snapshot today of what people are using and why.

525 points | 649 commentspage 21
tiffanyh 1 day ago|
My challenge is revisiting AI-gen code months later and making sure the AI has the context from our previous work.

How do people handle this?

Do you keep everything in the same conversation thread?

sheepscreek 1 day ago||
First off, I cannot pretend I have this solved. But I can share one thing that has worked for me, along with codex maintaining it's own local memory (turn it on).

Have your agent maintain a task journal. It is like a more detailed commit history, that includes tribal knowledge gained during the task and additional context, eg.

    X is incorrect but we cannot change it due to some other service depending
    on it, don't use Y as it is deprecated in favor of Z.
Reset your context frequently instead of only relying on compaction. Use the following prompt to summarize the current context for the new agent:

    Describe the current project or larger task in progress, then give a 
    breakdown of all the planned sub-tasks with status, explain any learnings,
    then note what work is remaining. Write this in a file called HANDOFF.md
Give it a try and feel free to share any improvements.
bottom999mottob 1 day ago|||
Try to keep context shoved in a conversation thread under a token limit to save tokens.

Ask AI to record in a projects directory memory: LOG.md, HANDOFF.md, DECISIONS.md, a plan folder. Reference code with absolute paths. Keep repeatable processes in skills. Version control it all, and use a dreaming process across multiple sessions to stop repeat mistakes.

That's what's worked for me, but there's many variations of this.

ehostunreach 1 day ago|||
> Try to keep context shoved in a conversation thread under a token limit to save tokens.

For big tasks/features, I'm always creating a new git worktree and I'm using a "status repo" skill that creates a sibling status git repository where everything is recorded.

It works quite well whenever I have to revisit something. It's quite token hungry but I have the full trace of what happened in the past.

https://gist.github.com/vkalintiris/3ad526e71a75bcba013aaadc....

Another approach I want to explore is using https://github.com/netdata/netdata (disclaimer, I work at Netdata) to send all OTel logs/traces of LLMs to it. The idea is to replace the status repo skill with something that will allow LLMs to retrieve the history of a given task/feature. It will probably require some "checkpointing" to make this more efficient.

sheepscreek 1 day ago||||
^ This is basically what I was getting at. Thanks for putting it so clearly mate.

> Try to keep context shoved in a conversation thread under a token limit to save tokens.

That is another solid tip. If using subagents, use the main thread for only the conversation + launching subagents. Tell it explicitly not to implement anything, and only support integration efforts.

Doing so keeps the worker subagent's context clean - so it can stay laser focused on the task.

tiffanyh 22 hours ago|||
Thank you.

Would you mind explaining what each file is, and how this works (do you create a skill such that AI is doing this on every prompt)

hypfer 1 day ago|||
You don't.

The context should be self-evident from the code alone, and if it is not, it should be in your head and you should write it down again so that you do not forget it yourself.

Being forced to re-explain stuff to the LLM is good, actually, as that way, one actually thinks about the architecture, choices and limitations.

mceachen 1 day ago|||
Have your agents keep contexts of tasks up to date as they work on stuff.

I've been iterating on this approach for about a year—it makes switching between agents and harnesses trivial.

https://photostructure.com/coding/claude-code-tpp/

coeneedell 1 day ago||
I usually have a “close out” routine that’s something like telling it to record hints to the project’s agents.md. It’s usually pretty good at figuring out what to save, and I usually set up the prompt to point the thing’s attention at the part of the process that made me most frustrated.
abstractcontrol 1 day ago||
Currently I am using the regular Claude extension with VS Code, but one of my friends is working on a new harness called NodeCode that doesn't require regular compaction, so I'll be trying it out as soon as I can get some time to do it: https://nodecode.ai/
woopsn 1 day ago||
For personal use: Claude Pro, Opus 5.5, occasionally API / usage credits. Outside of that, some smaller local models (lately poolside)

I still use emacs, I run agents in buffer or in different terminal tabs. I like pi but only claude is approved at work, so I mostly stick to that for consistency.

I'm use 1-3 agents at a time, not more than 2 on the same branch. I have some pipelined workflows but I don't run swarms.. I'm on budget!

gwbas1c 1 day ago||
1) What AI subscriptions are you personally paying for?

My employer pays for copilot, business plan. It also pays for Gemini.

2) Are you using models outside (or instead) of those subscriptions?

Gemini, company-wide. I mostly use it for general research, making clip art, and occasional programming questions / technical questions. I don't use it everyday, but when I use it, I really like it.

I no longer use ChatGPT or Claude's general-purpose chat bots.

3) What coding harnesses and interfaces are you using? Are you sticking with the default CLIs or IDE integrations, or using alternatives like OpenCode, Pi, Aider, Muse Code, or custom-built harnesses?

IDE integration with Visual Studio, and Copilot code reviews on Github. I mostly use agent mode; sometimes I use ask mode, and sometimes I use plan mode. (One very important thing is to instruct copilot, in .github\copilot-instructions.md, to only use its edit tool and not use Powershell to edit files. Otherwise you need to babysit it and approve cryptic find and replace commands.)

For Copilot in Visual Studio, I almost always use Claude Opus 5.5. Some of the GPT models "appear" to work well, but they leave the code harder to maintain.

We now do a round of Copilot reviews with our pull requests in draft mode before asking others to do the review; and we're not spending as much time "reading" code when looking at pull requests.

We don't (yet) have agents running unattended with high-level instructions and then making pull requests.

4) Are you using any agent orchestration or swarm tools?

No

5) Are you using broader agent platforms like OpenClaw / Hermes Agent / Grok bot / Dots / Muse?

No

------

One important thing: I'm after my boss to dedicate time (1-2 weeks) for me to set up and learn more of the hands-off tools. I love working with co-pilot, but it's best for work where I need to be hands-on. I really need to be able to offload simple work, or work where lower-quality results are okay, to a bot that I don't need to supervise.

_rousbound 17 hours ago||
I'm very happy right now with:

- DeepSeek Chat for reasoning about some idea

- DeepSeek Flash as pay-as-you-go API provider

- Maki as my harness

It is cheap, and I feel like it is a sustainable workflow, both financially and cognitively.

dustypotato 21 hours ago||
I have a custom frontend on my android running claude and antigravity CLIs with a UI built on top. Works surprisingly well. It's now about 40 % of my usage . I use it to apply for jobs automatically etc. and orchestrate stuff using adb
gitgud 21 hours ago||
I use

- opencode 2 as the harness it works well for pretty much any specific task

- openrouter to use deepseek flash 4.1 … insanely cheap, works amazingly well and fast

- orca as the orchestrator to manage all the work (self hosted). There’s a mobile app to orchestrate afk too

And yep, vscode to browse repos etc

ct0 21 hours ago||
One of those lenovo Mini pc running Ubuntu (plex server) that was just sitting idle. I installed tailscale and Claude code on it and run rclone with my Google Drive if I need to review docs on the go. I ssh into it from my iPad.
dismalpedigree 23 hours ago||
In the process of moving from claude code (opus 5.5 sub) to opencode with a custom sandbox system and using openrouter locked to certain models and providers with US data region requirements. Claude code is/was great. Just need to move due to industry regulations.
deathmonger5000 1 day ago|
I use Circus Chief to orchestrate workflows that use various combinations of Claude, Codex, Muse, z.ai, and Grok subscriptions. When one subscription runs out, Circus Chief falls back to the next. You can configure tiers to control how that works.

Full disclosure: I’m the creator of the project.

https://github.com/ferrislucas/Circus-Chief

More comments...