Viewing profile — das-bikash-dev

the worktree isolation per agent is clever. i've been running claude code as my sole dev partner on a production platform (10 repos) and the biggest unlock was treating context as …

the DAG decomposition approach is interesting — curious how it handles goals that span multiple services/repos. i build a multi-service platform solo with claude code and the harde…

the context isolation approach is smart — cascading drift between agents is a real problem. i run 10 microservices with claude code and solved a similar issue by maintaining curate…

Interesting to see the evolution mapped out like this. For those building on top of these models (RAG systems, agent frameworks), the real inflection point wasn't just model count …

How does Emdash handle state management when running multiple agents on the same codebase? Particularly interested in how you prevent conflicts when agents are making concurrent mo…

This matches my experience. I work across a multi-repo microservice setup with Claude Code and the .env file is honestly the least of it. The cases that bite me: 1. Docker build ar…

The multi-agent budget problem you're describing gets even harder when the services are heterogeneous. In a RAG pipeline, a single user query might hit: query analysis (LLM call), …

Re: when to add a WebSocket gateway vs keeping it in the monolith — I've built multi-channel chat infrastructure and the honest answer is: keep the monolith until you have a specif…

Nice project, especially given the VRAM constraints. A few things I've learned building production RAG that might help: 1. Separate your query analysis from retrieval. A single LLM…