Alternatives
Products that do what Liven Beta – Context engine mapping codebase dependencies for LLM(SWE) does
Liven Beta scaffolds your codebase’s dependency graph—functions, classes, cross‑file & folder relations—and displays it instantly in the terminal. Think of it as a context engine for developers and LLMs.
- 1
- 2
- 3
- 4LF
Hey HN, I built SWE-Kit, LLM toolkit (Function callable tools) which makes building agents specialised in coding like Devin very easy. I noticed a typical pattern while building local agents: creating & perfecting LLM tools to interact with system or codebase was the repeated and time-consuming. We created a layer that simplifies building agents that can interact with code, file system, git, shell and allows you to quickly solve for a wide variety of coding agent use cases. Aren’t there open coding agents already? Well, yes, but most folks would want to solve their specific use case like a…
2024 · swekit.dev
- 5WC
Hi all, I'm Ivan, and together with Alex, we're building a diagram visualization tool for codebases. Alex and I are devs, and we've noticed that recently we've been super productive at writing code (prompting :D). But when it comes to understanding big systems, prompting doesn't work that well — for that, diagrams are best imo. Most tools out there don't scale to big projects (e.g. PyTorch), so we're building CodeBoarding — a recursive visualizer for codebases. It starts from the highest level of abstractions and lets you dive deeper. We use static analysis and LLM agents. The control-flow…
2025 · github.com
- 6CM
I've been vibe-coding tools to automate chunks of my consulting work, fell down a rabbit hole, and started building actual products. Suddenly I'm in a world of unknown-unknowns and known-unknowns. One of the bigger things to solve was understanding code the LLM generated that I didn't fully grasp. What does it touch? What reads and writes where? Is the auth path where I think it is? So I built codeflowmap. Point it at a repo and it maps the dependency and call graph, then surfaces the read / write / auth paths between files and functions. Connect a local model (Ollama) or any…
Jun 2026 · github.com
- 7BA
I built CodinIT because I wanted that "Bolt-like" experience, but on my own terms. 100% Open Source The core idea: You should be able to prompt a full-stack application into existence, but the environment should be local, the models should be swappable (Ollama/LM Studio support was a priority), and the output should be standard code you actually own. A few things I focused on: Context Management: One of the hardest parts was figuring out how to feed the right file context back to the LLM without blowing out the token limit. I’ve implemented a custom indexing approach to keep the "vibe…
Dec 2025 · github.com
- 8
I find LLM interpretability extremely interesting and wanted to create a minimal repo for: - SAE training - Automatic feature interpretation - Visualizing features and running interventions through a GUI You can try it here: https://nanointerpret.pages.dev/ Or check the repo: https://github.com/Belluxx/nanointerpret
9d ago · nanointerpret.pages.dev
- 9CV
I built Codag because I kept getting lost in my own AI code. You're chaining 3 LLM calls across 5 files. A prompt change breaks something downstream. Which call? Which branch? You grep for "openai.chat", open 8 tabs, trace the flow manually. Codag automates this: - Point it at your codebase and it extracts every LLM call, decision branch, and processing step - Renders an interactive and shareable DAG with clickable nodes that link back to source - Live updates as you edit using tree-sitter — no waiting for re-analysis Supports OpenAI, Anthropic, Gemini, LangChain, LangGraph, CrewAI, and…
Feb 2026 · github.com
- 10GB
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
- 11CV
I worked as a software engineer at Amazon, SAP, and on open source. In all 3 places I have struggled with the friction of understanding codebases before I can make a contribution. I think this brain-fatiguing process can be improved. I am trying to solve it with a tool I built over the last 4 years called CodeCanvas: https://docs.code-canvas.com CodeCanvas visualizes codebases through interactive diagrams linked directly to source code. Users can record 'simulations' to demonstrate data flow and business logic. I’ve also recently added an LLM chat where it takes only the relevant…
2025 · pie-crepe-38f.notion.site
- 12AP
As a former CIO who managed teams working with millions of lines of legacy code (Visual Basic, Sybase, Oracle Forms, and worse), I feel the pain of maintaining and onboarding developers to legacy systems. Believing that LLM-enabled tools can play a role in solving this, I've built a tool that automatically generates documentation for legacy codebases using the Model Context Protocol (MCP) & Claude Sonnet. At first glance, I think this approach has merit. Some samples are in the README. I welcome your thoughts. The Problem: - Legacy codebases are notoriously difficult to understand and…
2025 · github.com
- 13MC
Hi HN, I'm excited to introduce Mixlayer, a platform I've been working on over the past 6 months that allows you to code and deploy prompts using simple JavaScript functions. Mixlayer recreates the developer experience of using LLMs locally without having to do all of the local setup yourself. I originally came up with this idea when using LLMs on my MacBook and thought it’d be cool to build a product that makes it easy for everyone. It compiles your code to a WASM binary and runs it alongside a custom inference stack I wrote in Rust. When you integrate LLMs in this way, your code and the…
2024 · mixlayer.com
- 14IM
Hi HN, I built Hypermod to help developers automate large-scale code migrations. If you've ever had to upgrade dependencies, refactor thousands of files, or apply the same fix across multiple repos, you know how painful and time-consuming it can be. Hypermod makes this process faster and more reliable by combining static analysis, AI-powered codemods, and GitHub automation. Why I Built This I've spent years working with large codebases where upgrading dependencies or migrating frameworks was a nightmare—lots of manual work, brittle scripts, and coordination across teams. Existing tools like…
2025 · hypermod.io
- 15LA
You build LLM applications with YAML files, that define an execution graph. Nodes can be either LLM API calls, regular function executions or other graphs themselves. Because you can nest graphs easily, building complex applications is not an issue, but at the same time you don't lose control. The YAML basically states what are the tasks that need to be done and how they connect. Other than that, you only write individual python functions to be called during the execution. No new classes and abstractions to learn.
2024 · github.com
- 16CL
Hi Hacker News, As a dev extensively using GPT-4 for coding, I've realized its effectiveness significantly increases with richer context (e.g., code samples, execution state - props to DevinAI for famously console.logging itself). This inspired me to push the idea further and create CaptureFlow. This tool equips your coding LLM with a debugger-level view into your Python apps, via a simple one-line decorator. Such detailed tracing improves LLM coding capabilities and opens new use cases, such as auto-bug fix and test case generation. CaptureFlow-py offers an extensible end-to-end pipeline…
2024 · github.com
- 17A1
I've seen a lot of comments about how complex frameworks like LangChain can be. Over the holidays, I wanted to see how minimal an LLM framework could get if we stripped away everything non-essential. The result is an LLM framework in just 100 lines of code. These 100 lines capture what I see as the core abstraction of most LLM frameworks: a nested directed graph that breaks down tasks into multiple LLM steps, with branching and recursion to enable agent-like decision-making. From there, you can layer on more advanced features like agents, RAG, task decomposition, and more. I’ve intentionally…
2025 · github.com
- 18XR
Hi HN, We built Xybrid, a Rust library for running LLM + speech pipelines directly inside your app, no server, no daemon, just one binary. We started building it while working on a privacy-focused LLM app with Tauri and realized there wasn’t a straightforward way to embed models directly into shipped applications without relying on a separate server process. Xybrid links into your process like any other library. It supports GGUF / ONNX / CoreML and integrates with Flutter, Swift, Kotlin, Unity, and Tauri, letting you run pipelines like speech → LLM → speech in a single call. On…
Mar 2026 · github.com
- 19AA
We've rolled out a feature for openbase.com that we think is a DX game changer for Node devs. Since the emergence of ECMA Script modules, it's been a continuous guessing game as to what kind of exports a package has. That's never really been discoverable without using a site like unpkg, or installing the package and inspecting package.json. Openbase now displays the ES Module support level (e.g. type of exports) on all of their package pages. We added this feature because our devs are some of the folks continually caught off guard by installing an NPM dependency only to find out it's…
2022
- 20LI
Hey HN! We built Lunon to make LLM development way less of a headache. Ever wanted to see how different models handle the same prompt without all the setup hassle? That's what we fixed. Our API lets you compare Claude, GPT, Mistral and others in real-time with just a few lines of code. No more complex infrastructure or managing multiple API connections - we handle all that boring stuff behind the scenes. Plus, you can cut costs by intelligently routing requests to the right model for each task. Use the powerful (expensive) models only when you really need them. If you're building with LLMs…
2025 · lunon.com
- 21AO
Hi, We are building an open-source framework for loading and structuring LLM context to create accurate and explainable LLM answers using knowledge graphs and vector stores. We built the tool with four main concepts in mind: 1. Loader -> uses dlt in the backend to load and structure the data 2. Cognify step -> creates a graph with summaries, labels and factoids that are interconnected across the documents and stored as a representation in the vector store 3. Optimizer -> Uses DSPy to optimize LLM queries, and we plan to extend it to most of the knobs we can turn, like chunking etc. 4. Search…
2024 · github.com
- 22AS
Hi HN, I built ast-visualizer.com because I wanted a way to visualize the architecture/structure of a Python repo before dived into the code. Most tools tell you what the code does; I wanted to see how it's built. The Problem: Onboarding onto a large codebase is a nightmare. LLMs help with single functions, but they struggle to show you the "God Objects," circular dependencies, or high-complexity hotspots across 50+ files. What it does: Dependency Graph: Visualizes imports and file complexity to find architectural bottlenecks. Radial AST Heatmaps: Maps individual files and color-codes…
Feb 2026 · ast-visualizer.com
- 23NT
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
- 24IB
After years of struggling with onboarding to new projects, I got tired of spending weeks just trying to grasp the basics of a codebase. The README rarely tells the whole story, and "just read the code" isn't practical for large repos. I built RepoIQ to create personalized learning paths through any GitHub repository. It analyzes the codebase structure, identifies key components, and creates a step-by-step guide tailored to your learning needs.
2025 · repoiq.be
Ranked by how close each launch is in meaning, then by votes. Refine with a description →