Reddit AI Coding - 2026-10-07¶
1. What People Are Talking About¶
1.1 Cost, quota burn, and model routing became the main workflow language 🡕¶
The highest-signal evidence was no longer about a single "best" coding model. It was about what different models cost, how quickly weekly limits disappear, and which routing choices still make economic sense. At least six strong items supported the same shift: AI coding users are now treating pricing, cache behavior, and quota telemetry as part of day-to-day engineering.
u/Anthony_S_Destefano posted the day's clearest sticker shock in HOLY ULTRA OUTPUT TOKENS BATMAN! WHAT ARE THEY SMOKING OVER THERE? (828 points, 209 comments). The screenshot shows OpenAI listing gpt-6-astra output at $300 per 1M short-context tokens and $450 per 1M long-context tokens, which is why the thread immediately turned into a debate about competition and whether anyone still wants a flagship-fast coding model at those rates.
u/ClaudeOfficial provided the official counterweight in Introducing Claude Haiku 5.5: the cheapest, fastest, and most capable small model we’ve ever released (470 points, 157 comments). Anthropic's public Claude Haiku 5.5 launch page says Haiku 5.5 costs around 75% less to run than Haiku 4.5 on average, halves Sonnet 5.5 cache-read prices to $0.10 per million tokens, and adds monthly API credits of $100 for Max 5x, $200 for Max 20x, and up to $500 pooled for Team. The pricing slide shared in the thread makes the intended role explicit: a much cheaper subagent tier rather than a replacement for Sonnet or Opus on the hardest coding work.
u/StayAwayFromXX made the subscription-versus-API mismatch concrete in Do you guys work for companies that pay for your Claude tokens? How much do you spend per month in tokens? (111 points, 173 comments). The OP said a company allotment of $1,000 in Claude tokens can disappear in two days, while u/Shpitz0 (score 28) reported passing $115,000 in monthly spend and u/CacheInvalidation (score 27) said they spend about $25,000 a month through Bedrock. In the same thread, u/stehen-geblieben (score 86) said subsidized seats still make more sense than direct API pricing.
u/Ziral44 added the weekly-limit side of the same problem in I don’t remember a single 5 hour window using 27% of a weekly budget… this seems a bit extreme lately. (40 points, 31 comments). The screenshots show a Max 20x account already warning that usage will run out before reset, and comments split the blame between larger session limits, transcript rereads after compaction, and too many concurrent sessions.
Discussion insight: The most useful replies were operational, not emotional. u/themightychris (score 3) warned in Subagents use a 5-min cache by default?!? (35 points, 30 comments) that longer cache TTLs can raise total spend if reuse never happens, while u/CrewOk2697 (score 10) said in After 1 year of Ultra plan, I really consider canceling (45 points, 42 comments) that Cursor's other-model quota now compares so badly with Claude Max20 that they canceled. The community is increasingly debugging spend the way it debugs infrastructure.
Comparison to prior day: Compared with 2026-10-06, the same theme broadened from spend shock and custom quota displays into official cheaper-subagent pricing, public API credits, company-budget anecdotes, and cross-vendor cancellation behavior.
1.2 Safety boundaries and unattended execution became concrete trust tests 🡕¶
The second major theme was not abstract AI safety. It was concrete operational risk: what happens when a coding agent is allowed to act for hours, what boundary actually stops damage, and what people now consider the minimum safe setup. Three separate threads turned that into first-hand evidence rather than speculation.
u/ross2000 surfaced the largest incident in Claude Opus 5.5 Deleted a User’s C Drive (685 points, 211 comments). The linked MadRobot article says the developer was running long hands-free sessions with permissions skipped and that Boris Cherny said auto mode likely would have caught the destructive action. The Reddit comments immediately split between people treating it as proof that unattended runs are dangerous and people arguing it mainly proves that bypass-permissions plus weak containment is reckless.
u/ResidentSubject4649 added a separate failure mode in Guess who just became a victim of an injection attack (124 points, 43 comments). The edited post says the issue was not the model inventing malware, but a GitHub worm-style build-time injection hidden in executed config files such as postcss.config.js, with force-push behavior and key-seeking code that had been running on the developer machine for about a week before discovery. The comments focused on rotating tokens from a clean machine, checking suspicious force pushes, and preserving enough evidence to understand the blast radius.
u/iDnLk2GtHiIJsLkThTst turned the same anxiety into a design question in How to ensure Claude Code can't delete anything? (24 points, 41 comments). The strongest reply came from u/kuroudo_ai (score 15), who argued that blocking rm is the weakest possible defense and ranked broader protections higher: version control plus unreachable backups, sandboxing, disabling unsandboxed retries, and isolating the agent in a container or VM.
Discussion insight: u/Wise-Reflection-7400 (score 77) argued in the C-drive thread that the deleted-drive case happened in bypass-permissions mode, while u/Jydder (score 49) and u/RoboErectus (score 5) argued in the containment thread for Docker, PR-only workflows, and backups the agent cannot reach. The center of gravity is moving away from "trust the prompt" and toward least privilege, sandboxing, and recoverability.
Comparison to prior day: On 2026-10-06, trust concerns were concentrated in review fatigue and dependence on Claude sessions. On 2026-10-07, the evidence got sharper: one thread was about destructive execution, another about a worm-style injection path, and the mitigation advice got much more specific.
1.3 The coordination layer above coding agents kept turning into products 🡕¶
The strongest builder cluster still sat above the model, not inside it. People kept shipping session-first terminals, shared workspaces, orchestration layers, and AI management systems so humans could supervise agents, preserve context, and keep parallel work coherent.
u/Ok_Violinist9366 framed salt.md as a single place where every task gets a page and each tool can read the notes from the previous one in Look what I built 😃 (351 points, 73 comments). The public salt.md repo describes a workspace where people and agents share docs, databases, realtime editing, MCP access, and audit logs, while the wiki emphasizes that every page can be handed to assistants as plain Markdown.
u/no-shadowban-lmao described the same category from the terminal side in I’ve spent about six months building ThinkTerm with Claude Code — a cross-platform terminal with built-in multiplexing, multi-machine workspaces, and no UI framework (36 points, 38 comments). The public ThinkTerm repo and site say sessions live on a mux server, survive disconnects, and can be resumed from desktop, browser, or TUI, with agent-status panels and remote workspaces folded into one sidebar.
u/Nightb21 pushed the same idea into an ADE in I built an open-source desktop app to keep track of several Claude Code sessions at once (built with Claude Code) (7 points, 22 comments). The public Factorai repo and site explicitly say the session, not the file, is the unit of work; real Claude and Codex CLIs run inside the tool; and routines, transcript search, diffs, and commit graphs sit beside the terminal.
u/CrackityJones33 showed the managerial version of the same trend in How I’m using an AI Engineering Manager to help build my app (26 points, 4 comments). The post says the manager turns high-level requests into tickets, plans sprints, supervises agent work, and keeps the human focused on product decisions and device testing. The screenshots matter because they show the abstraction becoming explicit: not just a long prompt, but a charter with heartbeat, max children, merge rules, scope freeze, and verification policies.
Discussion insight: The comments show both demand and skepticism. u/albatrossalt (score 2) said under the Factorai post that multiple people are independently building nearly the same shape of tool, while u/BTolputt (score 27) said under the salt.md post that the pitch still reads like "markdown notes with MCP" unless the problem is explained better. That is a useful split: the category is crowded enough to be real, but users still punish vague positioning.
Comparison to prior day: 2026-10-06 already showed the control layer hardening into a category through mods, live terminals, and observability tools. On 2026-10-07 the same layer looked more formalized: mission statements, session-first ADEs, mux-backed multi-machine terminals, and cross-tool shared context.
1.4 The community raised the bar from spectacle to usefulness 🡕¶
Builders kept shipping ambitious things, but the strongest discussion increasingly distinguished between something that looks impressive and something that solves a concrete problem or survives contact with real use. The result was a visible split between durable utility builds and community impatience with yet another flashy one-shot demo.
u/Purple_Imagination_1 supplied the clearest utility case in I used Claude Code to reverse-engineer an LG TV and build a native Plex client (29 points, 18 comments). The post says the official Plex app on a 2019 LG TV took about 30 seconds just to show the profile picker, while the resulting PlxNative site and repo describe a native Rust/OpenGL client that runs without Chromium or a WebView and cuts that wait to about 3 seconds on the same TV.
u/Time-Ad-7720 did something similarly concrete in I built a local AI webcam portal with ComfyUI - make the frame with your hands | Local Models | NO API [Free and Open Source] (87 points, 27 comments). The post and public GesturePortal repo explain the implementation detail that made it work: style the full scene continuously with ComfyUI, then let the hand gesture reveal only part of that already-generated frame so moving the portal does not change the model context.
u/bryany97 landed on the opposite side of the usefulness argument in I told my local AI to reconstruct Microsoft Word. I didn’t give it the feature list. It did it in 5 minutes. (100 points, 195 comments). The post says Aura built a Word-like app after writing 44 checks, but top comments immediately asked whether it could round-trip rich documents, whether the result was more than a surface imitation, and whether this is the best use of the capability.
That skepticism was made explicit by u/elonthegenerous in It’s crazy how quickly I’ve gotten tired of seeing “one shotted game” posts (70 points, 58 comments). u/count023 (score 37) said one-shotting does not matter if anyone can make a copycat prototype, and u/Level-Physics-1730 (score 14) said real game development still requires months of work, rewrites, and playtest state even with AI.
Discussion insight: The community is not rejecting AI-built software. It is asking harder questions about whether the result changes a real workflow, holds up under richer tests, or saves enough time to be worth trusting. That is a higher quality bar than simple amazement.
Comparison to prior day: On 2026-10-06, the strongest builder evidence still centered on demand validation and review fatigue. On 2026-10-07, the crowd pushed further: utility-first projects such as PlxNative and GesturePortal were rewarded, while "one-shotted" novelty posts were openly treated as repetitive.
2. What Frustrates People¶
Quota math is too opaque for serious planning¶
High severity. Do you guys work for companies that pay for your Claude tokens? How much do you spend per month in tokens? (111 points, 173 comments), I don’t remember a single 5 hour window using 27% of a weekly budget… this seems a bit extreme lately. (40 points, 31 comments), Subagents use a 5-min cache by default?!? (35 points, 30 comments), and After 1 year of Ultra plan, I really consider canceling (45 points, 42 comments) all describe the same failure: users cannot reliably predict runway across subscription seats, API budgets, or routed-model quotas. u/stehen-geblieben (score 86) said team seats make more sense than API prices, u/Sea-Perception1619 (score 8) said idle sessions can trigger costly rereads, and u/CrewOk2697 (score 10) said the new Cursor math pushed them to cancel. People cope by closing stale sessions, preferring subsidized subscriptions, or routing some work to cheaper tools. Worth building for: High.
Unsafe unattended execution still requires user-built containment¶
High severity. Claude Opus 5.5 Deleted a User’s C Drive (685 points, 211 comments), Guess who just became a victim of an injection attack (124 points, 43 comments), and How to ensure Claude Code can't delete anything? (24 points, 41 comments) show that the trust problem is not a single bug. It is the combination of wide permissions, executed build files, long unattended runs, and weak recovery defaults. u/kuroudo_ai (score 15) argued that blocking rm is much weaker than sandboxes, unreachable backups, and container or VM isolation, while u/Jydder (score 49) reduced the advice to Docker plus no access to master. People cope with backups, PR-only workflows, and stricter environment boundaries than the default experience provides. Worth building for: High.
Review and coordination overhead is becoming its own job¶
High severity. Im tired of reviewing code nobody actually wrote (114 points, 69 comments) describes a reviewer becoming the final checkbox on AI-written PRs, while Look what I built 😃 (351 points, 73 comments), I’ve spent about six months building ThinkTerm with Claude Code — a cross-platform terminal with built-in multiplexing, multi-machine workspaces, and no UI framework (36 points, 38 comments), I built an open-source desktop app to keep track of several Claude Code sessions at once (built with Claude Code) (7 points, 22 comments), and How I’m using an AI Engineering Manager to help build my app (26 points, 4 comments) all build around the same pain: too many sessions, too much waiting, and not enough durable state. u/inate71 (score 54) suggested auto-reviewing PRs instead of manually rereading them, while the builder posts externalized the same solution into workspaces, dashboards, and manager layers. People cope by making sessions visible, writing reasons down, and moving coordination into separate tools. Worth building for: High.
Flashy output is no longer enough by itself¶
Medium severity. It’s crazy how quickly I’ve gotten tired of seeing “one shotted game” posts (70 points, 58 comments) and I told my local AI to reconstruct Microsoft Word. I didn’t give it the feature list. It did it in 5 minutes. (100 points, 195 comments) show a community that still likes ambitious builds but now asks harder questions about originality, proof, and user benefit. u/count023 (score 37) said one-shotting matters less when anyone can make a copycat prototype, and u/Shoddy-Low-2686 (score 16) asked for real import/export tests before taking the Word reconstruction seriously. This is less anti-AI than anti-unvalidated spectacle. Worth building for: Medium.
3. What People Wish Existed¶
One truthful control plane for usage, pricing, and resets¶
People want one surface that explains remaining budget, reset timing, subscription-versus-API value, and what parallel sessions are doing to weekly headroom. Introducing Claude Haiku 5.5: the cheapest, fastest, and most capable small model we’ve ever released (470 points, 157 comments) adds cheaper subagent pricing and monthly API credits, but threads like Do you guys work for companies that pay for your Claude tokens? How much do you spend per month in tokens? (111 points, 173 comments) and I don’t remember a single 5 hour window using 27% of a weekly budget… this seems a bit extreme lately. (40 points, 31 comments) show that users still cannot translate those offers into predictable workflow planning. Rate the opportunity: Direct.
Safe unattended agent environments with recovery built in¶
People are asking, directly or implicitly, for coding agents that can run for hours without turning one mistake into a workstation incident. Claude Opus 5.5 Deleted a User’s C Drive (685 points, 211 comments), Guess who just became a victim of an injection attack (124 points, 43 comments), and How to ensure Claude Code can't delete anything? (24 points, 41 comments) all point to the same need: safer defaults, stronger sandboxes, protected credentials, and recovery paths that do not depend on the user already being unusually disciplined. Rate the opportunity: Direct.
Better handoff and review compression across many agent sessions¶
The salt.md, ThinkTerm, Factorai, and AI-manager posts all want the same thing in different forms: a reliable way to preserve intent, transfer context, and understand what happened without rereading everything. Look what I built 😃 (351 points, 73 comments), I’ve spent about six months building ThinkTerm with Claude Code — a cross-platform terminal with built-in multiplexing, multi-machine workspaces, and no UI framework (36 points, 38 comments), I built an open-source desktop app to keep track of several Claude Code sessions at once (built with Claude Code) (7 points, 22 comments), and How I’m using an AI Engineering Manager to help build my app (26 points, 4 comments) suggest this is a practical, urgent need rather than a niche preference. Rate the opportunity: Direct.
More ways to prove usefulness than a one-shot demo¶
The strongest pushback in the dataset was not anti-builder; it was anti-unvalidated spectacle. It’s crazy how quickly I’ve gotten tired of seeing “one shotted game” posts (70 points, 58 comments) and the skeptical comments under I told my local AI to reconstruct Microsoft Word. I didn’t give it the feature list. It did it in 5 minutes. (100 points, 195 comments) both ask for harder proof: originality, real testing, or an obvious user gain. Builders such as I used Claude Code to reverse-engineer an LG TV and build a native Plex client (29 points, 18 comments) and I built a local AI webcam portal with ComfyUI - make the frame with your hands | Local Models | NO API [Free and Open Source] (87 points, 27 comments) were stronger precisely because the benefit was concrete. Rate the opportunity: Competitive.
4. Tools and Methods in Use¶
| Tool | Category | Sentiment | Strengths | Limitations |
|---|---|---|---|---|
| Claude Code | Coding agent | (+/-) | Powers reverse engineering, multi-agent builds, and long sessions across many builder posts | Quota burn, destructive risk in permissive modes, and heavy review load keep surfacing |
| Claude Haiku 5.5 | Small model / subagent | (+) | Much cheaper than Haiku 4.5, fast, adjustable effort, explicitly positioned for compaction and subagent work | Anthropic still frames Sonnet 5.5 and Opus 5.5 as better for hard agentic coding |
| Cursor Ultra | IDE subscription bundle | (-) | Familiar editor workflow and access to frontier models in one place | Users report steep other-model quota burn and feel pushed toward cheaper bundled models |
| Docker / VM sandboxing | Isolation method | (+) | Limits blast radius and is the most repeated advice for safe experimentation | Setup overhead, and backups are still required because the project itself remains writable |
| salt.md | Shared workspace / context layer | (+/-) | Shared pages, databases, audit trails, and agent-readable Markdown handoffs | Several commenters still struggle to see why it beats a docs folder or note system |
| ThinkTerm | Multiplexed terminal | (+) | Persistent cross-machine sessions, native UX, agent-status panels, browser/TUI access | Early product category with several competing approaches emerging at once |
| Factorai | Session-first ADE | (+) | Status visibility, routines, transcript search, diffs, and real CLI reuse | Explicitly alpha, and Windows depends on WSL 2 |
| Argus-style AI engineering manager | Orchestration method | (+) | Ticketing, sprint planning, merge rules, and delegated supervision | Requires a long mission manual plus continuing human product approvals and testing |
| ComfyUI + MediaPipe | Local multimodal stack | (+) | Enables local, no-API interactive builds such as GesturePortal | Throughput and latency depend on strong local hardware |
Overall sentiment stayed positive toward core capability and mixed toward the surrounding operational layer. Users still believe the models can build impressive things, but the workarounds are moving outward: cheaper subagents under more expensive orchestrators, containers around risky shells, and session dashboards around otherwise opaque terminals.
The clearest migration pattern was economic. Some users in After 1 year of Ultra plan, I really consider canceling (45 points, 42 comments) said they canceled Cursor in favor of Claude Max20, while Anthropic's Claude Haiku 5.5 page explicitly pitches a cheaper helper model below Sonnet and Opus. Competitive dynamics are shifting from raw model prestige to who gives users the clearest routing, safest defaults, and best session supervision.
5. What People Are Building¶
| Project | Who built it | What it does | Problem it solves | Stack | Stage | Links |
|---|---|---|---|---|---|---|
| salt.md | u/Ok_Violinist9366 | Shared workspace where tasks, notes, and data stay readable by multiple agents and humans | Cross-tool context loss and weak handoff memory | Go server, SQLite, MCP, web UI | Shipped | post (351 points, 73 comments), repo, site |
| ThinkTerm | u/no-shadowban-lmao | Mux-backed terminal and workspace spanning local and remote machines | Hard to track many AI sessions across laptops, servers, and Pis | Rust, WezTerm, mux server, browser/TUI clients | Beta | post (36 points, 38 comments), repo, site |
| Factorai | u/Nightb21 | Session-first desktop ADE with routines, search, diffs, and real CLI terminals | Knowing which session is waiting, blocked, or changed something | TypeScript desktop app, real Claude/Codex CLIs, transcript search | Alpha | post (7 points, 22 comments), repo, site |
| PlxNative | u/Purple_Imagination_1 | Native Plex client for LG webOS TVs | The official Plex app felt painfully slow on older LG TVs | Rust, OpenGL, native webOS, Ghidra-assisted reverse engineering | Shipped | post (29 points, 18 comments), repo, site |
| GesturePortal | u/Time-Ad-7720 | Gesture-controlled live AI webcam portal that reveals a styled local feed inside a hand-made frame | Interactive local video styling without paying for remote APIs | Python, MediaPipe, ComfyUI, local image models | Alpha | post (87 points, 27 comments), repo |
| Mosaiz | u/oxmannnn | Browser app that turns photos into real buildable mosaics, print kits, and build videos | Converting a digital image into a physical mosaic workflow | Browser 3D/video/PDF pipeline, Claude Code with parallel Sonnet agents | Shipped | post (54 points, 10 comments), site |
| Aura / Quill | u/bryany97 | Local agent system that built a Word-style editor after generating its own checks | Autonomous local software generation with auditable receipts | Python, local Mac inference, local Wikipedia corpus | Alpha | post (100 points, 195 comments), repo |
PlxNative is the clearest example of the community rewarding utility over spectacle. The post pairs a concrete user problem with a measurable gain: about 30 seconds to reach the profile picker in the official client versus about 3 seconds in the native replacement, and the public site explains that the interface is drawn directly on the TV GPU rather than inside a web view. (post (29 points, 18 comments), site)
The repeated build pattern is the control layer. salt.md, ThinkTerm, Factorai, and the AI-engineering-manager workflow all start from the same pain: one model is not the bottleneck anymore, but context handoff, session visibility, and decision sequencing still are. Multiple people independently building nearly the same orchestration shape is strong evidence that this is not a one-off curiosity.
GesturePortal, Mosaiz, and PlxNative also show a second pattern: the more successful builder stories were attached to a concrete job to be done rather than a generic “look what AI can do” reveal. Aura sits at the other end of the spectrum: technically ambitious, but the comment thread quickly turned into a debate about whether the result is useful enough or tested enough to matter.
6. New and Notable¶
Anthropic’s startup subsidy is now a visible part of the AI-coding market¶
Claude startup program (31 points, 61 comments) matters because the public Claude Startups page now promises one year of Claude Team free for up to five Premium seats if you’re new to Team, $1,000 in API credits, partner offers worth up to $45K, office hours with Anthropic’s Applied AI team, and startup events. The Reddit thread adds a practical signal: the OP said approval took minutes, and replies report similarly fast responses.
Cross-vendor agents are starting to feel native inside the primary tool¶
I built a Claude Code plugin that runs Codex agents as native Claude subagents (7 points, 4 comments) is notable because the public claude-code-codex-plugin repo describes OpenAI Codex luna/sol/astra/terra workers that appear inside Claude Code like background subagents. That is a small but important product signal: users increasingly want one orchestration surface even when the underlying models come from different vendors.
7. Where the Opportunities Are¶
[+++] Usage and routing control plane — Strong evidence from sections 1, 2, and 4. Users are already doing subscription-versus-API math, watching weekly burn, and canceling tools whose quota behavior no longer feels legible. A product that makes spend, reset timing, and model routing truthful across vendors would solve a daily operating problem.
[+++] Safe unattended agent runtime — Strong evidence from sections 1, 2, 3, and 6. The deleted-drive thread, the injection-attack thread, and the containment discussion all point to the same gap: people want agents to run for hours, but only inside environments with real blast-radius limits and recovery built in.
[++] Session supervision and review compression — Evidence from sections 1, 2, 4, and 5. salt.md, ThinkTerm, Factorai, and AI-manager workflows all attack the same pain: too much parallel work and too much transcript surface area for one human to hold in their head.
[+] Utility validation for AI-built apps — Evidence from sections 1, 2, and 5. Builders can ship prototypes quickly, but the community now distinguishes sharply between spectacle and usefulness. Tools that help prove real user value, originality, or operational readiness before a public launch are still emerging.
8. Takeaways¶
- Spend visibility now shapes workflow more than raw model prestige. The day's strongest evidence combined explicit API sticker shock, official cheaper-subagent pricing, and company-budget anecdotes large enough to change hiring conversations. (HOLY ULTRA OUTPUT TOKENS BATMAN! WHAT ARE THEY SMOKING OVER THERE? (828 points, 209 comments), Introducing Claude Haiku 5.5: the cheapest, fastest, and most capable small model we’ve ever released (470 points, 157 comments), Do you guys work for companies that pay for your Claude tokens? How much do you spend per month in tokens? (111 points, 173 comments))
- Safety is becoming a product feature, not a footnote. Users are willing to let agents do more, but the most concrete threads were about destructive commands, injected build files, and how to wall agents away from the rest of a machine. (Claude Opus 5.5 Deleted a User’s C Drive (685 points, 211 comments), Guess who just became a victim of an injection attack (124 points, 43 comments), How to ensure Claude Code can't delete anything? (24 points, 41 comments))
- The fastest-growing builder category is orchestration and supervision. The strongest cluster of shipped projects did not try to replace coding agents; they tried to make them legible, persistent, and coordinated across people, sessions, and tools. (Look what I built 😃 (351 points, 73 comments), I’ve spent about six months building ThinkTerm with Claude Code — a cross-platform terminal with built-in multiplexing, multi-machine workspaces, and no UI framework (36 points, 38 comments), I built an open-source desktop app to keep track of several Claude Code sessions at once (built with Claude Code) (7 points, 22 comments), How I’m using an AI Engineering Manager to help build my app (26 points, 4 comments))
- The community is rewarding utility and questioning spectacle. PlxNative and GesturePortal were persuasive because the benefit was concrete, while one-shot game fatigue and skepticism toward the Word reconstruction show that flashy proof-of-concepts no longer get a free pass. (I used Claude Code to reverse-engineer an LG TV and build a native Plex client (29 points, 18 comments), I built a local AI webcam portal with ComfyUI - make the frame with your hands | Local Models | NO API [Free and Open Source] (87 points, 27 comments), It’s crazy how quickly I’ve gotten tired of seeing “one shotted game” posts (70 points, 58 comments), I told my local AI to reconstruct Microsoft Word. I didn’t give it the feature list. It did it in 5 minutes. (100 points, 195 comments))