I’m the author of Ephemora Skyline, an open-source desktop web app that maps a local codebase as a living 3D city.The idea is simple:

•folders become districts

•files become buildings

•taller buildings represent higher measured complexity

•security findings appear as visible landmarks

•Security Tour takes you from a finding to its file and line

The project is designed to run locally: no account, no login, and no telemetry. It does not claim that a finding is a proven exploit; each result is tied to the scanner, file, line, and matched source context so it can be checked.

I made a short demo showing the city being built and the Security Tour in action:https://github.com/MichaelS1011/Ephemora-Skyline

I’d especially like feedback from developers who work with large repositories: does a spatial view help you decide where to investigate next, or would another representation be more useful?

Hi all, I heard about this new community in TheVerge. I think it's owning an important place in a defining moment about how we approach engineering. That's aligned with what I want to share here.

Source code: https://github.com/ascendaone-com/ai-engineer-tools

Now as AI-engineers, we are spinning up 10s of agents simultaneously, managing PRs and landing the code. We've gone from crafting code line by line to supervising agents. The shape of the work has changed.

There are many OSS projects that can read your token spend eg: tokscale; or telemetry AgentTelemetry, YC has Paxel but I couldn't find any that created a standard across all coding agents for emitting agent activity eg: tool.started, / failed, agent.waiting.

The repo has a common schema that standardises these events.

The repo contains collectors for Claude Code, Codex, Cursor, GitHub Copilot with a common event schema to normalise activity across tools.

Everything runs locally. No prompts or source code collected.

There are many use-cases for reading the telemetry: we're running a research and benchmarking project. We've also developed an MacOS App to be able to visualise what your agents are doing. You can even build your own screensaver on this so when all your agents are done you can return to your machine. Here's an example you can install (instructions in the repo)

The collectors are Apache-2.0 so over to you on how you might use them.

Go forth, fork and/or contribute 🚀
AI-assisted PRs welcomed.

Openly, other coding agents like Gemini CLI, Windsurf etc are supported based on documentation, but at this stage testing is light so if you can try it out. I can give you early access to the Flow app to visualise and check data so hit me up.

Feedback, thoughts or suggestions?

I nerd out on this stuff daily so love to discuss Agentic work.

Source: https://github.com/OpenTubeX/OpenTubeX

Downloads: https://opentubex.org/downloads/

Processing img 9qjxini616yh1...

Processing img u0cfvaj616yh1...

OpenTubeX is for people who want to watch YouTube without ads or a Google account. It doesn't load YouTube's website or its JavaScript, and your subscriptions, playlists and history stay on your device. It's AGPL-3.0 and still in beta.

What it adds. The open-source YouTube clients I know of each cover one platform. OpenTubeX runs on Windows, macOS, Linux and Android from one codebase, has experimental iOS/iPadOS builds, and can sync your library between your devices. Sync is end-to-end encrypted on a compatible server, and you pair a new device with a QR code. It also combines features I haven't found together in another client:

• Browser-style tabs with pinning and grouping, a queue, and a mini-player that keeps playing while you browse
• Per-channel feed controls for videos, Shorts, live streams and posts, plus per-channel playback speed, quality and subtitles
• Optional recommendations, ranked on your device from your watch history and feedback
• SponsorBlock, including submitting segments from the player, and DeArrow
• Downloads and playback from other sites through yt-dlp
• Themes, a configurable Home page, a command palette and gamepad navigation

How it's built. AI agents wrote most of the code, mostly Claude Code and Codex. I decide what goes in, review and test the changes, and send them back when they're wrong. Every PR runs unit tests, linting, CodeQL and a Playwright end-to-end suite against the desktop app, and Android changes get tested on an emulator. Each PR description names the model that made it. The project has been in daily development since January 2026, with nightly builds.

You can install it through WinGet, Homebrew, APT, RPM/COPR, Flatpak, Snap, Nix or the AUR. On Android, use our F-Droid repo or Obtainium.

Bug reports and questions are welcome.

Hi r/TrueOpenSource, I'm David, one of the two developers of Oxynote. My friend Simon and I also maintain ttlcache, a Go caching library with about 1,300 GitHub stars, so this isn't our first open-source project.

I've spent 8 years writing software, 2 of them as an SRE and 3 as a team lead. Every team I've been on had the same documentation problem. The useful stuff lived in someone's head or a private Slack thread, and the wiki was full of stale docs nobody could find.

