The IDE Should Become an Operating System for AI
10 hours ago
- #Artificial Intelligence
- #Integrated Development Environment
- #Software Development
- Modern IDEs have limitations for AI work due to their file and panel-based organization, lacking flexibility for integrating diverse components like terminals, logs, and agents.
- Historical systems like Smalltalk, Lisp machines, and Emacs provided more flexible, inspectable environments by treating the running system as an addressable object space or using buffers as a universal substrate.
- For AI to thrive, every element—such as file lines, terminal byte ranges, diffs, or network requests—should have an identity, making them addressable, inspectable, searchable, and replayable.
- Buffers should be redefined as durable work items with types, URIs, and capabilities, applicable not just to text but also to terminals, tests, browser replays, and agent runs, with consistent commands across them.
- The future IDE needs to evolve into an AI operating system, featuring a scheduler, memory, object model, permissions, event logs, and a command language that serves both humans and agents, ensuring safety and coherence without hidden UI powers.
- This shift transforms the IDE from a code-typing tool into a runtime for software work, making Git, browsers, terminals, and deployments coherent objects in a unified space navigable by users and AI.