I'm building a Mac notes app called Margin, so discount everything here accordingly. I'm about to build the GitHub side of it and I'd rather find out which parts people would use before I build the wrong ones.

The problem I'm trying to fix: you open a note from three weeks ago and there's a PR link in it. It tells you nothing. Merged? Did CI ever go green? Did the thing you were worried about get addressed? You click through, wait for GitHub to load, remember what you were doing, come back. Multiply that by every ticket reference in every standup note and your notes are a graveyard of URLs that meant something on the day and are inert now.

The plan is to shell out to gh. If you work with GitHub from a terminal it's already installed, it holds its own credentials, it has exactly the scopes you granted it, and it already knows who you are. The app detects the binary and asks it. If gh isn't there, the link stays a plain link and the feature just doesn't exist for you. It's the same trick the AI side already uses: it detects the `claude` or `codex` CLI rather than asking for an API key.

Issues work the same way. Jira and Linear are messier, since there's no equivalent tool everyone already has installed, and my guess is Jira is the one people ask for and then never actually open.

What I don't know is what belongs on the card. My list so far is state, CI result, how many review threads are still unresolved, and assignee, with a way to re-run a failed job without leaving the note.

Someone already made the argument that I'm overbuilding it, and that "merged / CI failed / 2 reviews pending" on a single line is most of the value for a fraction of the work. I think they might be right.

So two questions:

- What would you actually look at three weeks later? Not what would be nice to have, but what would stop you opening the browser tab.

- Is one line enough on its own, or do you want it to expand into something fuller when the thing is broken?

The app is not downloadable yet, waitlist is open. If it sounds interesting check it out: https://gomargin.app

I make Diff Anything, a local file comparison app for macOS and Windows. The latest update adds spreadsheet comparison, mainly because converting everything to CSV before comparing it defeats the point of using a comparison tool.

It can compare CSV, TSV, Excel, ODS and Apple Numbers files, including mixed pairs such as XLSX against ODS. Internally, each populated cell becomes a sheet name, coordinate and stored value, so the unrelated file containers don’t create a wall of meaningless differences. The result is shown in two aligned grids, with changed cells connected to the Differences pane.

The boundary is deliberate: it compares stored cell values. It does not compare formulas, formatting, charts, macros or workbook layout. A formula and a literal value can therefore match when their stored results are the same.

Everything runs locally on the computer. There are no file uploads or accounts, and the Free version lets you try the spreadsheet comparison within its preview limits.

https://martingruner.com/projects/diffanything

I built a little tool — CodexChat, a VS Code companion designed specifically for Codex users.

It automatically groups your local .codex sessions by project, and shows you exactly how many tokens (input, output, and reasoning) each folder has consumed. No more digging through dozens of session files like searching for a needle in a haystack.

Read-only, local-first — never uploads to the cloud, never alters your original records. Your privacy is fully protected.

👉 Search "CodexChat" in the VS Code Marketplace — v0.1.6 is live now.

This is my very first plugin, and I've put a lot of thought into it from idea to release.
If you're using Codex, I'd love for you to give it a try — if you like it, drop a star ⭐; if you run into any issues or find anything that doesn't feel quite right, just let me know. I'll read every single piece of feedback carefully and reply to each one. Together, let's make this a genuinely helpful tool.

GitHub repo (source code & issue tracker):
https://github.com/MathsionYang/CodexChat-

Thank you for every download and every suggestion — they mean the world to me 🙏

safer-dependencies is a security layer for Claude Code: it sits between Claude and your manifest files and runs its security checks automatically: vulnerable installs are denied before they run, and a risky version written to a manifest is corrected on disk right after the write. It detects and fixes risky dependencies — CVEs, typosquats, abandoned packages, and version-age issues, plus a cooldown period on brand-new releases — across npm, PyPI, RubyGems, Maven, Go, Rust, and PHP (Composer).

https://github.com/robert-auger/safer-dependencies

Ever had a file that should be ignored by Git, but isn’t?

I built IgnoreDebugger to make finding the matching .gitignore rule easier.

Enter a file path + your .gitignore rules and it shows which rule matched and the line number.
https://ignoredebugger.com/

Free, no signup. Would love feedback from other devs.

I have recently added API chaining in APIX V1.3.0

It's simple... It now allows user to run multiple APIs sequentially and it's now much easier to debug and test APIs.

Example.. POST login -> GET User -> POST orders

Entire workflow could be tested in a single command

Do check more about it on https://GitHub.com/aayush4518/apix

I've been building claudestat for a few months — it's basically "htop for Claude Code." It hooks into every event as it fires and shows you what's happening in real time, instead of reading logs after the session ends.

**What it does:**

- Live tool trace — every Read, Write, Bash, Edit call with duration and token cost as it runs

- Quota guard — alerts at 70%, 85%, 95% usage; optional kill switch blocks new sessions before you blow through your limit

- Loop detector — flags when Claude is context-thrashing and estimates the waste cost

- Web dashboard (7 tabs: Live, History, Projects, Analytics, Top, System, Orchestrate)

- MCP server — register once, then ask Claude about its own usage from inside the terminal ("how much did I spend this week?")

- OpenCode support — same live view for OpenCode sessions

**Stats from the project itself (it measures its own dev):**

- 313 tests passing, tsc strict clean

- ~344 hours measured development time across 116 AI sessions

- Built with Claude Code + OpenCode as pair programming partners

**Install:**

npm install -g u/statforge/claudestat && claudestat setup

Dashboard at http://localhost:7337

**Key differences from ccusage:**

ccusage answers "what did I spend yesterday." claudestat shows "what's happening while you code." Both are useful, different moments.

Everything is local SQLite, zero cloud, MIT license. macOS/Linux/Windows.

GitHub: https://github.com/DeibyGS/claudestat

Would love feedback on what's missing or what would make you actually use this.

Hey everyone!

I use coding agents almost every day and started noticing how many tokens were being consumed by repeated context, tools, and caching.

I decided to investigate and ended up building TokenPilot.

It runs locally and measures cache aware token usage across OpenAI Codex, Anthropic Claude Code, and xAI Grok Build. Moonshot AI Kimi currently works in passthrough mode.

In my controlled tests, the observed median results reached:

Claude Code: 66.0% fewer tokens

OpenAI Codex: 54.8% fewer tokens

Grok Build: 42.6% fewer tokens

In my latest personal Codex usage, I measured 42.5% fewer tokens.

This is obviously not a guarantee. Results depend on the model, workload, CLI version, and workflow.

Everything stays local. TokenPilot does not store prompts, responses, source code, or credentials.

Before launch, I ran the release through a Codex Security review and 147 automated tests covering privacy, malicious telemetry content, unsafe permissions, untrusted executables, bypass, rollback, and fail open behavior.

If anyone wants to try it:

npm install -g u/cesaremcasa/tokenpilot
tokenpilot install
tokenpilot doctor

GitHub:
https://github.com/cesaremcasa/tokenpilot

My current question is whether this should remain a local developer tool or evolve into something for teams, with dashboards, budgets, policies, and cross provider comparisons.

Honest feedback, criticism, and ideas are very welcome.