Hacker Newsnew | past | comments | ask | show | jobs | submit | ddmdd's commentslogin

AI is finally leveling the playing field on all those long and confusing documents that were designed to make regular people give up and pay whatever


how do you make sure there's no context bloat?


Thanks for the question. Avoiding context bloat and overall engineering the context is (still) most of work. What’s been working:

- Role scoped calls: data modeling, code gen, are separate calls where each gets its own tailored context

- Context is divided into sections (tables, dbt, instructions, code) and each is getting a hard limit budget (required some experimentation, liked Cursor’s priompt project)

- agentic retrieval: agents can call tools to fetch or search data/metadata when needed

- summaries for different objects: messages, widgets; reports, data samples/profiles.

I wrote some more about how the agent and context work in the docs


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: