Insights
News
Thoughts on AI context, token optimization, and building tools for developers.
Your Reading Library Just Got a Knowledge Graph
Most read-later apps give you a list. A knowledge graph makes the invisible connections between your saved articles visible — clusters, threads, relationships the list never showed you.
We Just Launched a Live Embeddings API. Here's the Whole Story.
The origin story, what makes PyckLM different, pricing, billing architecture, and what's next.
Why Generic Embedding Models Fail at Code Search (And What to Do About It)
The vocabulary gap, L0/L1/L2 query framework, why fine-tuning alone doesn't fix it, and the compounding advantage of owning your retrieval model.
Your Codebase Has Its Own Language—And Your AI Doesn't Speak It
Every development team invents a dialect. Your AI needs to understand it.
Configuration Should Travel With You
You spend time configuring your AI tools on one machine. Then you switch to another and start over. That gap is the problem.
We Trained Our Own Code Embedding Model From Scratch. Here's What Happened.
Code search has a specific problem that generic embedding models aren't built to solve. So we built one that is.
Your Team's Knowledge Lives in Multiple Places, and Your AI Only Sees One.
You're debugging a production issue. The AI helps you trace it to a module. You ask why it was built that way. It doesn't know.
Search Is Commoditized. Memory Is the Moat.
Semantic search over a codebase felt like a differentiator 18 months ago. Today it's table stakes. Memory is what comes next.
Why Some Tools Age and Others Compound
Day one with a new AI assistant is rough. You spend more time explaining context than getting help. Some tools fix this. Most don't.
The Agent Loop: How Router Searches Until It Finds
Most AI tools make one retrieval attempt per question. Router loops — searching, reasoning, searching again.
Automated PR Reviews That Actually Know Your Codebase
Generic AI PR review tools flag style issues. Pyckle's diff review uses your actual codebase context.
Session Memory: Why Your AI Should Remember What You Worked On
Every new Claude session starts with amnesia. Session memory fixes that.
Notion Meets Code: Indexing Your Wiki Alongside Your Codebase
Your architecture decisions live in Notion. Your code lives in Git. Pyckle bridges the gap.
Why Your AI Can't Parse Your Mobile Code (And How Tree-sitter Fixes It)
AI coding tools excel at Python and TypeScript but fail on Java, Kotlin, and Swift. Tree-sitter AST parsing delivers accurate code search for mobile developers.
Your Codebase Has Its Own Language
Embedding models are trained on massive datasets — books, articles, documentation. Your codebase speaks a different dialect entirely.
One Index, Every Editor
Developer teams use multiple editors and AI tools. Each tool builds its own context from scratch. MCP changes this by separating the context layer from the editor.
The Flat Index Problem Nobody Talks About
Flat codebase indexing treats auth/login.py and tests/test_auth.py as equal neighbors. Code has structural relationships that embeddings cannot capture.
The Developer Reading List Problem
Developers accumulate technical articles, tutorials, GitHub issues, and documentation while solving problems. Finding what you saved requires remembering why you saved it.
AI Code Context Without the Lock-In
Don't leave your IDE. Just make it smarter. Pyckle gives any AI editor deep codebase context via MCP — model-agnostic, local-first. No vendor lock-in.