Building a 4-Agent Software Team on Telegram, With InsForge as the Backend Layer

I just built a 4-agent software team. (100% local and runs on open-source stack) Everything runs from Telegram and is managed on a Kanban board. - A project manager who plans the work - A backend developer - A frontend developer - And a tester The PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. The thing that makes them a team instead of four strangers is a shared kanban board. Every task is a row, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. The next agent reads that summary before it starts. So the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. The hardest part I faced when setting this up was building an agent that could actually act like a backend engineer. A backend engineer has to stand up a database, wire auth, manage storage, deploy functions, and keep all of it consistent while the rest of the team builds on top. An agent doing this from scratch failed almost every time in my run. It burned its context window, remembering which tables existed and which endpoint it created. Due to this, the work context exhausted quickly. I solved this by adding InsForge as the backend context engineering layer. It is an open-source, agent-native backend, and I added it to our backend developer agent as a skill. With InsForge installed, the agent stopped improvising infrastructure and followed a reliable path to create the project, define the database, set up auth, and deploy functions. To test the whole team, I had them build a working Google Docs clone, AI features included. The backend agent spun up the full service on its own, like database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. The frontend agent read that summary and built the UI on top of it, and the tester closed the loop. InsForge GitHub: https://lnkd.in/gZQ3CVva (don't forget to star 🌟) ____ Share this with your network if you found this insightful ♻️ Find me → Avi Chawla. Every day, I share tutorials and insights on DS, ML, LLMs, and RAGs.

This is primarily a personal build description, so most of it (the specific Telegram/Kanban orchestration, the 4-agent team, the Google Docs clone test) is a first-person account I can't independently verify — similar to other "I built X" posts. What I can check is the one concrete tool named: InsForge.

Confirmed accurate:

• InsForge is a real, actively maintained open-source project: it's an all-in-one, open-source backend platform for agentic coding that gives coding agents database, auth, storage, compute, hosting, and an AI gateway to ship full-stack apps end-to-end. GitHub
• The "backend context engineering layer" framing matches how the project describes itself: agents can read backend context and state — pulling documentation, schemas, metadata like deployed functions and auth config, and runtime logs — so the agent has what it needs to write code, verify what it built, and debug when something breaks, rather than improvising infrastructure from scratch each time. GitHub
• The specific capabilities the post lists (create project, define database, set up auth, deploy functions) match InsForge's documented feature set: a fully managed PostgreSQL database with pgvector support, built-in authentication and session handling configurable by agents, S3-compatible storage, and serverless edge functions running on Deno, all deployable and configurable by agents via CLI or MCP. Everydev
• "Edge functions running real TypeScript" is accurate: Edge Functions run on a lightweight serverless runtime powered by Deno, and Deno natively executes TypeScript, so this isn't an exaggeration. Alternative AI Tools
• It genuinely is installable as an agent "skill": InsForge offers CLI + Skills that agents invoke directly from the terminal, matching the post's "I added it... as a skill" framing. GitHub
• It's genuinely open-source under a permissive license: InsForge is licensed under Apache 2.0, with the full platform source code publicly available on GitHub. Everydev

Not independently verifiable:

• The specific claim that an agent "burned its context window" trying to track database schema state from scratch is a plausible and commonly reported failure mode for coding agents doing raw infrastructure work, but it's the author's own experience, not something I can check.
• The 4-agent Telegram/Kanban orchestration, the Google Docs clone build, and the described handoff behavior between agents are all part of the author's personal project and outside what I can verify.

No red flags — the one externally-checkable claim (InsForge and its capabilities) holds up accurately against the project's own documentation.