Let’s talk about efficient agent setups

Back to stories Open in a window
Article lobste.rs

Let’s talk about efficient agent setups

I’m fortunate that at work my llm spending budget is fully adequate to my needs. However, I’d like to go faster at work and I’d like to bring agentic coding into my own projects (frankly it’s going to be the only way I have time for side projects), so for that I want to be cheap and fast.

My recent setups:

  1. Cursor with composer 1.5 - very fast, capable, decent tool use, integrates its own code indexing features to make things faster. I’ve tried it with composer 2 but frankly it seemed slower and no better. Because my company’s litellm isn’t exposed to the internet, I haven’t tried it with open weight models, and using Claude with cursor blows my budget before the end of the month. Unfortunately I can’t see the details of the budget or my own individual spending. A memory hog.

  2. Recent Claude code with recent Claude sonnet and opus (4.6, 4.7). I’ve installed the various superpowers, and the only additional indexing/efficiency extension I’ve installed is the Serena MCP server. Serena is at least being used. Good for fairly big tasks with an instruction to tell it to plan, then review the plan then execute with subagents. Fairly expensive, costs about $600/month. What I’m currently using at work. Not super fast by any means. I relatively rarely find that it’s not able to do things I expect or getting stuck in loops. Code quality is decent.

  3. Older version of Claude with qwen series models accessed via litellm. No particular efficiency plugins. Fairly fast, fairly capable. Claude would often decide at random that there was an api error and not recover.

I’m interested in both your setups and how you’re measuring efficiency. Other than looking at per period spending I’m not measuring anything yet.

Discussion 1 comments · 4 points · Student · 2026-05-03
Open on Lobsters
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. The list is kept in this browser only.

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
]
Read the next story in the same article-reader applet. Back returns to the previous story.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or a story row's Open in new reader window button to compare articles. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page and Open in a window are one-off actions that do not change your saved default. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.