GraphSlice Blog
Notes on code graphs & AI context
Notes on semantic code graphs, C# code intelligence, and feeding LLMs the context they actually need.
The codebase nobody fully remembers
Every long-lived .NET shop has one: a solution that works, ships, and quietly outlived everyone who ever understood it. A story about institutional memory and the one participant that never forgot.
Read →Are we still talking loops, or did we shift to graphs yet?
The godfather of the agentic scene dropped a six-word tweet about loops and graphs, and 2.5 million people looked up. He didn't mean us. Probably. Here's what a graph-shaped question could mean, and why the arrow points our way.
Read →Compu-Global-Hyper-Mega-Net (or, how GraphSlice got its name)
Naming a company is the worst part of starting one. Ask Homer Simpson, who got as far as Interslice before losing his nerve and going with Compu-Global-Hyper-Mega-Net...
Read →We like Goose
Goose is Block's open-source AI agent. It's a CLI, plus a desktop app that's really just a GUI over the same config, plus a genuinely useful set of MCP servers in the box. Here's why it's the harness we keep reaching for.
Read →Why your AI assistant should query your architecture, not your files
File dumps and embeddings break down on large C# codebases. A semantic code graph gives an LLM the exact dependency paths a question needs — nothing more.
Read →What is a context slice?
A context slice is the minimal subgraph of your codebase that answers one question. Here's how GraphSlice extracts one, and why the boundaries matter.
Read →