HN Explorer

Ask HN: Heavy coding-agent users what's your context plumbing? Where it fails?

4 points by srbsa ↗ HN
From what I've seen it sits at three levels:

Layer 1: Personal (memory MCP tools, personal *.md files) Layer 2: Repo (CLAUDE or AGENTS.md, in-repo docs) Layer 3: Org-wide (Unblocked, Glean, or similar)

Most people have strong opinions on 1 and 2. Layer 3 seems underinvested.

Curious, do you think 1 and 2 make 3 redundant, or would a strong 3 mean you'd stop/reduce patching with 1 and 2?

6 comments

[ 3.1 ms ] story [ 23.9 ms ] thread
bohdanstefaniuk
From my team experience repo level documentation, skills and agents are enough to share similar approach of using AI among the team. We also trying to adopt journals for AI. Basically generate a single md file after each conversation to have a context of what was done.

For me the biggest pain right now is to have some kind of central place where other team can post skills they use, prompts and other things. Right now we are thinking about creating a separate repo to store custom skills and other stuff so each team can contribute and use others team work.

snapsynapse
I solve layer one and global layer two needs with things like https://agentlink.run/

As for layer three, a similar pattern with a local fallback should work. But I've not seen anybody do that yet.