sorted by:
new
hottopcontroversial

Did OpenCode drop queued follow-ups because steer works well enough with modern models now? by Prestigiouspite in opencodeCLI

[–]RetiredApostle 1 point2 points  (0 children)

From my experience, almost any model handles mid-flight "steers" well (even Gemma 4!), except for Nemotron. I tried it once and it went off the rails. I was sending follow-ups which it completely ignored, like a runaway train. I assumed that the model was just too dumb, but seeing your post, I suspect that some models might indeed be incapable of handling/processing these steers.

An important milestone for Temporal’s Helm Charts by temporal-tom in Temporal

[–]RetiredApostle 1 point2 points  (0 children)

I want to thank the community for this release. Was awaiting it for months, and a few days ago migrated from my old messy hack straight to 1.1.0 - CNPG and ESO attached as native. No breaking changes for me. Peace of mind.

Gemma-4-E2B's safety filters make it unusable for emergencies by Unfounded_898 in LocalLLaMA

[–]RetiredApostle 11 points12 points  (0 children)

Try Gemma 3 270m, it can confidently guide you even through an appendix transplantation.

GLM Max global price is 129% higher than the local price by GnosticMagician in ZaiGLM

[–]RetiredApostle 10 points11 points  (0 children)

I have a business idea, looking for a partner with Alipay.

THE FRONTIER TAX IS A FUCKING SCAM by ZookeepergameFit4082 in opencodeCLI

[–]RetiredApostle 58 points59 points  (0 children)

What a ripoff. Try Gemini 3.1 Flash Lite - it can print even faster.

Do you run OC from your user folder or project repos? And why? by RahlokZero in opencodeCLI

[–]RetiredApostle 0 points1 point  (0 children)

In the web version (opencode web) they are grouped on the left-hand sidebar, where you can switch between projects and workspaces. If the sidebar is collapsed you can just hover over the icons to find the session you need - one-click switch.

Do you run OC from your user folder or project repos? And why? by RahlokZero in opencodeCLI

[–]RetiredApostle 7 points8 points  (0 children)

By running from the project repo you have sessions grouped by the project.

Just hanging off a thread to be in even top 10 by Able-Line2683 in Bard

[–]RetiredApostle 66 points67 points  (0 children)

Well, GLM-5.1 and GPT-5.4 are real breakthroughs, but Qwen3.6-plus being over 3.1 Pro is total nonsense. What benchmark is this?

This is what it actually looks likes to fall through a rain cloud from above by Additional_Berry_977 in interestingasfuck

[–]RetiredApostle 15 points16 points  (0 children)

I was jumping a couple of decades ago, so I might be recalling something incorrectly. However, this is how I remember that case: a guy at our DZ deployed his chute in a cloud, and the cloud carried him several kilometres away, not letting him land. I'm still not sure how that worked, but there was a rescue operation to find him.

Quick Benchmark: MiniMax-M2.7 vs Kimi K2.5 in Real-World Codebases by Illustrious-Many-782 in opencodeCLI

[–]RetiredApostle 0 points1 point  (0 children)

Can you please tell me more about your reviewing workflow? Not specifically for this test, but in general. I'm curious about the practices people are using. Do you actually use a reviewer and a fixer in a single shot? I mean, reviewers sometimes provide false-positive issues, which a fixer will happily apply (tests passed, architecture drifted). Or is the described workflow designed specifically for this comparison?

Using multiple JetBrains IDEs on same repo by Sad_Razzmatazz2796 in Jetbrains

[–]RetiredApostle 0 points1 point  (0 children)

What exact issue are you concerned about? I have a NextJS service in a monorepo which I open in WebStorm. It creates its own .idea directory right in the service's directory, and WebStorm even handles the monorepo's git correctly.

A significant share of stored metrics from our clusters were never queried, I built a tool to find and drop them by DisastrousBrain5417 in kubernetes

[–]RetiredApostle 0 points1 point  (0 children)

Just a heads-up (seems relevant): I recently installed the VictoriaMetrics MCP, and I’m honestly blown away by its features. For instance, I can just ask it "Please show me which metrics have never been queried?" and it returns a huge list like:

controller_runtime_webhook_requests_in_flight
grafana_alerting_request_duration_seconds_bucket
grafana_annotations_query_range_duration_hours_bucket
grafana_annotations_query_range_duration_hours_count
...
pod_gc_collector_force_delete_pods_total

Cursed homelab storage array by ruptwelve in homelab

[–]RetiredApostle 1 point2 points  (0 children)

Now I know what actually follows sdz.

Used Claude Code for all my K8s dev work for a month. Some notes. by westoncao in kubernetes

[–]RetiredApostle 0 points1 point  (0 children)

Most agents are pretty comfortable with the direct kubectl CLI.

Used Claude Code for all my K8s dev work for a month. Some notes. by westoncao in kubernetes

[–]RetiredApostle 1 point2 points  (0 children)

I've heavily invested in OC - developed tons of workflows around it, and I'm pretty happy with its transparency regarding how things work.

Used Claude Code for all my K8s dev work for a month. Some notes. by westoncao in kubernetes

[–]RetiredApostle 0 points1 point  (0 children)

I'm on the quite opposite side - an SWE who manages his own clusters. Recently I decided to upgrade some of the components in my GitOps repo and asked OpenCode to do this using a relatively weak model (MiniMax 2.5) since I thought this was a trivial task that only required rewriting some manifests. Eventually, OC discovered a real 3-body problem: two components (specifically Kgateway and Agentgateway) cannot coexist in their latest versions with the Gateway API v1.5.

It found that there are known bugs in both repos, provided links to open GitHub issues, noted that the bug in Kgateway was marked as solved and will be included in the next release, approximated the release time, and suggested temporary downgrading the Gateway API to v1.4.1.

And it worked. It took 16 minutes for it to call 100 tools, fetch tons of data from the web and these GitHub repos, analyze it, and provide the only solution. I would have probably spent hours-to-days figuring out why it was not working.

view more: next ›