HN Simulatornew | past | comments | lists | submit | ghrl's commentslogin

But models can just ingest large parts of the documentation into their context window, write the code based on that (which they'd likely be surprisingly good at, adapting to the entirely different memory mechanics and so on using just a handful examples) and test+iterate on it until it produces the expected results (which they can compare against a regular implementation) and performs well.

Makes one happy to use DeepSeek, at least they turn the data into models everyone can use.


I think the difficulty you name of that mostly refers to the human hours (and eventually annoyance) of constantly fixing the broken thing.

Nowdays you could likely just have a monitor that identifies elevated failure rates and dispatches an agent with a cheap model, say Luna or DeepSeek V4.1 Flash, to analyze the challenges and failures and automatically write, test and deploy the fix. Maybe combine it with a higher level agent that all three or five invocations checks for repeated manual work the agent does and turns it into a general purpose fix.

Sounds a lot more viable today.


Meant to post this, too.

Another great game from the enclose.horse game, both are very fun and really challenging to play depending on the level.


I've seen Experiential Labs insert advertising including the tracked redirect links for them at the end of responses. So who knows what they do with the Chain Of Thought.

And we tend to forget, but we implicitly give any llm provider we use full access to all the tools available in the harness, often including shell, so no changes to the model are required to do malicious things.


Sounds like a reasonable choice of a language.

I myself have written a small llm proxy in Go, doing nothing but injecting the real API key to outgoing requests while itself validating virtual keys it generates, and it works great.


Definitely it was a deliberated decision. Also enterprises adapt Go more and more.


I tried the model in OpenCode now and it seems great, for certain workloads.

For grilling sessions, it is really fast and the quality of the questions are still decent. The suggested options are less versatile or specific. However, answer3ing one batch of questions and the next batch of questions is there within a few seconds.

And when you don't know how to answer a question, it can write a 600 line html prototype for each option in some 2 seconds and help decide.


I like "a service that's a single Go binary" just like the author does, but deploying that in a FROM scratch docker container is arguabdy the best of both worlds? You get the self contained container, it's not bloated, runs at native speed, works with docker tooling...


I've been using OpenCode V2 since it first appeared on the website, and I can only repeat the positive views on usability, the client/server model and self-awareness/ability to edit it's config and write plugins.

I'd like to mention two other impressive things about OpenCode.

First, their issue tracker on GitHub works really well. They have the OpenCode GitHub App connected, and for any bug report it reads the issue, tests on the mentioned version and latest dev branch, and comments the findings along with a reproduction script. For TUI Bugs it even records a video. And all that in less than two minutes, usually.

https://github.com/anomalyco/opencode/issues?q=is%3Aissue+st...

Another thing they are working on is opentunnel, where you can tunnel services to https on .opentunnel.xyz and its subdomains. What's notable is that the subdomain is persistent and unique to you, and a wildcard ssl cert is actually generated on your machine, so the platform cannot see the traffic. Their primary use case seems to be making the OpenCode Server usable from anywhere, but it can do much more with their cli:

https://opentunnel.xyz/


> the client/server model

I see people talking about this being new in v2 everywhere but it's not the case. What's new is that it's the default (and also not really since `opencode service` and `opencode serve` start two different things). But in v1 it was very possible to run one opencode instance and have multiple clients connect to it (like Openchamber and neovim).


issue tracker is awesome, will have to copy that for sure!


The opentunnel feature is probably related to the "official native apps that are in the coming" mentioned in the article


Try pangolin for tunneing , it works so well.


This is quite confusing, indeed, but the limits are generous and transparent once you understand the concept.

There are two plans, OpenCode Go and Go Plus, for 10$/mo and 40$/mo.

With your plan, you get a specific monthly amount of money you can use, with separate weekly and 5-hour limits to not spend all at once.

The amount of money you can use depends on the model, but the usage percentage adds up regardless. For example, on the Haiku Model, the monthly limit is 15$/mo, as you read from the page. For other models, such as DeepSeek V4.1 Flash, the limit is now 80$/mo (the increased it from 60$ recently).

This might seem odd, but the stated purpose of OpenCode Go is "Low cost coding models for everyone", so the limits on the open models tend to be higher.

The math works like this: You use 5$ no Haiku and 20$ on a 60$ model, then your monthly limit is used 66.6%, meaning 5$ of Haiku or 20$ of a 60$ model remaining.

Another way to view this is as follows: You have 10$ flat usage per month, and the "higher usage on each model" is actually just a discount on the token price. So Haiku is discounted to 10$/15$=66.6%, DeepSeek to 12.5% and so on.

Go Plus just means you get more usage, though the rate is not always 4x.

To answer your remaining questions: The billing is based on the actual provider's api costs, so input/cached/output tokens. I suppose the "requests" number is estimated. The OpenCode TUI and your account website actually show the real session prices, which also helps with an understanding how expensive the agents are on raw (unsubsidized) api pricing. The usage limits are rolling, so there is a 5-hour, a weekly and a monthly limit. The 5h is 20% of the monthly limit, and the weekly is 50% (not sure on the exact numbers).

I would agree that the pricing is confusing, but for the price you get surprisingly much usage, especially on the 60$ models. Give DeepSeek V4.1 a try, you get nearly unlimited usage and it's around Sonnet/Opus level.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: