I got tired of maintaining two files that describe the same thing: an OpenAPI spec for documentation and a Postman collection for testing. They always drift. Someone updates the spec, forgets the collection. A new engineer joins and runs outdated tests against an endpoint that was changed two months ago. VolcAPI lets you define test scenarios directly inside your OpenAPI spec using a custom extension (v-functional-test), then run them from the CLI. Single source of truth. It's a Go binary no runtime, no node_modules. The goal is for it to drop into GitHub Actions with zero friction once JUnit XML output lands (in progress). Repo: https://github.com/aliamerj/volcapi This is early alpha. GET/POST/PUT/DELETE work, response validation works, environment configs work. CI output formats are the next thing I'm building. Honest question for the HN crowd: is the "spec as test suite" concept something you'd actually use, or do you prefer keeping tests separate from the spec? I've gone back and forth on this and would genuinely like to hear from people who've felt this pain. Comments URL: https://news.ycombinator.com/item?id=47814655 Points: 1 # Comments: 1
A terminal UI (TUI) for exploring, auditing, and cleaning developer cache directories on macOS and Linux. Scan cached packages for known CVEs, find outdated dependencies, and reclaim disk space — all from one tool. Developer machines accumulate tens of gigabytes of invisible cache data — ML models, package archives, build artifacts, downloaded bottles. ccmd makes it all visible, scannable for vulnerabilities, and safely deletable. brew tap juliensimon/tap && brew install ccmd cargo binstall ccmd Comments URL: https://news.ycombinator.com/item?id=47808194 Points: 2 # Comments: 0
mac 版 Claude App、vs code Claude 扩展、系统terminal版Claude（我也不知道这个叫啥） 我安装了 web-access 插件，系统 terminal 可以使用，vs code 扩展和 App code 模块都不能使用。 之前是 vs code 扩展和终端可以安装，code App 不能安装，可以使用。 找 claude 来来回回 消耗了很多时间都没解决掉。 有老哥遇到过类似问题的么？ App 系统都是最新版本 3 个帖子 - 2 位参与者 阅读完整话题
DbCls is a powerful terminal database client that supports various databases Comments URL: https://news.ycombinator.com/item?id=47792884 Points: 2 # Comments: 0
Windows Terminal 设置保留上次的 tab， settings.json 根级加： { "firstWindowPreference": "persistedWindowLayout" } 或者设置 查看 PowerShell 的配置文件位置，在 PoweShell 里执行： echo $PROFILE 输出： C:\Users\xxxx\Documents\PowerShell\Microsoft.PowerShell_profile.ps1 把这段放进 $PROFILE ，让终端记住当前目录： # 首次使用时创建 PowerShell 配置文件 if (-not (Test-Path $PROFILE)) { New-Item -ItemType File -Path $PROFILE -Force | Out-Null } # 仅在 Windows Terminal 启动时清屏 if ($env:WT_SESSION) { Clear-Host } # 保存当前已有的 prompt，后面继续沿用原来的提示符样式 if (-not $Global:__OriginalPrompt) { $Global:__OriginalPrompt = $function:prompt } function prompt { # 读取当前目录 $loc = $executionContext.SessionState.Path.CurrentLocation # 通过 OSC 9;9 把当前目录发给 Windows Terminal # 这样恢复窗口布局时，每个 tab 可以回到上次目录 [char]27 + ']9;9;' + [char]34 + $loc + [char]34 + [char]7 + (& $Global:__OriginalPrompt) } 之后正常关闭 Terminal，重开会恢复窗口布局、tab 和目录。 1 个帖子 - 1 位参与者 阅读完整话题
Article URL: https://github.com/chojs23/ec Comments URL: https://news.ycombinator.com/item?id=47788684 Points: 1 # Comments: 1
Article URL: https://github.com/rccyx/lookas Comments URL: https://news.ycombinator.com/item?id=47783528 Points: 2 # Comments: 1
Claude Code is notoriously boring. Once you finish typing your prompt, what are you supposed to do? That is exactly where Honeytree comes in. Honeytree creates a beautiful pixelated forest in your terminal, one tree for every prompt you type into Claude Code. As you gather more and more trees, you can create a highly biodiverse and colorful environment! If you ever feel tired looking at your code, you can switch terminals and see your cool forest! Honeytree can also be used to track the number of prompts you type (plot-twist: it's probably a lot). I'd greatly appreciate feedback on if the forest fixes your attention span and makes you appreciate coding again! p.s: i plan on collaborating with non-profits to plant REAL trees whenever 100 terminal trees are created overall, so feel free to share honeytree! Comments URL: https://news.ycombinator.com/item?id=47774554 Points: 1 # Comments: 0
I want to share a new dataset of 331 reward-hackable environments. These are real environments used in Terminal Bench and adjacent benchmarks. I first got interested in this because, as a reviewer of Terminal Bench, I noticed a lot of our tasks were hackable. I also noticed that many contributors to the benchmark do so because it provides credibility when selling environments to labs. Hence, TBench tasks are, in my opinion, held to a higher quality standard than those being used today for RL. No one is spending hours manually reviewing the $1B in tasks being purchased by major labs. As far as I understand, while everyone knows environments are hackable, nobody has released hundreds of "realistic" environments. Comments URL: https://news.ycombinator.com/item?id=47773298 Points: 6 # Comments: 1
A local-first, personal knowledge base for the terminal. Zettelkasten methodology, built with Rust. Your notes live as plain files on your machine. No cloud, no telemetry, no lock-in. An optional LLM layer amplifies your ability to organize and connect knowledge -- but the app works fully without it. You think, the tool organizes. Comments URL: https://news.ycombinator.com/item?id=47769865 Points: 1 # Comments: 0
Last week I wanted to quickly view some Gaussian splats which I had trained on a remote server that didn’t have any open ports or a display device. So I ended up downloading everything locally just to inspect the results This weekend I put together a terminal-based Gaussian splats viewer that renders directly in the terminal. It works over SSH and currently runs on CPU only and written in rust with claude code. I’ve found it to be pretty useful for quickly checking which .ply files correspond to which scenes and getting a rough sense of their quality. Along the way, I also wrote a small tutorial on the forward rasterization process for Gaussian splatting on CPUs Comments URL: https://news.ycombinator.com/item?id=47762025 Points: 5 # Comments: 1
Article URL: https://nodeops.network/createos/docs/CLI/Overview Comments URL: https://news.ycombinator.com/item?id=47761684 Points: 6 # Comments: 1
Bloomberg Terminal exists because financial traders needed one place to see everything: prices, risk, routing, counterparty health. You can't trade blind. LLM engineers are trading blind. Which provider is degraded right now? What does this model actually cost when you factor in overhead, not just token price? If traffic shifts between providers, what happens to cost and latency? Is your stack dangerously concentrated on one provider? These are operational questions every production LLM system has. Nobody's built the tooling for them until now, so most teams either fly blind or patch together status pages, spreadsheets, and gut feel. We built the LLM Ops Toolkit to fix that: 1. Provider uptime monitor across 18+ LLM providers, live status in one view 2. Cost calculator that includes overhead, not just raw token pricing 3. Routing simulator to model cost and latency impact before you shift traffic 4. Model diversity audit to surface concentration risk before it becomes an incident Free, open-source, no signup. Dashboard is at tools.lamatic.ai The routing simulator is the most experimental piece and has the roughest edges. Genuinely curious how others think about provider concentration risk. We've been treating it as dependency risk in software but that framing may not hold at scale. Also live on Product Hunt today: producthunt.com/products/lamatic-ai Comments URL: https://news.ycombinator.com/item?id=47754636 Points: 5 # Comments: 1
Article URL: https://github.com/Higangssh/winclipshot Comments URL: https://news.ycombinator.com/item?id=47752632 Points: 3 # Comments: 0
Article URL: https://github.com/DeepBlueDynamics/hyperia Comments URL: https://news.ycombinator.com/item?id=47751697 Points: 2 # Comments: 0
I built xlg to browse Reddit, HN, GitHub, Wikipedia from terminal using Unix pipe syntax. Example: xlg 'reddit "r/Art" | take 5 | print' Also works as MCP server for AI agents, OpenClaw GitHub: https://github.com/auraz/xlg Comments URL: https://news.ycombinator.com/item?id=47748323 Points: 1 # Comments: 1
I built a terminal diff viewer for a workflow I couldn't do comfortably with existing tools: reviewing AI-generated code changes without leaving the terminal session where the agent runs, annotating what needs to change, and feeding those annotations straight back to the agent. Plenty of diff viewers exist, and some can even feed notes back to an agent, but none of them fit that flow for me - they pulled me out of the terminal into a separate app, or the round-trip back to the agent was clunky. Revdiff is how I solved it. From a Claude Code session I type `/revdiff main` or just say "review diff for last 3 commits" - it opens as a terminal overlay on top of the agent session. I read the diff, drop annotations on any line, hunk, or file, then quit. The annotations go straight back to the agent, which picks them up and starts working on them. When the agent is done, revdiff reopens on the new changes so I can annotate again - and this loop continues until I quit without leaving any annotations. The same flow turned out to be useful for plans too. There's a separate `revdiff-planning` plugin that hooks into Claude Code's plan mode - the moment the agent finishes a plan and calls ExitPlanMode, revdiff opens automatically on the plan text. I annotate the parts I disagree with or want expanded, quit, and the agent revises the plan before writing any code. It's a two-pane TUI: file tree on the left, syntax-highlighted diff on the right. Vim-style navigation, /search, hunk jumping, word-level change highlighting, blame gutters, collapsed diff mode. Fully customizable - 7 bundled color themes, remappable keybindings, and per-color overrides via CLI flags, env vars, or config file. Works with git and Mercurial. It's a single binary - just `revdiff HEAD~3` to review your last 3 commits. Ready-to-use plugins are available for Claude Code (terminal overlay via tmux, Zellij, kitty, wezterm, Kaku, cmux, ghostty, iTerm2, or Emacs vterm - whichever you're in), Codex, and pi. Written in Go, open source (MIT). Install via brew: `brew install umputun/apps/revdiff` GitHub: https://github.com/umputun/revdiff Site: https://revdiff.com Would love to hear how others approach reviewing AI-generated diffs and PRs, any unusual use cases, and ideas for what to improve or add. Comments URL: https://news.ycombinator.com/item?id=47742437 Points: 9 # Comments: 2
Hello everyone. Claudraband wraps a Claude Code TUI in a controlled terminal to enable extended workflows. It uses tmux for visible controlled sessions or xterm.js for headless sessions (a little slower), but everything is mediated by an actual Claude Code TUI. One example of a workflow I use now is having my current Claude Code interrogate older sessions for certain decisions it made: https://github.com/halfwhey/claudraband?tab=readme-ov-file#s... This project provides: - Resumable non-interactive workflows. Essentially `claude -p` with session support: `cband continue 'what was the result of the research?'` - HTTP server to remotely control a Claude Code session: `cband serve --port 8123` - ACP server to use with alternative frontends such as Zed or Toad ( https://github.com/batrachianai/toad ): `cband acp --model haiku`. - TypeScript library so you can integrate these workflows into your own application. This exists cause I was using `tmux send-keys` heavily in a lot of my Claude Code workflows, but I wanted to streamline it. Comments URL: https://news.ycombinator.com/item?id=47741889 Points: 25 # Comments: 3
Article URL: https://spuddy.sh Comments URL: https://news.ycombinator.com/item?id=47740641 Points: 2 # Comments: 0
Built it just for fun. Feel free to give me feedback. Comments URL: https://news.ycombinator.com/item?id=47739588 Points: 1 # Comments: 0