90 karma · joined May 29, 2023
I build open-source tools for developer workflows. Currently working on VibePod, which runs AI coding agents in Docker or Podman containers with traffic logging and local analytics. I also work on VoiceVault (conversation transcription and summaries) and SnyPy (a self-hosted code snippet manager).
Interested in Python, APIs, self-hosting, local LLMs, and understanding what coding agents actually do.
Blog: https://nezhar.com/ GitHub: https://github.com/nezhar VibePod: https://vibepod.dev/
Go to https://claude.ai/settings/usage, turn on extra usage and enable the promo from the notification afterwards.
I received €42, top up was not required and auto-reload is off.
On my desktop Chrome on Ubuntu, it seems to be persistent, but on my Android phone in Chrome, it loses the directory if I refresh.
I'm not sure how large the image becomes on the VM or if the distribution process is straightforward.
What I was also curious about is what is actually sent and received by the agent, so I included this feature and created a CLI to make integration easier in a developer workflow.
Since I started doing this for other agents as well, I considered the idea of using a VM with Vagrant. However, I want the setup to remain minimal, so I still believe there is room for improvement.
Regarding the second and third rules, I like to work with two terminals. One is for my agent, isolated in a container, and the other one I use for `git`. This way, I can assess whether my changes are moving in the right direction.
The PLAN.md files have also proven to be a good approach. I'm still trying to figure out the best way to keep them aligned with the application without polluting the context, but they hold significant value for documentation purposes.
1. API Proxy - Transparently logs all interactions with the Anthropic API. Every request/response is captured without modifying Claude Code itself.
2. Datasette Integration - Lets you query and visualize the captured API data with SQL. Useful for tracking token usage, analyzing prompt patterns, or debugging unexpected behavior.
The container itself provides isolation from the host system while maintaining persistent credentials and workspace access via bind mounts.
Happy to answer questions about the implementation or use cases.
The isolation here refers to the workspace. Since you run the CLI in a container, the process can only access what you have mapped inside. This is helpful if you want to avoid issues like this: https://hackaday.com/2025/07/23/vibe-coding-goes-wrong-as-ai...
* Audio Extraction: First, it extracts the audio from the video. * Speaker Diarization: It then identifies the different speakers in the audio. * Split Audio: The audio is split into smaller chunks based on the identified speakers. * Speech to Text: Each chunk is transcribed into text. * Combine ASR and Diarization: The transcriptions (from Automatic Speech Recognition) are combined with the diarization results to provide a structured, text-based dialogue for each identified speaker. * Summarization: Finally, the dialogue is condensed into a summary for a quick overview.
The entire process is containerized to ensure seamless and efficient operation. I'd love to get feedback or suggestions.