Agents
Context harnessing is super challenging to do right: what info needs to be collected, how to accumulate it into a knowledge graph, how to ke…
Context harnessing is super challenging to do right: what info needs to be collected, how to accumulate it into a knowledge graph, how to keep it up to date, etc... Super excited for @QodoAI, harnessi
Context harnessing is super challenging to do right: what info needs to be collected, how to accumulate it into a knowledge graph, how to keep it up to date, etc... Super excited for @QodoAI, harnessing the info in @Atlassian's product portfolio, so engineering teams can get grounded, high-quality code review and code governance Qodo now runs natively across the Atlassian stack: - agentic review in Bitbucket - requirements from Jira - engineering standards from Confluence More than 1 million Qodo code reviews have already run on Bitbucket. Read more: http://qodo.ai/blog/code-governance-for-the-atlassian-…
Related
- This is the right frame. We’re currently designing our agent memory platform, and the hardest part isn’t storage — it’s deciding what to rem…
- I fed The Godfather into a structured knowledge graph, here's what the MCP tools surface
- Stop bloating your agent context with MEMORY.md. I built a local cognitive memory MCP instead.
- Active Graph is the best, most 'correct' knowledge/context engine I've come across so far (and I've tried or at least researched most of the…
- we built the @hyperspell filesystem around this principle every source in your company feeds into a context graph where we resolve conflicts…
Source: Itamar Friedman (X) | 2026-07-14