Ask HN: How do you manage your AI agents' context across clients and projects?
20 comments
- Points9
- Comments5
20 comments
Hi Guys, like many of you I work with AI agents every day and across several clients. The major time cost for me is to re-explaining context and past decisions, client rules, that we already do. To finish every tools as its own memory. So I’m curious how you actually handle this: 1. When you start a new session, how do you give context to the agent (context came from chat, mail, ticket ...) ? 2. Do you use more than one agent type (claude, codex ...) ? And if yes, how do you carry context…
Story details from Hacker News ↗.
Ask HN: How do you manage your AI agents' context across clients and projects? was first seen on Hacker News · Front page on Nov 9, 2026. Since then it has appeared in 9 checks on 1 different day. Its best position was #24 of 30, reached on Nov 9, 04:39 UTC. It is #25 right now, holding steady at #25 over the last 6 checks.
Position on Hacker News · Front page at every check (lower is better).
Best rank per day (UTC).
points as reported by Hacker News.
A few top-level comments from Hacker News, shortened. Read the full thread on Hacker News.
Matt Pocock's skills library^1 is the basis for my approach. 1. https://github.com/mattpocock/skills/blob/main/README.md
Gitea wiki. Tell it to reference previous projects if applicable, standard setup principals etc.
Spec driven design helps, OpenSpec/Git SDD Kit/ GitShipDone helps with the previous decision problems and design context. Most of these live in the project repos so they won’t pollute each other
Archived daily, weekly and monthly lists that include this entry.
Yes. As of Nov 9, 05:24 UTC it is #25, holding steady at #25 over the last 6 checks.
#24 on Hacker News · Front page, on Nov 9, 04:39 UTC. Trendoday checks this list every 15 minutes.
It was first seen on Nov 9, 2026 and has been on the list on 1 day (9 checks) since.
9 points and 5 comments; submitted by Michel_Aventin on Nov 7, 2026.