Alternatives
Products that do what trawld does
catch vulnerable dependencies before they catch you
- 1
Everything in OpenClaw's terminal, you can now do visually
Apr 2026 · rectify.so
- 2
- 3
- 4
Traccia▲197AI applications are becoming agents, which has started to take autonomous decisions. There are plenty of tools and platform available to trace, and observe what an agent or llms calls does. They are good in what they do, but tracing and observability isnt enough for AI agents era. We need a solution that can help you observe, evaluate, create run time policies to govern and finally audit the actions of the agent. We built Traccia to solve this problem. The good part, all of these can be achieved by just writing few lines of code. Traccia has an open-sourced sdk that can work with your…
11d ago · traccia.ai
- 5CS
We now write most of our code with agents. For a while, PRs piled up, causing review fatigue, and we had this sinking feeling that standards were slipping. Consistency is tough at this volume. I’m sharing the solution we found, which has become our main product. Continue (https://docs.continue.dev) runs AI checks on every PR. Each check is a source-controlled markdown file in `.continue/checks/` that shows up as a GitHub status check. They run as full agents, not just reading the diff, but able to read/write files, run bash commands, and use a browser. If it finds…
Feb 2026 · docs.continue.dev
- 6RT
This project (Agents Observe) started as an exploration into building automation harnesses around claude code. I needed a way to see exactly what teams of agents were doing in realtime and to filter and search their output. A few interesting learnings from building and using this: - Claude code hooks are blocking - performance degrades rapidly if you have a lot of plugins that use hooks - Hooks provide a lot more useful info than OTEL data - Claude's jsonl files provide the full picture - Lifecycle management of MCP processes started by plugins is a bit kludgy at best The biggest takeaway is…
Apr 2026 · github.com
- 7
- 8TO
Hey Xinwei and Zecheng here, we are the authors of TraceRoot (https://github.com/traceroot-ai/traceroot). TraceRoot (https://traceroot.ai) is an open-source debugging platform that helps engineers fix production issues faster by combining structured traces, logs, source code contexts and discussions in Github PRs, issues and Slack channels, etc. with AI Agents. At the heart are our lightweight Python (https://github.com/traceroot-ai/traceroot-sdk) and TypeScript (https://github.com/traceroot-ai/traceroot-sdk-ts) SDKs -…
2025 · github.com
- 9
Trawl▲2Version autocomplete and outdated warnings inside VS Code
Mar 2026 · marketplace.visualstudio.com
- 10
- 11AD
I’ve been tinkering with what a “multi-agent IDE” should look like if your day-to-day workflow is mostly in terminal (Claude Code, OpenAI Codex, etc.). The more I played with it, the more it collapsed into three fundamentals: * A good TUI: Terminal is the center stage, with other stuff (CodeEdit, Diff, Review) baked on the side. I don’t like piping Agent’s output through some electron wrapper, here you get to run CC/Codex/Droid/Amp/etc directly. * Isolation: agents shouldn’t step on each other’s toes. The simplest primitive I’ve found is Git worktrees. It is not as…
Jan 2026 · agentastic.dev
- 12
- 13
- 14
- 15SD
I've created a simple automation tool called Sonarless that allows developers to scan their code using SonarQube through an easy-to-use CLI interface. Key Features: - Easy Installation: Just run `curl -s "https://raw.githubusercontent.com/gitricko/sonarless/main/in..." | bash` - Simple Scanning: Run `sonarless scan` from your git root to start scanning and improving your code quality. No need to wait for your admin to set up SonarQube for you. - GitHub Actions Integration: Sonarless GitHub Actions enable you to incorporate code scanning into your CI pipeline…
2024 · github.com
- 16LT
Running multiple coding agents could make user losing track of what they were doing. Once subagents start spawning other subagents, basic questions get hard to answer: what is running right now, what tool did it just call, did the child agent actually do what the parent asked. Lazyagent is a terminal TUI that collects events from Claude Code, Codex, and OpenCode and shows them in one place. It groups sessions from different runtimes by working directory, so Claude and Codex runs on the same repo appear under the same project. From there you can: - Filter events by type: tool calls, user…
Apr 2026 · github.com
- 17
- 18AR
If you're interested in exploring what LLM-based agent systems these days actually do to solve certain benchmarks such as SWEBench or WebArena, we created a small leaderboard with our team, that allows to view a lot of public and OSS agent results including all the runtime traces (the step-by-step reasoning behind the scenes). Looking at traces is actually quite interesting, as they reveal a lot about the inner working and shortcomings of current agent system, e.g. see https://explorer.invariantlabs.ai/u/invariant/webarena--SteP... for an example trace.
2024 · explorer.invariantlabs.ai
- 19PS
Hey HN — I kept seeing developers describe the same frustration: the commit-push-wait-read-logs cycle when debugging CI pipelines. So I built PipeStep. PipeStep parses your GitHub Actions YAML, spins up the right Docker container, and gives you a step-through debugger for your run: shell commands. You can: 1. Pause before each step and inspect the container state. 2. Shell into the running container mid-pipeline (press I). 3. Set breakpoints on specific steps (press B). 4. Retry failed steps or skip past others. It deliberately does not try to replicate the full GitHub Actions runtime — no…
Mar 2026 · github.com
- 20
- 21
- 22
Scan and auto-fix GitHub vulnerabilities in seconds
Apr 2026 · package-helper.up.railway.app
- 23
- 24LA
Lazyagent a simple way to see what your coding agents were actually doing across Claude, Codex, and OpenCode. Once you have more than 1 agent running, its really hard to answer the simple question: what is it doing right now and why? It is a local terminal UI that collects your agents runtime events and shows their activity in one place. You can inspect: - agents and subagents - tool calls - prompts - outputs - status changes Sessions and projects are there to give that activity some context, so it is easier to follow what happened over time and which run belongs to which repo. And make it…
Apr 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →