Glamorous Toolkit

Glamorous Toolkit | Glamorous Toolkit is the moldable development environment.

Next GT Meetup: April 20, 2026, 16:00 CET

-->

The moldable development environment for<br>making sense of systems and AI

Code reading is the bottleneck. Systems are too large, and AI generates code too fast.<br>Glamorous Toolkit replaces reading with deterministic contextual tools that compress the system around each problem, helping humans and AI explore faster.<br>Build these tools yourself or with AI in one integrated environment.

Get started

Learn the basics<br>Choose a problem and start solving it

Download

Free and open-source<br>Mac, Linux & Windows

Star us on GitHub. Chat on Discord.

Any question about an existing system can be answered through narratives made out of contextual tools.examples

API exploration

Dedicated AI chats

Software analysis

Data exploration

Technical documentation

DevOps investigations

System specific editors and views

System specific editors

-->

Inspecting runtime

Domain documentation

Rewriting code

See it live

45 minute introduction video

-->

Drive with the built-in moldable agent harness

Work with AI agents without delegating your comprehension to them. Remain in charge by controlling your harness.<br>-->

Programmable agents

Setup conversations through scripts that define context, tools or structured outputs.

Expandable agent memory

Define context through executable explanations linked to code and examples. Leverage contextual views to expand the agent's memory to arbitrary objects.

Explainable agent actions

Don't take for granted what the AI says it does. Understand it deterministically through contextual views.

Objects, not text

Pass live objects into the conversation and get structured objects back, each with contextual views that make them explorable for both humans and AI.

Work with OpenAI, Anthropic, Ollama or build your own provider.

Get started to see it in practice

Choosing the role of human decision making is the most important architectural decision of our time. Understanding the nature of software and what it takes to comprehend it are paramount before making that choice

-->

Software is shapeless. You cannot perceive anything in a software system except through a tool. Tools are essential as they provide the shape of software. Control the tool to control the perception, and therefore your comprehension.

Software is highly contextual. For tools to be effective, they must be contextual, too.

There is no single representation of anything in a software system. Even the textual shape of code is just the incidental form of the medium in which you type. There are always many representations, each relevant for different problems.

To accommodate many unforeseen contextual tools, the environment is designed as a language made out of interactive and visual operators with which you can program and combine micro tools inexpensively, live and in many ways.

A tool is an interface through which you interact with a computation. It can be a configuration editor, a debugger over the runtime, or an inspector of an API. A tool can be elaborate, doing many things, or it can be simple, focusing on answering a single question. A tool can be visual, or it can be plain. A tool can be generic, applicable to many inputs, or it can be contextual, relevant to only a narrow input.

Authorship history

Dependencies editor

Treemap distribution

Class hierarchy

Abstract syntax tree

Generic tools are applicable widely at the cost of making everything look the same. But in software systems, value is always specific. Contextual tools can communicate that value much more efficiently and pleasantly.

Contextual views

Generic views

Understanding systems boils down to answering questions about them. The answers can be found in the system's artifacts, but those artifacts are too large to be read. Tools can encode the way to get the answer deterministically. The result produced by the tool essentially acts as a compression of the system for that question. The more specific the tool, the more relevant and larger the compression is. The larger the compression, the easier it is to understand.

Contextual views compress the system

Answering every question through deterministic contextual tools leads to thousands of tools per system. To manage them, you need an inversion of control: tools should come to where you are, instead of you invoking them explicitly. In Glamorous Toolkit, tools are associated to the contexts in which they are relevant and they activate only when you interact with that context. Such a context can be as basic as an individual object.

Multiple views for the same context

A typical moldable development flow

Start with a specific question. If there is no relevant tool, build one. Interpret the answer and make a decision. Repeat.

Get started to see it in practice

A view associated to an object offers a unit of documentation. When the objects are produced and...