Inspiration
Engineering teams waste hours searching scattered code, docs, and PDFs. We wanted a context copilot that provides trusted answers bound to exact files and releases.
What it does
Bytebell ingests code, docs, and PDFs, builds a version-aware knowledge graph, and delivers answers with citations. It also ships with a Chrome extension that captures user context for sharper LLM results.
How we built it
We combined parsing pipelines for code and documents, added embeddings and a reranker, and connected everything to Slack, IDEs, and the browser through a Chrome extension.
Challenges we ran into
Handling large PDFs, aligning answers to exact file lines, and ensuring low latency across multiple interfaces were major challenges.
Accomplishments that we're proud of
We built a working context copilot live with five teams, cut onboarding time by more than ninety percent, and delivered answers always tied to sources.
What we learned
Context without receipts is noise. Binding every answer to files and releases builds trust and adoption.
What's next for Bytebell
Expanding pilots, adding release-aware snapshots and analytics, and scaling the Chrome extension into a universal context layer for developers.
Built With
- amazon-web-services
- cerebras
- mistral
- openrouter
- pinecone
- python
- together
- typescript

Log in or sign up for Devpost to join the conversation.