Alternatives
Products that do what Lspwatch – Automatic, configurable observability for language servers does
Hey HN, I'm sure many of you have encountered statically-typed codebases so large and complicated that your code editors freeze, lag, become unresponsive, and generally struggle. Debugging a slow editor is involved and usually an unwelcome distraction. In many cases, slowness in code editors comes from language servers, which are external programs that provide language features (e.g. go-to-definition, diagnostics, type hints). Examples of developer frustrations: [1] and [2]. At a previous company, we were concerned about growing internal frustrations from editors bottle-necked by slow…
- 1
- 2
- 3
- 4
- 5
- 6
- 7IR
Sharing an internal tool that accelerated my development work 10-fold, especially with API debugging. Thought fellow developers here might find it useful. As a developer, I often have trouble reproducing errors at the client end. https://intercept.rest lets me debug and monitor API requests and responses. It is similar to the Network tab in Chrome Developer Tools but works for any API: mobile apps, webhooks, frontend etc. After I shared it with a close circle of friends, they found it incredibly useful and even found new use cases, I never imagined. Been a long time lurker here and…
2018
- 8OS
Hi HN, we’re Dylan and Matthew, building sublingual (https://github.com/sublingual-ai/sublingual), an open-source LLM observability tool you can use with zero code changes. As developers focused on iterating and building features as fast as possible, we felt observability would’ve been a helpful tool to have, but we found existing solutions had too much overhead to set up. So we gave ourselves the challenge of building an observability tool that you can integrate without changing a single line of code in your project. How it works Run your python application as usual with…
2025 · github.com
- 9IB
The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.
2025 · github.com
- 10OS
Hey again HN. Isaac and I originally released a voice-first code review tool, but have since open-sourced it and turned it into just a better way to review your and your team's Github PRs. Main things we've heard that make code reviews slower are: 1) PRs are too big and overwhelming 2) Need to jump around to find the right context and relevant code 3) Need to spend time thinking (should not be a thing since AI exists), and writing comments What we built to address these: 1) PRs are split up into sub-PRs without needing to actually split them up and stack them yourself -> Automatically done…
2025 · github.com
- 11CS
Hi HN, I built *CodeDrift*, a CLI tool that detects bugs commonly introduced by AI coding assistants like Copilot, Cursor and ChatGPT. Over the last year I noticed that AI tools often generate code that compiles correctly, passes linting and looks reasonable in code review but still contains subtle issues. Some common examples I kept seeing: * async `forEach` loops that never await promises * missing authorization checks (IDOR) * hallucinated dependencies that don’t exist * stack traces leaking sensitive information * request data used without validation These bugs often slip past ESLint,…
Mar 2026 · npmjs.com
- 12TA
Hey HN, I think session transcripts written by coding agents like Claude Code and Codex are very interesting because they offer a detailed window into how work gets shipped. You can see the sequence of decisions that resulted in the final PR, what the agent got wrong, tools used etc. So I built a cli that analyzes these sessions and provides a local dashboard that shows what each session shipped (PRs, features), how much each PR cost, and recommendations for more effective usage. Concretely, it enriches each session with: - Outcome links: merged PRs, features shipped, files changed -…
Jul 2026 · github.com
- 13TT
2020 · typer.tiangolo.com
- 14GB
Hey HN, We’re excited to share PySpur, an open-source tool that provides a graph-based interface for building, debugging, and evaluating LLM workflows. Why we built this: Before this, we built several LLM-powered applications that collectively served thousands of users. The biggest challenge we faced was ensuring reliability: making sure the workflows were robust enough to handle edge cases and deliver consistent results. In practice, achieving this reliability meant repeatedly: 1. Breaking down complex goals into simpler steps: Composing prompts, tool calls, parsing steps, and branching…
2024 · github.com
- 15NT
I built a CLI tool that turns codebases and PRs into diagrams so you can quickly understand how things fit together. Originally made it because I couldn't follow my own AI-generated repos. Just shipped a big update: - Switched from D2 to Mermaid for rendering - Tree-sitter AST parsing + agentic flow instead of raw LLM calls. ~50x faster. - Works on any GitHub repo or PR, not just local - Dropped the web frontend, it's just a CLI now - Published as a pip package Still a ton to improve and I'm building fast. Feedback, issues, PRs all welcome.
Feb 2026 · github.com
- 16FM
I wanted to better markdown editor for collaborating with Claude/Codex and built Flashtype (https://github.com/opral/flashtype): - opens local markdown files - Claude/Codex natively integrated (with my existing subscription!) - in-line diffing to quickly accept/reject changes - WYSIWYG (!) The in-line diffs are a big step up to other apps static previews, and, in theory, just the first collaborative primitive. But, I am getting feedback that "editing" might become a thing of the past. Why do I need to see diffs from Codex/Claude if the models are…
Jul 2026 · flashtype.com
- 17FS
I built FlouState because "4 hours of coding" tells you nothing. Was it 4 hours debugging or 4 hours building features? Very different. It's a VS Code extension that automatically categorizes your coding into: Creating (new features), Debugging (fixing issues), Refactoring (improving code), or Exploring (learning codebase). Example: Yesterday I "coded" 6 hours but it was actually 3.5h debugging a race condition, 1.5h refactoring, 0.5h tests, 0.5h exploring. Traditional time trackers just show "6 hours in TypeScript." Technical: Tracks file changes, debug sessions, and edit patterns locally.…
2025 · floustate.com
- 18OS
Hello HN, I’ve been building AI agents lately and ran into a common "Context Bloat" problem. When an agent has 20+ skills, stuffing every system prompt, reference doc, and tool definition into a single request quickly hits token limits and degrades model performance (the "lost in the middle" problem). To solve this, I built OpenSkills, an open-source SDK that implements a Progressive Disclosure Architecture for agent skills. The Core Concept: Instead of loading everything upfront, OpenSkills splits a skill into three layers: Layer 1 (Metadata): Light-weight tags and triggers (always loaded…
Jan 2026
- 19IB
Logging and tools like Sentry are a thing of the past. A while back on a night out in northern Norway, I had to start debugging a critical production bug that broke the payment flow of my SaaS product. I had limited time to fix the bug or I would have lost about ~1K profit. Super stressful. I had logging and Sentry in place, but neither helped me reproduce or find the root cause of the bug. Ever since, I started thinking; why can’t we just have a tool that you setup once, and that allows us to reproduce every function call and function that the user ran before the bug? This is how the idea…
2023 · useflytrap.com
- 20AA
I’ve had this idea for a new code editor chord grammar bouncing around in my head for over 2 years, and now I can finally release v0.1 of ane. You can run it one-shot from scripts or agents (`ane exec —chord…`) or use its full-on TUI editor. ane is pure Rust, and integrates tree-sitter and LSP to provide a pleasant and predictable terminal code editing experience. I’d love folks to try it out and give feedback! Thanks :)
May 2026 · github.com
- 21AR
Hi HN. I'm the founder of Phoenix Labs (ex TikTok, Applied AI) and we're open sourcing our internal tooling today which is like a toolchain / meta-harness for CLI agents useful for really scaling eng and creative work. We are a very small team who's building a very ambitious product so we had to find ways to squeeze every ounce of efficiency that we could get our hands on. Harness strengths of different models (Claude, GPTs) and CLI-harnesses (Claude Code, Codex), safe/robust browser integration to speed up UX/QA testing, teams cli to speed up security reviews and parallelize…
May 2026 · agents-cli.sh
- 22DC
I built this tool a couple days ago to temporarily hide your prints & comments. I wanted to focus on the core logic without having to constantly delete/add prints and comments. Lmk if you like it ;)
2024 · marketplace.visualstudio.com
- 23TI
Spent a week in the break building a pre-compiler that brings type safety to runtime. Still pretty early, but generally does what it says. Looking for feedback, code that breaks it (check out the playground), ideas etc.
Jan 2026 · typical.elliots.dev
- 24DO
AI agents are great at writing code but blind at runtime. They guess, print, and waste tokens. I built dbg to give them a real debugger experience. Since it is backend based with the few I implemented (still at basic level) it can support 15+ languages with one simple CLI (still some work needed but it is functional as it is): LLDB, Delve, PDB, JDB, node inspect, rdbg, phpdbg, GHCi, etc. Profilers too (perf, pprof, cProfile, Valgrind…) I also added GPU profiling via `gdbg` (CUDA, PyTorch, Triton kernels). It auto-dispatches and shares the same unified interface. (Planning to bring those…
Apr 2026 · redknightlois.github.io
Ranked by how close each launch is in meaning, then by votes. Refine with a description →