2026-07-31 13:20 GMT+8 · summary_2026-07-31_13-20.md
🤖 AI News Summary - 2026-07-31 13:20 GMT+8
Focused AI/dev subreddit roundup.
Full site: https://ai-news-summary.pages.dev/
What changed since last run
- Inkling-Small-276B-12B, effort “max” VS Qwen3.6-27B — r/LocalLLaMA
- I’ve been building runNburn: a Rust GGUF runtime for models that do not fit in fast memory — r/llmdevs
- cptr once again — r/OpenWebUI
- Thoughts on current state of tenancy — r/OpenWebUI
- Deep dive on OTel GenAI semantic conventions for agents, plus runnable Python/TS recipes — r/llmdevs
- Software Engineers: Do you honestly get anything useful out of LLMs? — r/LocalLLaMA
- Stop building AI systems without doing evals - here’s my setup — r/llmdevs
- Another victim of the SSO tax — r/selfhosted
- I had an idea for an airgapped file transfer mechanism — r/ClaudeAI
- Strange Requested Files (URLs) in the NGINX monitoring — r/selfhosted
- Claude thought I could be having a stroke. I was. — r/ClaudeAI
- Codex cheaper than ever — r/Codex
r/openai
| # | Post | Summary | Time | Score | Author | Community reaction |
|---|---|---|---|---|---|---|
| 1 | OpenAI Codex Charged Me Hundreds and Refused a Refund. I am also a teacher and dont get paid over the summer. Im so upset at myself. | I am a teacher, I was thrilled when I saw that Codex was a thing. I was using it heavily for the last week. | 2026-07-31 09:30 GMT+8 | /u/hexcodehero | Community reaction (frontier/gpt-5.4-mini): Commenters mostly questioned whether the charges were actually from Codex desktop credits versus the API, and one early reply suggested the screenshots were easy to misread and that the bill may have come from Codex auto-reload settings. The main technical takeaway was to inspect Codex payment settings, especially the monthly reload limit, because one user argued the non-auto reload path is hidden behind a plus button while the auto-reload flow is prominent and can keep charging until the card limit if the limit is left blank. There was also pushback that auto-replenish is not on by default, so the dispute centers on confusing UX and setup rather than an obvious platform bug. Overall sentiment — post: skeptical; author: skeptical. Reply threads: 2026-07-31 09:41 GMT+8: post=skeptical, author=neutral — They ask whether the screenshots are from the API account instead of Codex and whether the bill was actually… | 2026-07-31 09:42 GMT+8: post=neutral, author=neutral — They deny using the API and say the charges came solely from Codex on the desktop, while admitting they may… | 2026-07-31 09:50 GMT+8: post=skeptical, author=neutral — They say the shown limit applies only to the API and suggest the user likely enabled Codex Auto-reload… | |
| 2 | Price reduction for Luna and Terra!! | Advancing the price-performance frontier with GPT‑5.6 : https://openai.com/index/advancing-the-price-performance-frontier-with-gpt-5-6/ (https://openai.com/index/advancing-the-price-performance-frontier-with-gpt-5-6/) API pricing is $2 per million input tokens and $12 per million output tokens for Terra, $0.20 per… | 2026-07-31 01:29 GMT+8 | /u/Batman4815 | Community reaction (frontier/gpt-5.4-mini): The dominant reaction is enthusiastic: commenters say the Luna/Terra price drop is a big deal because it makes switching from 5.4 Nano or Mini to Luna/Terra viable for bulk summarization and other high-volume API workloads, with one user noting Luna would have been a 5x cost increase before this change. Several operators also report practical quality wins or adequacy at lower tiers, including Luna handling news TLDR and Microsoft Graph context well, while another notes that Luna High is enough for most day-to-day work and that Terra/Luna are also 50% off on OpenRouter (1$/6$). Overall sentiment — post: positive; author: neutral. Reply threads: 2026-07-31 01:43 GMT+8: post=positive, author=neutral — They call the price drop huge, say Luna would have been a 5x cost increase versus 5.4 Nano for summarization,… | 2026-07-31 10:14 GMT+8: post=positive, author=neutral — They say they switched from 5.4 Nano to 5.6 Luna in a news TLDR app, prefer Luna so far, and think its… | 2026-07-31 07:06 GMT+8: post=positive, author=neutral — They add that Max is often unnecessary and that Luna High is good enough for most day-to-day work. |
r/LocalLLaMA
| # | Post | Summary | Time | Score | Author | Community reaction |
|---|---|---|---|---|---|---|
| 1 | Inkling-Small-276B-12B, effort “max” VS Qwen3.6-27B | [Image: Inkling-Small-276B-12B, effort “max” VS Qwen3.6-27B] I saw u/danielhanchen ()’s 1-bit Kimi K3 post: https://huggingface.co/unsloth/Kimi-K3-GGUF/discussions/12#6a6a4a90ec74ef13d85d7cf6 (https://huggingface.co/unsloth/Kimi-K3-GGUF/discussions/12#6a6a4a90ec74ef13d85d7cf6) and decided to test Inkling-Small and… | 2026-07-31 07:58 GMT+8 | /u/lilian_moraru | Community reaction (frontier/gpt-5.4-mini): The dominant reaction is that the comparison is not apples-to-apples because the two models are being run at different quantization levels, with commenters calling out Q2 Inkling versus a higher-quantized Qwen 27B and noting that the post omits Qwen’s quantization in the main writeup. A minority argues the setup is still fair for DGX Spark–class RAM limits because heavier quants would not fit, while others add the broader operator caveat that heavily quantized models may carry more “knowledge” but tend to fall apart on coding, math, and long-horizon context due to accumulated error. One commenter also says one-shot tests are not representative of real usage, and another clarifies that Qwen 3.6 27B being widely tested does not mean the model itself has changed. Overall sentiment — post: skeptical; author: skeptical. Reply threads: 2026-07-31 08:36 GMT+8: post=critical, author=skeptical — They argue the post is not a fair capability comparison because it pits Q6 27B active Qwen against Q2 12B… | 2026-07-31 08:38 GMT+8: post=mixed, author=neutral — They specify using Q2_K_XL, which keeps sensitive layers at higher precision, and note that heavily quantized… | 2026-07-31 10:13 GMT+8: post=positive, author=neutral — They defend the comparison as practical on a RAM-limited DGX Spark, saying higher-than-Q2 quants for Inkling… | |
| 2 | Software Engineers: Do you honestly get anything useful out of LLMs? | For 6 months now I’ve been trying to make agentic coding work for me, using Pi and a handful 30-120B models (Qwens, Nemotrons, Leguna…etc). I’m not greedy either, I stick to decent quants, never quantize kv cache, and keep my sessions up to 90k max. | 2026-07-30 22:37 GMT+8 | /u/ParaboloidalCrest | Community reaction (frontier/gpt-5.4-mini): Commenters mostly answer yes: local LLMs are described as genuinely productivity-improving when used with discipline, and Qwen3.6 27B is repeatedly called the current consumer-hardware winner, with 35B-A3B as the fallback if 27B is too slow. The shared operator guidance is to cap sessions around 100k-150k context, restart often, attach the relevant files, think through the implementation yourself, and lean on embedded documentation such as docstrings and module comments; the main caveat is that harness quality matters a lot, because Claude Code can make Sonnet or even Qwen look stronger in code review, albeit with higher latency. Overall sentiment — post: positive; author: neutral. Reply threads: 2026-07-30 22:52 GMT+8: post=positive, author=neutral — Says local LLMs have improved their productivity and recommends Qwen3.6 27B or 35B-A3B, keeping context… | 2026-07-30 23:42 GMT+8: post=positive, author=neutral — Agrees with the step-by-step workflow, says Qwen models feel intelligent enough to prefer over Claude Haiku,… | 2026-07-31 04:11 GMT+8: post=mixed, author=neutral — Says Claude Code is the real advantage for Sonnet, reports Qwen3.6 27B in Pi with a tweaked prompt scoring… |
r/llmdevs
| # | Post | Summary | Time | Score | Author | Community reaction |
|---|---|---|---|---|---|---|
| 1 | I’ve been building runNburn: a Rust GGUF runtime for models that do not fit in fast memory | I used an LLM to turn my own development notes and benchmark records into English and to edit the wording. All technical claims and measurements are from my project records. | 2026-07-31 11:42 GMT+8 | /u/coderyeon | ||
| 2 | Deep dive on OTel GenAI semantic conventions for agents, plus runnable Python/TS recipes | I went down a rabbit hole trying to actually understand how you instrument an LLM agent with OpenTelemetry, instead of pasting a snippet and hoping. Wrote it up, and put the runnable versions in a public repo (Python and TypeScript), because most guides stop at “install the instrumentor”, which is roughly where the… | 2026-07-31 04:39 GMT+8 | /u/frisbeema52 | ||
| 3 | Stop building AI systems without doing evals - here’s my setup | [Image: Stop building AI systems without doing evals - here’s my setup] I run a bootstrapped company (5 of us in total) and we have a number of products that sit on top of our RAG pipeline. I wanted to run through the setup/approach we’ve taken with evals, as I tend to see a lot of folks struggling with (or skipping)… | 2026-07-30 18:12 GMT+8 | /u/TheRedfather | Community reaction (frontier/gpt-5.4-mini): Commenters converged on keeping evals deterministic with a frozen golden set and regression tests, with retrieval metrics like recall, MRR, F1, and coverage treated as more important than generation wording for RAG quality. The main caveat was to avoid AI judges because they add another flaky validation layer and are hard to tune, while routing stayed deliberately boring: fixed cheap models for ingestion steps, user-selected chat models for answering, and only limited concern about context bloat, compaction, and occasional re-embedding when the corpus changes. Overall sentiment — post: positive; author: neutral. Reply threads: 2026-07-30 20:33 GMT+8: post=positive, author=neutral — They argue that avoiding AI judges is underrated because it adds a second flaky system on top of the thing… | 2026-07-30 20:46 GMT+8: post=positive, author=neutral — They agree that AI judges are hard to tune and point to “Who Validates The Validators” (arXiv:2404.12272) as… | 2026-07-30 18:52 GMT+8: post=positive, author=positive — They describe a deliberately non-dynamic routing setup with fixed cheap models for vision extraction,… |
r/OpenWebUI
| # | Post | Summary | Time | Score | Author | Community reaction |
|---|---|---|---|---|---|---|
| 1 | API Keys section on the latest openweb-ui ? | Hi , Anyone know where the api key section is? I cant seem to find it at all EDIT : sorry all! | 2026-07-30 10:07 GMT+8 | /u/Tasty-Picture-8331 | Community reaction (frontier/gpt-5.4-mini): Commenters converged on a permissions/configuration cause rather than a missing UI bug: one noted you need a role with the “create api key” right assigned to the user, another suggested checking whether the setting was in admin settings, and the OP ultimately confirmed it was turned off in auth settings. The thread is mostly troubleshooting with mild confusion, because several replies simply say they could not find the section or that it was “weird,” but there is no real disagreement about the root issue once the OP found it. Practical takeaway for operators: if the API key section disappears in Open WebUI, check role grants and auth/admin settings before assuming a broken build. Overall sentiment — post: neutral; author: positive. Reply threads: 2026-07-30 10:52 GMT+8: post=positive, author=neutral — They offered the concrete fix that a role must have the “create api key” permission and then be assigned to… | 2026-07-30 16:20 GMT+8: post=positive, author=positive — The OP confirmed the issue was caused by the API key feature being disabled in auth settings and apologized… | 2026-07-30 10:47 GMT+8: post=neutral, author=neutral — They said the missing API key section seemed weird but had no explanation for why it was absent. | |
| 2 | cptr once again | Ok, so I read about cptr once again. If I understand it correctly, it’s a glorified terminal with your own data that you can communicate with and it communicates back. | 2026-07-31 01:03 GMT+8 | /u/Fun-Purple-7737 | Community reaction (heuristic-fallback-bad-json): The comment section is split between positive and skeptical. Top reactions focus on You’re describing open terminal. Not sure about cptr as I haven’t used it but what you just said is open terminal | no. I am using Open terminal. Open terminal is a tool like any other.. only with terminal inside.. Overall sentiment — post: mixed; author: mixed. Reply threads: 2026-07-31 01:05 GMT+8: post=mixed, author=mixed — You’re describing open terminal. Not sure about cptr as I haven’t used it but what you just said is open… | 2026-07-31 01:20 GMT+8: post=mixed, author=mixed — no. I am using Open terminal. Open terminal is a tool like any other.. only with terminal inside. | 2026-07-31 01:38 GMT+8: post=mixed, author=mixed — It’s a full blown Linux operating system - so it’s actually thousands of tools. | |
| 3 | Quick way to stop all users from being able to chat? | Note: I am not on the newest update of OWUI yet. I’m looking for a very quick way to disable chatting as a whole for user groups. | 2026-07-30 02:27 GMT+8 | /u/NoobLLMDev | Community reaction (frontier/gpt-5.4-mini): The thread converges on there being no built-in Open WebUI toggle to stop chat wholesale, so the practical workaround is to revoke a group’s model access or, if you need fast switching, use an event function or separate connections/deployments. The main caveat is that this approach typically surfaces a “model not found” error rather than cleanly hiding custom assistants, and splitting into a second connection only helps if your demo and private usage are actually isolated; if they share the same deployment instance, toggling one affects the other. A softer suggestion was to add a home-page banner like “model maintenance underway,” but that is framed as a UX warning rather than a true access control fix. Overall sentiment — post: positive; author: positive. Reply threads: 2026-07-30 02:33 GMT+8: post=positive, author=neutral — They say there is no built-in toggle, recommend removing the group’s permission to access the model on… | 2026-07-30 02:48 GMT+8: post=positive, author=positive — They confirm the permission-based workaround works for their use case, but note it shows a model-not-found… | 2026-07-30 14:29 GMT+8: post=mixed, author=neutral — They suggest cloning the first connection into a second one so you can toggle demo and normal usage by… | |
| 4 | Thoughts on current state of tenancy | In my environment tenants are a big deal, we work collaboratively but separately, due to institutional/legacy reasons. As such there’s a ton of shared, and a ton of separate, and we have to try to accommodate for all of it. | 2026-07-31 02:12 GMT+8 | /u/DHT-Osiris | ||
| 5 | Thoughts on my workflow? | I’m working on a document ingestion engine in n8n that will archive documents and create an index in Postgres. I plan on making cron jobs for Hermes to read all new documents and update a summary md file for each project. | 2026-07-30 07:25 GMT+8 | /u/SadPhilosophy9202 | Community reaction (frontier/gpt-5.4-mini): The commenter argues the workflow is overcomplicated and recommends replacing n8n, Hermes cron jobs, and Postgres with a single folder-added trigger that writes the markdown summary directly. They also question the document-to-project boundary and suggest the real operator concern is defining when documents expire or are considered “done,” with Postgres only justified if it is truly serving as an index. Overall sentiment — post: critical; author: neutral. Reply threads: 2026-07-30 16:50 GMT+8: post=critical, author=neutral — They say the design has too many tools, recommend a simpler folder-triggered write path, and question why… |
r/selfhosted
| # | Post | Summary | Time | Score | Author | Community reaction |
|---|---|---|---|---|---|---|
| 1 | Another victim of the SSO tax | Yet another interesting project falls victim to the SSO tax: bichon. As a long time open source contributor, I totally understand wanting to get some money back, but for… | 2026-07-31 05:38 GMT+8 | /u/kernald31 | Community reaction (frontier/gpt-5.4-mini): Commenters mostly agree that asking self-hosting users to fund projects through donations or subscriptions is a poor fit, with one calling high-default donation prompts “delusional” and another saying lifetime pricing only works if all features stay included, citing AMP and Filerun as examples. The main disagreement is economic: a former maintainer argues that losing unpaid users is not very important for popular FOSS projects because companies routinely expect free work, lowball custom module pricing, and still return after threatening to switch; the few off-topic replies are just a typo correction and a joke. Practical takeaway for operators is that premium SSO or other gated features are likely to keep surfacing in open-source tools, and maintainers may prioritize paying customers or paid modules over retaining free users. Overall sentiment — post: mixed; author: neutral. Reply threads: 2026-07-31 06:07 GMT+8: post=critical, author=neutral — They say the advice to ask for donations with fairly high default amounts is “fucking delusional” and reject… | 2026-07-31 06:17 GMT+8: post=critical, author=neutral — They argue the self-hosting community is the wrong place for subscription models and say lifetime licenses… | 2026-07-31 06:40 GMT+8: post=skeptical, author=neutral — They say that for a project with about 80k users and 10k GitHub stars, losing non-paying users is not a major… | |
| 2 | Strange Requested Files (URLs) in the NGINX monitoring | [Image: Strange Requested Files (URLs) in the NGINX monitoring] Hello everyone. I have a self hosted internet facing server with nginx. | 2026-07-31 04:25 GMT+8 | /u/PizzaDevice | Community reaction (frontier/gpt-5.4-mini): The commenters largely agree that the strange NGINX URLs are just bot/probe traffic hitting an internet-facing server, with several saying this is normal background noise and that 404-heavy logs usually do not mean anything was actually served. The practical advice is to look at response codes and request volume, ignore or suppress routine 404 logging, and use defenses like TailScale/HeadScale for private access, fail2ban, or iptables/SYN filtering; one caveat is that repeated hits or successful responses deserve investigation, and one commenter notes LLM scrapers are now part of the noise. Overall sentiment — post: neutral; author: neutral. Reply threads: 2026-07-31 04:40 GMT+8: post=neutral, author=neutral — They say the odd requests are bot traffic and that this will make up the majority of traffic received by a… | 2026-07-31 04:59 GMT+8: post=neutral, author=neutral — They warn that trying to explain every weird request will drive you crazy, recommend putting home services… | 2026-07-31 08:07 GMT+8: post=neutral, author=neutral — They explain that the random files are usually automated probes for known paths, and advise checking response… |
r/ClaudeAI
| # | Post | Summary | Time | Score | Author | Community reaction |
|---|---|---|---|---|---|---|
| 1 | I had an idea for an airgapped file transfer mechanism | [Image: I had an idea for an airgapped file transfer mechanism] I’ve been using Claude Code to build a cached web app MP3 player (got really tired of online music streaming quality, and ads). I wanted to try adding a phone to phone file transfer option without requiring the phones to be on the same network, when I… | 2026-07-30 23:10 GMT+8 | /u/Alstroph | Community reaction (frontier/gpt-5.4-mini): Commenters largely agree the flashing-QR airgap transfer is a neat implementation but not a new idea, with multiple people citing earlier versions or similar tech and one saying the thread feels like a “Simpsons did it” case. The main caveat is semantic: some question whether it is truly “airgapped,” while others say novelty matters less than speed and robustness, especially for single-user or niche workflows where AI makes it easy to build tools that fit one need exactly. Overall sentiment — post: mixed; author: neutral. Reply threads: 2026-07-31 00:18 GMT+8: post=skeptical, author=neutral — They argue the idea was already done and note that someone beat OP to it two years earlier. | 2026-07-31 00:19 GMT+8: post=positive, author=neutral — They say they have seen several similar examples already but still think the project is pretty cool. | 2026-07-31 01:01 GMT+8: post=mixed, author=neutral — They warn that AI will create many duplicate internal tools at work, but also say it is valuable because… | |
| 2 | Claude thought I could be having a stroke. I was. | [Image: Claude thought I could be having a stroke. I was.] Working talk to text, I found I couldn’t speak to Claude properly, couldn’t think of words, then saying complete gibberish instead of the word I was looking for. | 2026-07-30 22:32 GMT+8 | /u/loosepantsbigwallet | Community reaction (frontier/gpt-5.4-mini): Commenters overwhelmingly agreed that the post describes a real emergency where Claude served as a useful fallback when speech and word-finding failed; they repeatedly cited anosognosia as the reason stroke victims may not recognize what is happening, making OP’s instinct to keep interacting with the bot and seek help seem logical and potentially life-saving. The only notable disagreement was a small set of downvoted critics calling the situation “insane,” but the thread mostly pushed back with anecdotes about strokes causing bizarre perception, unintelligible speech, and lost limb awareness. Practical takeaway for operators: an always-available text/chat interface can be a low-friction escalation path when voice or cognition breaks down, though the discussion also drifted into ambulance-cost and joke tangents. Overall sentiment — post: positive; author: positive. Reply threads: 2026-07-30 23:12 GMT+8: post=positive, author=positive — The auto-generated mod summary says the thread’s consensus was that Claude was a good bot and OP did the… | 2026-07-30 22:40 GMT+8: post=positive, author=positive — This commenter reinforced the stroke/anosognosia explanation and told OP to ignore the critics, framing the… | 2026-07-30 22:55 GMT+8: post=positive, author=neutral — They shared a personal anecdote about a friend believing his arm had fallen off during a stroke to illustrate… |
r/ClaudeCode
| # | Post | Summary | Time | Score | Author | Community reaction |
|---|---|---|---|---|---|---|
| 1 | Is Anthropic cooked ? | [Image: Is Anthropic cooked ?] Codex limits are going to be crazy now. What do you guys think, why did they drop the prices ? | 2026-07-31 02:27 GMT+8 | /u/Odd-Card8046 | Community reaction (frontier/gpt-5.4-mini): Commenters mostly treat the price cuts as a competitive move rather than evidence Anthropic is failing, citing a WSJ report that OpenAI was considering similar cuts and noting that the lower-end model prices moved while Sol stayed unchanged. The main disagreement is whether this points to an imminent Haiku 5 launch or a Haiku retirement/discontinuation, but several users independently speculated that Anthropic is getting ahead of a smaller/faster model release. Practical operator takeaways are to watch subscription promos and usage windows like the 50% extra-usage offer and 5h limits, because users want those concessions to stick, yet the whole pricing landscape feels volatile and tied to broader financing pressure. Overall sentiment — post: mixed; author: neutral. Reply threads: 2026-07-31 02:47 GMT+8: post=mixed, author=neutral — They cite a WSJ report that OpenAI was anticipating similar Anthropic cuts, argue competition is good but the… | 2026-07-31 03:49 GMT+8: post=positive, author=neutral — They hope Anthropic keeps the 50% extra-usage promo on subscription, even if it remains limited for Fable,… | 2026-07-31 03:09 GMT+8: post=mixed, author=neutral — They think the lower-end price cuts are odd because Sol stayed the same, and speculate that Anthropic either… | |
| 2 | Opus 5 Is good | [Image: Opus 5 Is good] Must say I am impressed, he does this all day. | 2026-07-31 09:41 GMT+8 | /u/Mayimbe_999 | Community reaction (frontier/gpt-5.4-mini): Commenters do not really back the post’s praise of Opus 5; the dominant reaction is concern that it is missing basic validation and assumptions, with one user saying they now need guard scripts to confirm a probe label exists in an index/list before running, and another saying Codex had to correct multiple assumptions made by Opus. A smaller counterpoint is that some heavy 20x users say they have not seen the issue at all, and one commenter interprets the behavior as deliberate double-checking against false positives, but several others still describe Opus 5 as tripping, prefer 4.8/Fable, and say they are waiting for a fix. Overall sentiment — post: critical; author: neutral. Reply threads: 2026-07-31 09:47 GMT+8: post=critical, author=neutral — Says teams now need check scripts to ensure a probe label exists in an index/list before running or to reject… | 2026-07-31 10:41 GMT+8: post=neutral, author=neutral — Interprets the output as a test that intentionally imported a non-existent probe module and wonders whether… | 2026-07-31 09:50 GMT+8: post=neutral, author=neutral — Says they regularly use 100% of their weekly credits on the 20x plan without running into the reported issue,… |
r/Codex
| # | Post | Summary | Time | Score | Author | Community reaction |
|---|---|---|---|---|---|---|
| 1 | Codex cheaper than ever | [Image: Codex cheaper than ever] https://preview.redd.it/5xjxq3xlmegh1.png?width=593&format=png&auto=webp&s=f60deb306b3fce67245cc2e41aa3e59e16014556 (https://preview.redd.it/5xjxq3xlmegh1.png?width=593&format=png&auto=webp&s=f60deb306b3fce67245cc2e41aa3e59e16014556) What do you think? | 2026-07-31 01:46 GMT+8 | /u/New-Bus6938 | Community reaction (frontier/gpt-5.4-mini): The thread’s practical consensus is that lower price is welcome only if it comes with enough tokens and usable reset mechanics: multiple commenters joke about needing more banked resets, while others worry that an expiring banked reset or a new 5h cap would erase the benefit. One concrete operator datapoint is that Luna is described as 5x cheaper and ‘90% as good as Terra’ for a data extraction agent, so at least one user sees enough quality at this price to call it a no-brainer. Overall sentiment — post: mixed; author: neutral. Reply threads: 2026-07-31 01:58 GMT+8: post=positive, author=neutral — They argue that if Luna is 5 times cheaper, it should also come with 5 banked resets, framing the price cut… | 2026-07-31 13:24 GMT+8: post=concerned, author=neutral — They say their banked reset expires tomorrow and warn that another reset paired with a 5h limit would leave… | 2026-07-31 04:01 GMT+8: post=mixed, author=neutral — They report still not dropping below 70% usage even with resets, but note that two banked resets will expire… | |
| 2 | OpenAI cuts GPT-5.6 Terra and Luna prices | [Image: OpenAI cuts GPT-5.6 Terra and Luna prices] Luna by a lot Terra by a decent amount Sol the same EDIT: Official blog post: https://openai.com/index/advancing-the-price-performance-frontier-with-gpt-5-6/… | 2026-07-31 01:09 GMT+8 | /u/BigbyWolf8 | Community reaction (frontier/gpt-5.4-mini): Commenters are broadly enthusiastic about the price cut, with multiple people saying Luna is now cheaper than GPT-5.4 nano and even below the already-discounted OpenRouter price, which they call “crazy” or “insane” given the model quality. The practical operator takeaway is that Luna may now be a realistic replacement or successor for 5.4 Nano, so at least one user plans to run evals against their 5.4 Nano workload, while another says Luna at xhigh feels comparable to Terra at Medium in Hermes and could stretch a $20 budget further. A small side thread focuses on workflow, with users discussing xhigh/max reasoning settings and a plan/review split where Sol writes the plan and Luna implements it, after a correction of the initially reversed roles. Overall sentiment — post: positive; author: neutral. Reply threads: 2026-07-31 01:12 GMT+8: post=positive, author=neutral — They say the cut is even bigger than the one already seen on OpenRouter, and note that Luna now costs less… | 2026-07-31 01:48 GMT+8: post=positive, author=neutral — They argue Luna is basically the successor to GPT-5.4 Nano, say the old 5x price gap made no sense, and plan… | 2026-07-31 01:50 GMT+8: post=positive, author=neutral — They report that Luna at xhigh is comparable to Terra at Medium in Hermes for their use case, which would… |
Generated 2026-07-31 13:20 GMT+8 | Next update in 2 hours