YAI Setups Review · 2026 edition Jan 1 – Nov 5, 2026 Hacker News · Lobste.rs · Tildes · blogs
Infographic report · counted by unique authors

What the IT community actually uses for AI work

We read comments from Hacker News, Lobste.rs and Tildes posted in 2026, plus personal blogs. Each author counts once per tool, and only if they currently use it themselves. New in this edition: which interface people use to work with AI and how the communities differ.

of authors who described their setup use Claude Code.
01

Harnesses: Claude Code, then a long gap

Agents and coding tools ranked by the number of authors who currently use them. Percentages are out of authors who named at least one tool.

Top 18 · harness / coding tool

Each dot = 1 author

Claude Code and Codex CLI are often not mutually exclusive. authors use both, typically Claude Code as the main tool and Codex for review or as a fallback.

Beyond coding · apps and services

02

Communities side by side: same leader, different tail

Share of authors in each source who use the tool. Cell colour reflects the share within the row. Blogs = authors of articles about their own setup (1 vote per author). They are mostly enthusiasts, so naturally “pro-AI”.

03

Interfaces: the terminal rules, but not alone

Which surface people use to work with a tool or model. Solid fill = the author named the interface explicitly. Hatching = inferred from the tool’s default interface (e.g. “Codex CLI” → terminal), since most people don’t mention it.

Interface type · unique authors · explicit inferred

Host: where it runs (explicitly stated)

Claude Code: interface where the author named it

GitHub Copilot: interface where the author named it

Model × what the author uses it through · number of authors who stated the pairing explicitly

Claude is used mostly through Claude Code. Open models (Qwen, DeepSeek, GLM) run mainly through the open harnesses Pi and OpenCode, via OpenRouter, or directly on llama.cpp. GPT is most often paired with Codex CLI.

04

Trend: open-source agents rise, Cursor fades

Share of authors in each quarter who use the tool. Shares rather than absolute counts, because sample size varies (Q4 is mostly one big HN thread from November). Every panel uses the same axis; grey lines are the other tools for comparison.

05

Models: Claude leads, open weights are well represented

Solid fill means the author names the model explicitly. Hatching means the model is inferred from a harness tied to a single provider (Claude Code → Claude, Codex/ChatGPT → GPT, Gemini CLI/Antigravity → Gemini).

Model groups · explicit implicit open weights

Families · explicit mentions only · most common versions

Qwen and DeepSeek owe much of their count to the thread “Has anyone replaced Claude/GPT with a local model…”. Even without it, Qwen remains the most frequently named open model.

06

Money: median a month, a tail in the thousands

Paid plans by provider (unique authors) and monthly spend for those who stated it.

Each dot = 1 author with a stated amount · log axis USD/mo

Breakdown by band

<$20$20–100$100–250>$250

Plans and billing modes · top 18

07

Churn: from where to where

Authors who wrote that they stopped using a tool ( author × tool cases in total, across all categories). Left is the original harness or app, right is the destination. Only departures with a known destination are drawn; the rest are listed next to the source as “no destination”.

People move between Claude Code and Codex CLI in both directions, so it looks more like switching to whichever model is better at the moment. Cursor and Aider lose almost exclusively to Claude Code. OpenClaw lost users after Anthropic changed its subscription rules, partly to Hermes Agent.

08

Local models: llama.cpp has overtaken Ollama

authors mention running their own local inference (runtime or hardware).

Runtime

Hardware (classes)

Most common are Apple Silicon Macs with lots of unified memory, followed by gaming GeForce cards (RTX 3090 to 5090). 128 GB DGX Spark / GB10 and AMD Strix Halo boxes also show up fairly often.

09

Calibration: the community vs. the big 2026 surveys

Community share = authors using the tool / authors who named at least one coding harness. The surveys ask differently (“in the past year”, “weekly at work”, “regular agent users”), so compare rank and direction, not absolute percentages.

HN, Lobste.rs and Tildes skew strongly terminal and open source compared with the average: Pi’s share in the community is 3× its Stack Overflow figure, and OpenCode’s is 2× its JetBrains figure. Copilot, Cursor and JetBrains AI, on the other hand, are well below average. Those tools are used mainly by the “silent majority” at companies, who don’t post in threads like these.

Sources: Stack Overflow Developer Survey 2026 (n≈12,260, “used in the past year”) · JetBrains Developer Ecosystem 2026 (n>15,000, May–Jul, “at work”) · Pragmatic Engineer AI Tooling 2026 (n=507 regular agent users).

10

How the bloggers do it

articles about personal setups from 2026 by authors (HN front page + library and ITech feeds in Readwise Reader, including Swamp Club). Only the article’s author was counted, not the comments under it. Below is one article per author, at most 24.

11

Sources and the richest threads

How much we read, how many authors described their own setup, and which threads were richest (by number of authors with a setup).

§

Methodology and limitations

Process

  1. HN (Algolia API): 21 hand-approved Ask HN threads about setups and workflows, 19 of them with comments from 2026. Lobste.rs (JSON API) and Tildes: 213 discussions about AI in practice from 2026.
  2. Downloaded full comment trees, keeping only comments from 2026 ().
  3. An LLM read every comment, with no pre-filter, and extracted the tool, uses/left status, interface, host and model → harness pairing.
  4. Blogs: HN front page + Readwise Reader (later/starred/archive library and 100 ITech feeds, including Swamp Club). Triaged by title and summary, then an LLM read the full text. Only the author counts.
  5. Alias normalisation, author × tool deduplication, latest status wins.

Counting rules

  • Unit = unique author × tool within a source. The same handle on two sites counts as two authors.
  • Only the author’s own current use counts, not recommendations or “I’ve heard”.
  • Interface: explicitly stated vs. inferred from the tool’s default interface; both numbers are shown.
  • Surveys are for calibration only and are not merged into the rankings.
  • Tools with fewer than 3 authors are left out of the charts (long tail).

Biases and limitations

  • Discussion communities are not a representative sample of developers; they lean more terminal and open source.
  • The HN thread on local models (June) inflates Qwen, DeepSeek, Pi and OpenCode.
  • Swamp is a product of the Swamp Club community, so it is excluded from the source comparison.
  • Reddit excluded: the Reddit Responsible Builder Policy requires API approval and prohibits research outside the Reddit for Researchers program.
  • LLM classification: 99.6% of quotes verified verbatim against the source comment.