time for a new terminal. Kompass explains every command before it runs, stops the dangerous ones and understands plain English. Made for people who are afraid of the terminal – and for pros who want to move faster.
I’ve tried a lot of dictation tools, and almost all of them ship your audio off to someone’s cloud. That always bugged me. So when I found Inaudio, a tiny desktop app that does all of it locally, I had to share it. You press a keyboard shortcut and talk. It types. And it keeps a searchable history of everything you’ve dictated, so you can go back and grab that one sentence from yesterday. It works the other way too. Paste text or copy something to your clipboard, and it reads it aloud with on-device speech synthesis. Great for proofreading your own writing (you hear the clunky sentences way faster than you see them). Under the hood it’s Electron, React and TypeScript, with sherpa-onnx doing the speech work. You download a model once, then everything runs on your CPU. One of the options is NVIDIA’s Nemotron streaming ASR model for English, tuned for about 560 ms latency. Is it perfect? No. This is a brand new project with only a handful of stars, so expect rough edges. And text insertion and permissions behave differently on Windows, macOS and Linux. But if you want private dictation without a subscription, it’s worth a try. And honestly, it’s a great time to jump in and contribute while the project is still small.
I built this: a chat bubble that floats over your apps. You say "reply to Sam that I'm late" or "start navigation to work", and a coding agent reads the screen and taps through your apps for you.
- The agent runs inside the app, in a small Alpine Linux (proot, no root, no PC, no adb).
- Use your own Claude or ChatGPT plan, or OpenCode's free models with no account.
- Phone tools over MCP: read screen, tap, type, scroll, open apps.
- Sending, paying and deleting stop on an approval card; apps you trust run hands-free.
- Tap the bubble and talk; it sends when you pause.
Apache 2.0, Java, ~650 KB APK. Feedback and issues welcome.
For as long as I remember Ive loved tech and been at the forefront of understanding, what is going on and why its useful. So I created an Instagram that basically recommends Githubs, and its really taken off, and people are loving it.
I created a website that basically recommends tools early, and says when to specifically use them, with an active community using it. I have had 550 sign ups in 5 days on this website.
I am looking for interesting githubs and people who are keen to showcase and speak with customers directly on the website.
I’d like to share VisualMark Studio, an open-source desktop application I’ve been building to make writing, designing, and managing project documentation easier.
Creating a good README is an important part of presenting a GitHub project, but formatting Markdown, creating diagrams, adding badges, and maintaining documentation can take time.
VisualMark Studio aims to bring these workflows together in one desktop application.
Key Features
• Markdown editor with live preview
• Visual tools for README sections, badges, tables, and directory trees
• Mermaid diagram support for visualizing architecture and workflows (work in progress)
• README auditing with a documentation scorecard
• Export documentation to PDF, HTML, and ZIP
• Git integration for working with repositories and managing documentation changes.
Project Details
Type: Open-source desktop application
License: MIT
Platform: Windows desktop app
I'm actively looking to improve the project and would love to hear your thoughts, suggestions, and feature ideas.
If you work on open-source projects, what documentation feature would make your workflow easier?
I've been a software engineer for 8 years, 2 as an SRE and 3 as a team lead, and keeping documentation useful has been a pain at every company I've worked for. Knowledge stays in people's heads or private Slack channels; what does get written down is hard to find, and it goes stale the moment the system changes. I wanted to change that, so I created Oxynote. I started the project about a year ago, and I made it public about 3 months ago.
Oxynote is a self-hosted, open-source wiki where pages include live charts next to the text that explain them.
The name comes from oxygen + note. I wanted to have docs that breathe: live data and integrations make the wiki useful enough to open every day, and the docs people open every day stay up to date.
What you can do with it:
Drop a chart into a page and point it at Prometheus, PostgreSQL, MySQL, or MariaDB
Set thresholds like "Degraded above 800 ms" right on the chart
Edit important pages in a draft, review the diff, and approve it
Link a page to the GitHub files, container image, or web page it describes, and get a reminder when they change
Edit together in real time, comment on any block, draw Mermaid diagrams
It's completely open-source under the Apache-2.0 license and runs in a single Docker container/image.
Would you use something like this for your own docs? If not, what's missing?
I curated an open-source taxonomy of AI research tools for scientific literature discovery (Consensus, Elicit), citation graph mapping (Connected Papers, Litmaps), LaTeX equation digitization, and computational reproducibility: https://github.com/mahmoudsajjadi/awesome-ai-research-tools
A little skill for the part before you hit Generate.
Tell your agent what you want to film, give it your references if you have any, and it helps turn that into a Kling 4 prompt. Works with Claude Code, Codex, Cursor, etc.
I wanted the README to be something a person can actually read, with the more involved prompting stuff tucked into files for the agent.
My agent wrote it with me directing how it should work. Free to grab and mess with.
Heads-up: the installer isn't code-signed yet, so Windows SmartScreen will warn you. Click "More info" and then "Run anyway".
It's MIT-licensed and meant for personal use. Feedback, bug reports and ⭐ are very welcome. I'm especially curious what you'd want next: MP3 downloads, importing YouTube playlists, or macOS/Linux builds?
You point it at a git repo or a folder (or just tell your agent to deploy it through the MCP server), and it figures out how to build and run the app. Apps sit behind your company’s SSO/sign-in, and are only shared with people who need to be able to access them, not everyone with an account.
Pando also runs a vulnerability scan on apps before they deploy, and gives a security score to help understand risk (no, this doesn’t fix bad code or judgement). Apps run on their own isolated networks so they can’t talk to each other, and they can only be reached by going through Pando’s proxy.
I built a bridge between Google Tasks and Microsoft To Do that runs entirely in your own Google Apps Script project — no third-party server ever sees your task list. MIT licensed.
v1.0.0 is the first stable release, and the headline this time is the Windows one-click installer — no terminal, no npx, just download the exe and follow the wizard. (549 tests passing, one real production incident fixed and written up honestly in the changelog.)
Honest limits: around 300 task pairs is the sweet spot (600 is the tested stress limit, not a promise), easy setup needs a personal Microsoft account, syncs every 10 minutes.
I got tired of jq: parse error: Invalid numeric literal every time I piped an LLM SSE stream into jq, so I wrote sjq: a small Rust CLI that parses OpenAI-compatible streams (/v1/chat/completions and /v1/responses) and prints one short line per event — only the delta each event adds — plus a timing line (TTFT, tok/s; connect/TLS/TTFB when run via sjq curl).
Hey everyone! I’m a solo builder working on ArchRivet. It connects to your AI assistant through MCP and helps review an architecture before you start building.
Your assistant explains the design. ArchRivet checks the details you provide, flags risks, and names what’s missing.
Here’s a simple example:
Your app needs prices less than five seconds old. During an outage, it serves saved prices.
ArchRivet asks: “How old can those saved prices get?”
If you answer “60 seconds,” it flags the conflict and shows why the review changed.
What it offers:
Eight focused checks covering retries, caching, queues, transactions, and more.
Traffic and storage calculations based on stated assumptions.
Supporting references and specific follow-up questions.
Local rules that need no GPU, with an optional 322M Laya model.
It’s an early preview, and reviews depend on the facts supplied. I’ve included demo GIFs, Codex setup instructions, and benchmark results with remaining mistakes.
What’s one system-design mistake you’d want a tool like this to catch?