Skip to Main Content
Talk Intermediate MIT

Teaching Agents How to Think, Not What to Say

Proposal status is Rejected
Session Description

Today's AI agents are remarkably capable, yet surprisingly fragile. They can write code, search documentation, and call tools, but they often lack something every engineering team relies on: a consistent way of thinking, real understanding of the codebase, and built in safety.

In this talk, I will demonstrate an elevated approach to AI assisted software development where the agent does not just generate code, it reasons through engineering phases, understands the structural impact of its changes, and is prevented from leaking credentials before they ever leave your machine.

The workflow combines three open source components into a single development experience. A lifecycle framework gives the agent persistent memory and phase aware guidance so it stays focused across sessions without being told it is being guided. A code intelligence layer transforms the repository into a navigable call graph, giving the agent structural context through impact analysis, dependency maps, and call chains instead of brute force context windows. A credential scanner built as a native hook catches secrets before they reach the AI model, ensuring safety from the very first keystroke.

The result is a development workflow where the agent explores before it proposes, understands dependencies before it refactors, remembers what was rejected and why, and cannot accidentally expose sensitive data. Every component is local first, fully open source, and runs on open models without any cloud dependency.

The session will walk through a live engineering task using this workflow end to end: from exploring an unfamiliar codebase, through architecture and implementation, to validated, safe code changes. I will share the design trade offs, lessons learned, and the practical patterns that made agent assisted development actually productive.


Key Takeaways
  1. How structured lifecycle guidance makes AI agents productive across long engineering tasks instead of one shot code generation.
  2. Why code intelligence and structural context reduce hallucination to near zero compared to brute force context windows.
  3. How to protect credentials from reaching AI models using native hooks in your development workflow.
  4. A practical, local first, open source workflow for AI assisted development that attendees can adopt immediately.


References

Session Categories

Knowledge Commons (Open Hardware, Open Science, Open Data etc.)
Talk License: MIT

Which track are you applying for?

Main track

Speakers

Aniket Paluskar
Aniket Paluskar Software Engineer | Red Hat

Aniket Paluskar is a Software Engineer at Red Hat, working on open-source AI and MLOps platforms. He contributes to projects across Feature Stores, Kubeflow, and agentic AI systems, and is the creator of Nous and CodeGraph projects focused on collaborative AI agents and code intelligence. He also leads Kubeflow Commons Hub India, helping developers move from users to open-source contributors.