Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Introducing the Knowledge Base MCP. Greptile maintains a detailed knowledge base of how every part of your codebase works, as well as a history of past incidents. Starting today coding agents like Codex, Claude can access the Knowledge Base via Greptile's MCP, so they can use Greptile's learnings to...

64,850 görüntüleme • 9 gün önce •via X (Twitter)

22 Yorum

Greptile profil fotoğrafı
Greptile9 gün önce

Learn more:

Simantak profil fotoğrafı
Simantak9 gün önce

Yalls dont stop shipping do you. Love it team

Max profil fotoğrafı
Max9 gün önce

Greptile knowledge base is slept on. It's so powerful having all the context in one place & constantly evolving

Martin Jonsson profil fotoğrafı
Martin Jonsson9 gün önce

Does it work on historical? Lots of reviews behind me.

Saai Arora profil fotoğrafı
Saai Arora9 gün önce

Damnnn this is fire

Varik Verilion profil fotoğrafı
Varik Verilion9 gün önce

Incident history inside the coding loop is a useful addition.

EKOS _ AGI 🦊 🇮🇷 profil fotoğrafı
EKOS _ AGI 🦊 🇮🇷8 gün önce

This is where agent memory starts becoming real infrastructure. The next challenge is making that accumulated knowledge structured, versioned, and traceable — so agents don’t just remember what happened, but understand how that knowledge evolved and where it came from.

Yijie profil fotoğrafı
Yijie9 gün önce

production quality on this is crazy

cole murray profil fotoğrafı
cole murray9 gün önce

awesome!

Samuel Hu profil fotoğrafı
Samuel Hu9 gün önce

the history-of-incidents bit is what i actually want. most mcp demos can answer a file question, but the "why did we do this weird thing" context is the part i keep missing — does it update itself from prs or only docs?

Dominik profil fotoğrafı
Dominik9 gün önce

the useful boundary is not 'agent can read the codebase.' it is whether each retrieved fact carries provenance, freshness, and an owner. otherwise a knowledge base becomes another prompt-shaped authority with no way to tell stale guidance from a current constraint.

AWE profil fotoğrafı
AWE8 gün önce

does the incident history get pulled in automatically or does someone still have to write the postmortem

Ali Mirza | AI Agents & Automation profil fotoğrafı
Ali Mirza | AI Agents & Automation9 gün önce

hooking an mcp incident log directly into the subagent prompt stops it from making the same breaking imports twice.

Bessi profil fotoğrafı
Bessi8 gün önce

past incidents in the MCP. did not expect that

virtualuncle profil fotoğrafı
virtualuncle8 gün önce

most codebase context tools tell the agent how things work. knowing how it broke last time is a step past that

Mike Lopez profil fotoğrafı
Mike Lopez8 gün önce

How do you prevent stale architectural knowledge from becoming authoritative context for the agent?

Mohamed Khlifa profil fotoğrafı
Mohamed Khlifa9 gün önce

What is the difference between it and things like onsidian git that is free and most common for users ?.

0xdotdot profil fotoğrafı
0xdotdot9 gün önce

fire

Omair-Inam Abdul-Matin profil fotoğrafı
Omair-Inam Abdul-Matin9 gün önce

How much will this cost?

Jag profil fotoğrafı
Jag9 gün önce

Interesting. So all the code base replicates to greptile?

AI Mastery Guide profil fotoğrafı
AI Mastery Guide9 gün önce

past incidents remembered, that's smart

TonkaToyXL | AI Test Cabin profil fotoğrafı
TonkaToyXL | AI Test Cabin8 gün önce

This is the missing piece for coding agents. Giving them a living map of the codebase and past incidents is how they stop guessing and start helping for real.

Benzer Videolar