Загрузка видео...

Не удалось загрузить видео

На главную

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 просмотров • 9 дней назад •via X (Twitter)

Комментарии: 22

Фото профиля Greptile
Greptile9 дней назад

Learn more:

Фото профиля Simantak
Simantak9 дней назад

Yalls dont stop shipping do you. Love it team

Фото профиля Max
Max9 дней назад

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

Фото профиля Martin Jonsson
Martin Jonsson9 дней назад

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

Фото профиля Saai Arora
Saai Arora9 дней назад

Damnnn this is fire

Фото профиля Varik Verilion
Varik Verilion9 дней назад

Incident history inside the coding loop is a useful addition.

Фото профиля EKOS _ AGI 🦊 🇮🇷
EKOS _ AGI 🦊 🇮🇷8 дней назад

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
Yijie8 дней назад

production quality on this is crazy

Фото профиля cole murray
cole murray9 дней назад

awesome!

Фото профиля Samuel Hu
Samuel Hu9 дней назад

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
Dominik9 дней назад

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
AWE8 дней назад

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

Фото профиля Ali Mirza | AI Agents & Automation
Ali Mirza | AI Agents & Automation8 дней назад

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

Фото профиля Bessi
Bessi8 дней назад

past incidents in the MCP. did not expect that

Фото профиля virtualuncle
virtualuncle8 дней назад

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

Фото профиля Mike Lopez
Mike Lopez8 дней назад

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

Фото профиля Mohamed Khlifa
Mohamed Khlifa8 дней назад

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

Фото профиля 0xdotdot
0xdotdot8 дней назад

fire

Фото профиля Omair-Inam Abdul-Matin
Omair-Inam Abdul-Matin9 дней назад

How much will this cost?

Фото профиля Jag
Jag9 дней назад

Interesting. So all the code base replicates to greptile?

Фото профиля AI Mastery Guide
AI Mastery Guide8 дней назад

past incidents remembered, that's smart

Фото профиля TonkaToyXL | AI Test Cabin
TonkaToyXL | AI Test Cabin8 дней назад

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.

Похожие видео