GraphQLConf 2026

How do you expose all the internal tools to the Agents is the question everyone is asking today. Turns out we already expose all the things people can do with our internal tools at Meta through GraphQL and LLM Agents are now able to write GraphQL queries, so... come to this talk to see how both work wonderfully together!

After eleven years as an open source technology, GraphQL has never had a more favorable learning curve. Clearer mental models, better educational materials, and a deeper collective understanding of best practices have transformed the “wild west” of 2015 to a much more manageable landscape today.

You and your team are unique, so rather than a one-size-fits-all blueprint I thought I’d present a practical guide to teaching yourself GraphQL in 2026. We’ll examine how beginners typically build their first mental model of GraphQL, the most common misconceptions, and the key design questions they encounter early. Special attention will be paid to different modalities: schema-first vs. code-first, schema design principles, common pitfalls when considering enums, the proper use of fragments, and security and performance by default.

Attendees will leave with a conceptual roadmap for self-study, a recipe book for context engineering in their agent, and an understanding of the major decision points along the journey ahead.

Deprecating fields and removing them in GraphQL is tricky itself, but tooling can help identifying such based on statically analysing operations or traffic. But, deprecating inputs is a whole different challenge! Once clients start sending arguments or input object fields, removing or changing them can break integrations in subtle ways, as you do not know which fields might be used in the future and which ones might not, especially if you are running GraphQL at scale. In this lightning talk we will explore possible options for making this whole process more safe in the present, and dip into how it could look in the future!