Comment

Comment by y14

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

parent y14 1 year ago

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton