The latest articles on DEV Community by Slikti (@slikti). https://dev.to/slikti https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3933562%2F7b1f8575-bbdc-4d85-911f-1399a239037a.JPG https://dev.to/slikti en Slikti Fri, 15 May 2026 16:27:35 +0000 https://dev.to/slikti/looking-for-feedback-on-my-first-open-source-self-hosted-dev-tool-3p4i https://dev.to/slikti/looking-for-feedback-on-my-first-open-source-self-hosted-dev-tool-3p4i <p><strong>Hey everyone.</strong></p> <p>This is my first open source project, and I’m looking for honest feedback rather than trying to promote a finished product.</p> <p>I built a small self-hosted tool that lets me control Codex CLI or Claude Code from Telegram. The idea is that the bot, server, repos, and agent credentials stay on my own machine/server.</p> <p>The workflow I wanted:</p> <ul> <li>send a coding task from Telegram</li> <li>run it against a configured local repo</li> <li>inspect logs, git status, diffs, and checks</li> <li>require manual approval before deploy or rollback</li> <li>optionally run multi-agent “missions” with roles like product, designer, QA, frontend, backend, and builder</li> </ul> <p>It is still MVP-grade, and I know there are things to improve:</p> <ul> <li>better Mini App auth</li> <li>real task queue</li> <li>more tests</li> <li>safer server profile storage</li> <li>GitHub PR creation</li> <li>better docs and onboarding</li> </ul> <p>I’d appreciate feedback on:</p> <ul> <li>whether this idea is actually useful</li> <li>what looks unsafe</li> <li>what architecture choices I should rethink</li> <li>what would make it production-ready</li> </ul> <p>GitHub link, if anyone wants to inspect the code: <a href="https://github.com/slikti/agent-telegram-bridge" rel="noopener noreferrer">Git</a></p> agents ai opensource showdev