If it didn't have Wikipedia's layout and structure, I'd say all the articles were from something adjacent to the SCP Foundation. The narrative style is much more SCP-ish than Wikipedia-like, because Wikipedia's main strength is its interconnected network of articles, which eliminates the need to tell the whole story on a single page. Only SCP Foundation articles try to capture the idea of an entire world on a single page.

UPD: And, well, sadistic and otherworldly descriptions of the unenviable existence of all humanity after something terrible happens are the SCP Foundation's bread and butter.

Fun fact: IntelliJ itself switches to Ghostty VT (with Swing rendering)

https://github.com/JetBrains/intellij-community/blob/55910d2...

As the relevant issue states, it's exactly because it should perform better for TUI agents.

https://youtrack.jetbrains.com/projects/IJPL/issues/IJPL-226...

You can actually plug Zed's ACP into Air's acp.json file to draw subscription tokens:

{ "agent_servers": { "Claude Code": { "command": "bunx", "args": ["@zed-industries/claude-code-acp"], "env": {} } } }

Swap bunx with npx -y if necessary

{ "agent_servers": { "Claude Code": { "command": "bunx", "args": ["@zed-industries/claude-code-acp"], "env": {} } } }

is to be put into your Air's acp.json (or swap bunx with npx / pnpm exec if you have only one of them)

I am an external contributor and had a few PRs merged there and I'm using a heavily customized fork.

Two core ideas I think are right: - Worktrees as the essential unit of the project interface, not a secondary feature. It kinda makes it a default thought for every coding session: maybe I create worktree instead of sending multiple agents in one workdir. - A hierarchical spec view

The interesting tension is that it's built around pi, which has a tiny share, while the potential users of agentic IDEs are already on Claude Code or Codex. That's why my fork is about hosting Claude Code compatibility and adding to GUI what's my missing for CC.