Faceless. Nameless. I just build the simulation. “I can only show you the door. You’re the one that has to walk through it.”

  • 2 posts
  • 7 comments
Joined 8 days ago
Cake day: June 29th, 2026

Hy,

I wanted to share a desktop client I’ve been building and recently open-sourced under the GPL-3.0 license: DWN.BRIDGE (C# WPF, targeting .NET 10). It is designed to solve the data privacy issue when using web LLMs (like Gemini) to analyze files or query local databases. It exposes a local orchestration bridge to your browser session via WebView2 automation, bypassing developer API paywalls while keeping your raw data offline. Key Features:

  • Zero-Knowledge Schema Mapping: It extracts table headers and column metadata locally. It sends only this structure to the web LLM. The LLM acts purely as a logic generator, and the client runs the SQL query locally using native providers (Dapper/SqlClient). Raw data rows never leave your hard drive.
  • Process Sandboxing & Consent: Every shell script execution, SQL write, or file modification requested by the agent is paused. The client prompts you with a WPF modal showing a git-style diff of the command/file for manual approval.
  • Coder Compilation Loop: If the agent generates scripts, it compiles and runs unit tests locally, feeding error logs (stderr) back to the context window until it builds successfully. The codebase is completely audit-friendly. I’d love to get feedback on the security consent model or contributions on expanding local DB support! 📺 Demo Video: https://www.youtube.com/watch?v=dCtOsXAuPgc 🔗 GitHub: https://github.com/MarckDWN/DWN.BRIDGE

Hey programmers,

I wanted to share a desktop client I’ve been building: DWN.BRIDGE (fully open-source C# WPF).

I love using AI for data analysis (like cleaning CSVs or querying databases), but there was no way I was going to upload my private/corporate files to cloud LLMs.

So I built a Zero-Knowledge local bridge:

When you point the client to a local database (SQL Server, SQLite, Excel, CSV), the client extracts ONLY the table schemas/headers locally. It sends the schema metadata to the LLM (Gemini web UI) via a secure browser-automation bridge. The LLM writes the SQL query, and the client executes it locally on your computer. Your raw rows and records never leave your hard drive. All local file system access and system commands run locally and require explicit pop-up confirmation. You can check out the source code or download the installer below. I’d love to get feedback on the local sandboxing model! watch the demo videos I uploaded on my youtube channel (links on github)

🔗 GitHub: https://github.com/MarckDWN/DWN.BRIDGE

Hey programmers,

I wanted to share a desktop client I’ve been building: DWN.BRIDGE (fully open-source C# WPF).

I love using AI for data analysis (like cleaning CSVs or querying databases), but there was no way I was going to upload my private/corporate files to cloud LLMs.

So I built a Zero-Knowledge local bridge:

  • When you point the client to a local database (SQL Server, SQLite, Excel, CSV), the client extracts ONLY the table schemas/headers locally.
  • It sends the schema metadata to the LLM (Gemini web UI) via a secure browser-automation bridge.
  • The LLM writes the SQL query, and the client executes it locally on your computer. Your raw rows and records never leave your hard drive.
  • All local file system access and system commands run locally and require explicit pop-up confirmation.

You can check out the source code or download the installer below. I’d love to get feedback on the local sandboxing model! watch the demo videos I uploaded on my youtube channel (links on github)

🔗 GitHub: https://github.com/MarckDWN/DWN.BRIDGE

  • you are a senior developer, start to transform your view in a senior architect. With AI there’s no more need of developers. An architect ius needed, and if it haas a solid dev backround as yours projects will change view. Technology is always changing and it’s hard to stay at pace. But if you look from an higher perspective your project your experience will only help the AI to do the Job for you

  • The most important thing developers forget is planning. I am senior and used to delegate dev to Junior Devs. If you have not enough experience in software architecture you are missing the most important thig: You cannot start developing. You must start planning, first of all require your agent to plan the steps for the target mission. Than examine the plan produced, ask to divide int single in testable units. Most AI Vibe programmers start with develop directions. That is wrong. The longest part of the job is to prepare the Agent to perform correctly

  • The problem isn’t the tool; it’s the lack of engineering foundations. Generalizing all AI-assisted development as ‘vibe coding’ is a massive oversimplification. There is a vast difference between a beginner blindly copy-pasting LLM output into a codebase they don’t understand, and a senior architect using LLMs as a high-powered assistant to speed up boilerplate, local schema generation, or parsing scripts. When you already know exactly how the underlying system operates, how memory is managed, and how to design clean software architectures, the LLM is just a productivity multiplier. You still design the data flow, audit the tool-use sandboxes, and review every single line of code. It doesn’t replace thinking; it replaces tedious typing.