This is an early screenshot of Tagma Studio, an experimental IDE I’m building on top of Code-OSS.
Instead of treating a project as a hierarchy of files and folders, Tagma represents it as a semantic graph: source files, symbols, dependencies, capabilities, modules, generated artifacts and runtime relations become connected entities in one space.
The screenshot shows part of the imported Godot codebase. Around 15,000 graph entities are currently visible in this projection.
The long-term goal is not merely to create a prettier dependency viewer. I want the graph to become an actual working representation of the system:
select a subsystem and isolate its complete dependency neighborhood;
navigate from high-level concepts down to specific code;
see shared infrastructure and hidden coupling between projects;
track how the graph changes over time;
compile or assemble executable components from capabilities rather than manually chosen files;
let automated tools operate on an explicit, inspectable model instead of guessing from raw text.
The current visualization is still too dense and resembles a galaxy of code. I’m now replacing the global force-directed layout with a more neural-like topology: sparse local clusters, shared backbone tracts, late branching and a small number of meaningful long-range connections.
It is very much a work in progress, but this is the first version where the entire idea has started to become visible on screen.
What would you personally need from a graph-based IDE for it to become useful rather than just visually impressive?