Show HN: Yutovo – visual online and desktop calculator inside a text editor https://ift.tt/jVyivot

Show HN: Yutovo – visual online and desktop calculator inside a text editor Hi all, I build a calculator that displays and edits formulas in a familiar graphical form, has a WYSIWYG editor, can work with numbers of any size, supports physical units, and has many other features. There are online and desktop (Linux, Windows) versions. The project is open source and consists of these ones: https://ift.tt/wuA7kL5 — a text and formula editor with output to a custom window. Built from scratch, no dependencies on other editors. C++, boost. https://ift.tt/bcpx0d6 — a desktop application based on Qt. https://ift.tt/nzXEaRx — an online version based on Vue.js and Quasar. The remaining components are compiled for Wasm. https://ift.tt/tUH8CNm — a string expression calculator based on boost.spirit. https://ift.tt/ZtcYGj5 — a web server for a website based on Drogon. https://ift.tt/yZ9n8eV — a calculator broker. C++. https://ift.tt/dxyAY8C — a logger based on spdlog. There are versions for Flatpak, Snap, Debian, and Windows. You can save your documents on the website after registering. I welcome any comments, bugs, shortcomings, or suggestions. https://yutovo.com February 4, 2026 at 04:03AM

Show HN: Ghidra MCP Server – 110 tools for AI-assisted reverse engineering https://ift.tt/0DLXGYt

Show HN: Ghidra MCP Server – 110 tools for AI-assisted reverse engineering https://ift.tt/XuwUVqz February 4, 2026 at 03:51AM

Show HN: OpenClaw Assistant – Replace Google Assistant with Any AI https://ift.tt/riMyeSQ

Show HN: OpenClaw Assistant – Replace Google Assistant with Any AI https://ift.tt/ZhKw96S February 4, 2026 at 12:45AM

Show HN: Ec – a terminal Git conflict resolver inspired by IntelliJ https://ift.tt/z1Tjax4

Show HN: Ec – a terminal Git conflict resolver inspired by IntelliJ Hi HN, I built ec because my friends who are new to development kept getting stuck on Git conflicts. Most TUI merge tools felt hard to use or non-intuitive for them. The only flow they found easy was the IntelliJ (JetBrains) conflict resolver, so I recreated that experience in the terminal. ec is a terminal-native, 3-pane conflict resolver with a focused, step-by-step flow. If you try it and leave feedback, I would be really grateful. Thanks! Repo: https://ift.tt/bNcti9Q https://ift.tt/bNcti9Q February 3, 2026 at 09:25PM

Show HN: Axiomeer – An open marketplace for AI agents https://ift.tt/Ola53if

Show HN: Axiomeer – An open marketplace for AI agents Hi, I built Axiomeer, an open-source marketplace protocol for AI agents. The idea: instead of hardcoding tool integrations into every agent, agents shop a catalog at runtime, and the marketplace ranks, executes, validates, and audits everything. How it works: - Providers publish products (APIs, datasets, model endpoints) via 10-line JSON manifests - Agents describe what they need in natural language or structured tags - The router scores all options by capability match (70%), latency (20%), cost (10%) with hard constraint filters - The top pick is executed, output is validated (citations required? timestamps?), and evidence quality is assessed deterministically - If the evidence is mock/fake/low-quality, the agent abstains rather than hallucinating - Every execution is logged as an immutable receipt The trust layer is the part I think is missing from existing approaches. MCP standardizes how you connect to a tool server. Axiomeer operates one layer up: which tool, from which provider, and can you trust what came back? Stack: Python, FastAPI, SQLAlchemy, Ollama (local LLM, no API keys). v1 ships with weather providers (Open-Meteo + mocks). The architecture supports any HTTP endpoint that returns structured JSON. Looking for contributors to add real providers across domains (finance, search, docs, code execution). Each provider is ~30 lines + a manifest. https://ift.tt/mTnFMCO February 2, 2026 at 09:43PM

Show HN: Kannada Nudi Editor Web Version https://ift.tt/xLETAbQ

Show HN: Kannada Nudi Editor Web Version Ported the Desktop Version of Kannada Nudi Editor to Web under the guidance of https://kagapa.com/ https://nudiweb.com/ February 3, 2026 at 01:11AM

Show HN: 127 PRs to Prod this wknd with 18 AI agents: metaswarm. MIT licensed https://ift.tt/BgJyc1z

Show HN: 127 PRs to Prod this wknd with 18 AI agents: metaswarm. MIT licensed A few weeks ago I posted about GoodToGo https://ift.tt/rSafhmw - a tool that gives AI agents a deterministic answer to "is this PR ready to merge?" Several people asked about the larger orchestration system I mentioned. This is that system. I got tired of being a project manager for Claude Code. It writes code fine, but shipping production code is seven or eight jobs — research, planning, design review, implementation, code review, security audit, PR creation, CI babysitting. I was doing all the coordination myself. The agent typed fast. I was still the bottleneck. What I really needed was an orchestrator of orchestrators - swarms of swarms of agents with deterministic quality checks. So I built metaswarm. It breaks work into phases and assigns each to a specialist swarm orchestrator. It manages handoffs and uses BEADS for deterministic gates that persist across /compact, /clear, and even across sessions. Point it at a GitHub issue or brainstorm with it (it uses Superpowers to ask clarifying questions) and it creates epics, tasks, and dependencies, then runs the full pipeline to a merged PR - including outside code review like CodeRabbit, Greptile, and Bugbot. The thing that surprised me most was the design review gate. Five agents — PM, Architect, Designer, Security, CTO — review every plan in parallel before a line of code gets written. All five must approve. Three rounds max, then it escalates to a human. I expected a rubber stamp. It catches real design problems, dependency issues, security gaps. This weekend I pointed it at my backlog. 127 PRs merged. Every one hit 100% test coverage. No human wrote code, reviewed code, or clicked merge. OK, I guided it a bit, mostly helping with plans for some of the epics. A few learnings: Agent checklists are theater. Agents skipped coverage checks, misread thresholds, or decided they didn't apply. Prompts alone weren't enough. The fix was deterministic gates — BEADS, pre-push hooks, CI jobs all on top of the agent completion check. The gates block bad code whether or not the agent cooperates. The agents are just markdown files. No custom runtime, no server, and while I built it on TypeScript, the agents are language-agnostic. You can read all of them, edit them, add your own. It self-reflects too. After every merged PR, the system extracts patterns, gotchas, and decisions into a JSONL knowledge base. Agents only load entries relevant to the files they're touching. The more it ships, the fewer mistakes it makes. It learns as it goes. metaswarm stands on two projects: https://ift.tt/pP2534V by Steve Yegge (git-native task tracking and knowledge priming) and https://ift.tt/QFl1f3j by Jesse Vincent (disciplined agentic workflows — TDD, brainstorming, systematic debugging). Both were essential. Background: I founded Technorati, Linuxcare, and Warmstart; tech exec at Lyft and Reddit. I built metaswarm because I needed autonomous agents that could ship to a production codebase with the same standards I'd hold a human team to. $ cd my-project-name $ npx metaswarm init MIT licensed. IANAL. YMMV. Issues/PRs welcome! https://ift.tt/7XzJrkL February 2, 2026 at 10:18PM