So we set out to solve this problem by building Oxynote, a self-hosted wiki for engineering teams. Pages hold text and live charts side by side, and the charts pull fresh data from Prometheus or a database (PostgreSQL, MySQL, MariaDB) whenever someone opens the page. Changes to important pages go through a draft and a diff that a teammate approves, like a pull request, and several people can edit the same page at once. AI agents can read and edit pages too, through the built-in assistant or over MCP, but that part is optional.

The name comes from oxygen + note: docs that breathe. Live data gives people a reason to open the wiki every day, and docs people open every day stay up to date.

Things worth knowing before you try it:

- You run one Docker container on your own server, and your team uses it in the browser.

- There's no hosted version and no account with us. Your docs and data stay on your server.

- It's at version 0.9, so it's still early in development.

- It's made for tech teams and the systems they run, not as a wiki for a whole company.

It's Apache-2.0. The backend is Go, and the editor is built on Nuxt, Tiptap, and Yjs, with Hocuspocus for live editing and Better Auth for sign-in, so it also includes a lot of other people's open-source work.

GitHub: https://github.com/oxynote/oxynote

We started it about a year ago, and we made it public about 3 months ago. If you have any questions, feedback, or suggestions, feel free to reach out. I'm happy to answer any questions.

Thanks for the new subreddit! :)

I wanted to post about my project, which is an open-source alternative to Hamachi, Radmin, and ZeroTier. The project has two active developers.

How does it work?

- Peers find each other via BitTorrent trackers, BitTorrent DHT, or through other peers (peer exchange). No central server to rely on or pay for.

- Built-in NAT traversal. Since 0.14, RUDP with UDP hole punching is the default transport, so two nodes behind NAT can connect directly.

- L2 virtual LAN. Works with games and software that need broadcast/multicast.

- Cross-platform. Windows, Linux, FreeBSD and MacOS.

- GUI and headless modes. Use the tray app, or run it in the background from the CLI. There is also an experimental GraalVM native-image build of the headless version for Linux x86_64.

Every contribution helps me keep fixing bugs, testing on more platforms and adding new features.

Donations, stars on GitLab, bug reports and feedback are just as appreciated. Thank you!

- Gitlab: https://gitlab.com/Monsterovich/lanemu
- Our discord: https://discord.com/invite/m7VhRTQnCU

Hi,

I kept running several coding agents at once and lost track of them across terminal tabs, so I built a desktop app for it.

OpenVibe puts each agent in a real terminal (a PTY, not a chat wrapper) on an Excalidraw canvas. It works with Claude Code, Codex, Gemini CLI, Aider, Ollama or any command you type.

What it does today:

- group agents into teams and send one instruction to a whole group (@frontend ...), or a slash command to all of them

- review what an agent changed, click a diff line to leave a remark, send all remarks back in one message

- an orchestrator mode: a Claude Code session plans the task, gives each agent its own git branch and worktree, tracks a time budget and merges into a mission branch. It never pushes and never merges into your branch w/o permissions. The orchestrator even have a router mode that distribute the tasks to a smaller model if the tasks doesn't need a big model

Everything stays on your machine. No cloud service, no telemetry, and it doesn't skip the agents' permission prompts. The Rust side handles the PTYs, git, SQLite and a localhost-only HTTP server and the UI is React.

Currently, it's only on Windows 11/11 but I'm really open to have it for everyone.

Two things I'd like feedback on:

1. Is the orchestrator useful to you ?

2. Anyone interested in a macOS/Linux port? portable-pty already supports both, the work is mostly around paths and shells.

Repo: https://github.com/Mideky-hub/openvibe

Demos: https://mathieukerbel.com/projects/openvibe

Hi! I would like to announce, that I've created a social app. Details here: https://robertostrowskijagoda.github.io/Zen/about/

https://www.reddit.com/r/TrueOpenSource/s/jB8fuAtDTq The post was very relevant to open source and yet locked.

It has begun. At the core it's the same drive. The holier than though attitude, silencing, and very soon - immediately once possible - random banning

While the post being locked is very relevant to discuss when open source is concerned.

The problem is inherent in Reddit, whose mechanics gives unlimited power to control-hungry mods. I've had enough of this.

This post will very likely be locked, removed, and I'll be banned. Funny and ironic. But I don't really care. Good luck with this - and all the next r/TheNewOpenSource, r/TheRealTrueOpenSource, r/ComeHereWeLoveAI and so on. All mod fantasies.