Synapse
A self-hosted AI agent platform running across WhatsApp, Telegram, Discord, and Slack.
Built independently
tests
commits
LLM providers routed
- Python
- FastAPI
- LanceDB
- SQLite FTS5
- asyncio

I’m an Associate Software Engineer at Accenture. Outside work, I build systems like Synapse that report on their own state.
Kolkata, India · open to remote
Status: immediate joiner
… page loads since 2026-08-16
contributions, last 12 months, public and private repos
commits to public repos, last 12 months
repositories, 18 public
stars across public repos
At Accenture I keep a production system running, which mostly means finding out why something broke when the symptom and the cause sit in different places. The parts that repeat, I automate: when the same questions kept routing through me, I put a read-only Claude agent over a 2,300-table database so they could be answered without me. Outside work I build that same infrastructure deliberately (retrieval systems, message routers, knowledge graphs), and I publish the numbers, not just the code, because a claim you cannot check is just marketing.
On /lab there is a chat that answers questions about my work, background, and availability from 72 answers I wrote and sourced myself. Retrieval runs in your browser; on hardware that can carry it, a small language model answers in its own words, grounded in those same answers, and a question I have not written about gets an honest not-on-record reply instead of a guess. Nothing you type is sent anywhere unless you choose to email me the conversation. When you want the human: book a 30-minute call with me, or send the conversation to my inbox from the chat and I reply personally.
A self-hosted AI agent platform running across WhatsApp, Telegram, Discord, and Slack.
Built independently
tests
commits
LLM providers routed
Turns any repository into an onboarding site: dependency graphs, directory maps, framework cookbooks.
Built independently
npm downloads, trailing year
A universal intent router for Claude Code, matching fast-path first and falling back to dynamic skill discovery.
Built independently
npm downloads, first 30 days
npm downloads, trailing year
npm downloads, trailing 30d
Synapse's knowledge graph moved from an in-memory NetworkX object to a SQLite-backed schema. What moved, what stayed compatible on purpose, and the benchmark I still owe.
Synapse routes across a wide provider list behind one router. A rate limit, an auth failure, and a context overflow all need a different response, and the honest cost of how it tells them apart.
Four channel adapters, one shared ingestion layer. What FloodGate, dedup, and a capped asyncio queue guarantee under a concurrent burst, and what the evidence for it actually is.
Rebuilding Synapse’s rerank stage; writing up the retrieval trace format for /lab.