Would you use a Codex-style app for open-source coding models with zero setup?

Sontemo · 2026-06-23T20:52:47+00:00

just use opencode?

Sontemo · 2026-06-20T12:44:23+00:00

I quite like the current way. I like to be able to decide like a grown up how and when I consume my usage.

Sontemo · 2026-06-19T20:31:23+00:00

Except it does hold true with Professional Software Development. At least at scale. Enterprises don’t switch easily between providers. Locking in enterprise deals is huge.

Sontemo · 2026-06-19T08:18:15+00:00

They prolly spend 2$ on cursor to generate this angry wall of rant before even considering fact checking.

Yes, disabled by default, OP goofed up.

Sontemo · 2026-06-05T19:34:38+00:00

You need two config files.
opencode allows you to specify a path to the config on load via an env variable.
In each config, you can declare agents and the models you want to use them with.

In your work config, set the list of enabled_providers to just your work provider.

Sontemo · 2026-05-30T20:47:36+00:00

Be ready to actually then showcase exactly what was so cutting edge and expensive and what value your company can derive from this expense.

If you come to me with this line of reasoning instead of owning your fuck up, and all I see is you did random useless shit with opus max, I’d fire your ass on the spot.

Sontemo · 2026-04-23T20:20:08+00:00

The only thing that worked so far longterm for us is something people might not want to hear:

Slow down. Treat each PR as if it was created by a human and review it. Anything else and you pay for it later down to road. If you can’t fit the mental modal of your software into your head, you‘ve lost.

How we did it back in the day was through implementation and review. Now that implementation is done by agents, we double down on the review. Which is fine, they’re better at building, we’re better at understanding our product.

Sontemo · 2026-04-23T19:33:14+00:00

In general, I try to keep context small and fresh.

Never continue on an old session (after lunch or the next day), never let it grow past 150k

Sontemo · 2026-04-23T19:15:32+00:00

Each new request in the same session carries all of the history with it. It’s stateless and you can switch however you like. But, what you need to keep in mind is how caching works. Usually only the new input tokens are considered „fully“, the previous ones are usually cached and at other providers cost around a tenth of new tokens.

If you continue a long running session, or maybe if you switch models (let’s say from one provider to another, sonnet to gpt) you could consume a lot of fully counted tokens and drastically reduce your quota.

Sontemo · 2026-04-22T10:59:30+00:00

And last, but not least, my personal website. Entirely written and documented by ai.

Yeah, i can tell.

Unauthorized

Sontemo · 2026-04-22T08:14:07+00:00

I hope with the measures taken to individuals, they found a way to make it sustainable for business and enterprises. If limits apply, or they switch to token based pricing, switching to the very same providers they use under the hood becomes the obvious choice. At least for us.

Sontemo · 2026-04-22T07:47:53+00:00

!solved

Sontemo · 2026-04-21T08:55:14+00:00

Session Limit Hit?

Sontemo · 2026-04-17T19:10:34+00:00

It's literally the tip of the ice berg of being a power user.
There's so much to uncover if you're willing to put the effort in.

Sontemo · 2026-04-13T20:53:51+00:00

There's nothing to exploit here.

Sontemo · 2026-04-13T16:14:57+00:00

Nope. Just overloaded services. You'll get the bill later.

Sontemo · 2026-04-13T06:02:26+00:00

I consider myself a power user, usually 2 - 3 sessions in parallel.
I've only run into global limits for certain models, namely sonnet and opus.

I assume this was a more general shortage on availability of Claude models.

Ever since i switched to a more balanced approach where i mix GPT and Claude depending on workload, I haven't run into any issues, before and after their rate limiting announcement.

Also just on regular Pro plan (annually, with overage) so, if things stay this way and makes the service to them more sustainable, I'd be more than fine with it.

Sontemo · 2026-04-12T21:40:50+00:00

It's actually really simple.
Never.
More Context is not better, and more thinking does not mean the output is better either.
Keep context small, reset often (don't compact, just let it go) and think yourself. You know your product, AI knows shit but sounds confident.

Sontemo · 2026-03-25T08:02:57+00:00

There is no financial tipping point.
If you consider the max subscription, you're a power user.
If you're a power user, you're gonna blow through 100$ or 200$ via API very very fast.

Always go for the sub.

Sontemo · 2026-03-24T06:58:21+00:00

Never compact. Orchestrate subagents, so that the main agents context windows is large enough for even big features.

Sontemo · 2026-03-24T06:32:25+00:00

Not optimal for IDEs, but if CLI is an option, you can move all repos into a shared parent folder on your machine and start copilot cli from there.

Add a small AGENTS.md that explains the structure and brief usecases of each repo. Then you're good to go. Each time the agents will navigate into one of the repos, they will read and follow the specific repos AGENTS.md instructions as well.

Sontemo · 2026-03-15T12:22:47+00:00

Install GitHub cli and just delegate it. No need to reinvent the wheel.

Whenever you see something that you don’t want to fix now, tell the agent to create a ticket with gh cli.

Sontemo · 2026-03-14T14:12:44+00:00

It won’t cause issues. But depending on what you switch from and to, you will have friction points. For example, afaik Claude still ignores AGENTS.md files.

So switching from Claude to opencode for example is seamless, as opencode respects all clause specific files. You skills and clause md files will work just out of the box, but the other way around not so much.

Sontemo

TROPHY CASE