I remember there were multiple such websites before being shared in HN. I bookmarked them, and a couple years later when I finally wanted to find a book, the only thing I got is 404.
I hope this one lives longer.
It would be interesting to see how many times this same project has been done because I feel like I was seeing it at least once a month for years.
The book recommendation aggregation website is so common because it’s one of the few variations of this theme that can be monetized through affiliate links.
None of them last long because the traffic falls to zero basically as soon as it falls off the front page.
That's why to build things as a static site generator, and then the result of that effectively needs no further maintenance, and only costs whatever the domain costs.
Makes it much more viable to keep such experimental things online "forever".
The background task / subagent feature and the ability to specify a model when starting a subagent are so far my favorite improvements. Small things but make huge QoL difference in everyday development.
Whenever I start checking a dump, the conversation with Sol won't last five rounds before it flags the work as cybersecurity-related. No matter what I do, the conversation gets cut off in the middle.
Astra is even worse. It starts saying nonsense and even refuses to run a test that we know will cause an AV (as a repro for a nullptr case).
Whenever that happens, I just switch to Opus to continue my work.
I double checked the publish date before writing down this comment. Because I use the same harness (Opencode, to be specific) as the author, and some of the features are just right there. Like opencode can start multiple subagents for different tasks in parallel. Also I usually ask the main model (e.g. opus 5.5) to pick subagent models for me, and it has no problem identify the difficulty of work and delegate large portion of them to gpt-luna.
I didn't want to complain about OpenCode too much because it's open-source and kind of the scrappy underdog to Claude/Codex, but I do find its multitasking support pretty limited. I have to specifically remind it to spin up subagents, and when it does, it'll do 2-3 tasks in parallel and then wait until all of them finish. It can't seem to inspect tasks in progress, and if a subagent dies or hangs, the main agent can't seem to retrieve any information from it, even though I as the human can look at the session and see what happened.
Are you doing anything special to make OpenCode multitask well?
I'm using opencode v2, if it matters.
I don't have any special skills / prompts for subtasks. Instead, I found new models (I usually have sol or opus as my main model) have the tendency to trigger subtasks, even to a level I need to ask it "please do this task XYZ yourself". The only special prompt I gave is just something like "please use gpt sol or luna for subtasks, base on your judgement".
And in my experience it can handle more than 5 async subtasks out of the box
I'm confused about opencode's v1/v2 split. The docs say v2 is here, but their Github is only v1.x.[0] And the docs don't really explain why v2 is better, but there's a long list of things I have to do to migrate,[1] so I haven't been that eager to pull the trigger, especially since I can't tell if they consider it alpha/beta/release.
If you use Nix it's a flake so super easy to run too.
Seconded that v2 has much better background shell + subagent management: it's now much more eager to appropriately spawn either of them on its own, and does so in a way that is asynchronous, i.e it doesn't block the conversation and you can examine them by pressing down arrow at the prompt box.
I am curious: Why is it bad to merge chat and work? In Claude I didn't have a porblem with it (although I switched to an OpenAI subscription shortly after they made the merge). Isn't the model capable of deciding if it needs the extra capabilities of Work?
Which is probably why they will merge it. You can get a lot done in chat mode, especially if you connect custom MCPs to it. I can't see that continuing.
Pro messages is like 50 per week for pro 100 and 200 for pro 200.
Regular chat, even on extra high thinking mode, is sort of unlimited. Idk at what point you hit the abuse gaurdrail but its really high whatever it is.
For a company with Open in the name, OpenAI is very opaque about things, there are all kinds of limits and quotas that randomly come and go, but they only show you the meters for a couple.
E.g. codex reviews come from codex quota but also has its separate quota they don’t tell you about. Same with security reviews which has another quota still.
So the chat messages can be sent at several effort levels and from various models including 5.6 and 6 pro. The 6 pro messages are limited and they don’t tell you how many you’ve sent or how many are left. But the 5.6 messages seem to be unlimited, however there could just be a much higher unstated quota.
It's insane how hard OAI is choking, they had much better models than A/ who were fumbling this year to date... then blunder after blunder.
The only things that OAI still have over A/ are better coding agent GUI, no 5hr limit on >$100, much more reasonable cybersec guardrails (that allow most RE work) and... that's it.
reply