--- title: "Graphlin - Jev-Enabled Live Architecture Visualizer" type: post url: "https://robotpaper.ai/graphlin-jev-enabled-live-architecture-visualizer/" canonical: "https://robotpaper.ai/graphlin-jev-enabled-live-architecture-visualizer/" markdown_url: "https://robotpaper.ai/graphlin-jev-enabled-live-architecture-visualizer.md" published: "2026-09-22T15:24:56.000+00:00" updated: "2026-10-22T21:57:58.000+00:00" tags: ["Tools"] author: "Roy Osherove" author_links: ["https://robotpaper.ai", "https://x.com/royosherove", "https://www.linkedin.com/in/osherove/", "https://forms.gle/jQSx5KoXvrVA1JCK7", "https://robotpaper.ai/about-roy.md"] description: "Graphlin is my open-source Claude Code/Codex plugin that draws a live diagram of the architecture your agent is building, using Jev to classify each action." usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original post)." license: "https://creativecommons.org/licenses/by/4.0/" --- # Graphlin - Jev-Enabled Live Architecture Visualizer Introducing [Graphlin](https://github.com/royosherove/graphlin) - a plugin for Claude Code/Codex that auto visualises your architecture as your agent is building it, and what the agent is currently working on. [Graphlin Plugin for Claude/Codex: Live, on-the-fly Architecture Diagrams](https://www.youtube.com/embed/ynZLe9p7PxM?feature=oembed) Why? I, like many others, tried [Jev](https://typesafe.ai/blog/introducing-system-one-models-and-jev) over the weekend. Unlike others, I did NOT build a router. I built a live diagram of the architecture being built by my agent - not perfect but it might be the beginning of something. It's open source and you can plug your own visualization to it. The source is fully open at [https://github.com/royosherove/graphlin](https://github.com/royosherove/graphlin) ## How does it work? ![Graphlin sequence diagram: agent hooks send actions through a local parser to Jev for classification, then update the live architecture viewer](https://robotpaper.ai/content/images/2026/09/image-1.png) After various hooks in the agent such as pre tool use, file edit, create etc, actions are being sent for classification by Jev (multiple layers), and the results are used for both generating state, and visualizing it by a local server. Jev is used as a runtime decider on what actions are being taken, what are the various types of components/files, what icons to use, who depends on who and more. The idea of a general classifier is pretty strong and opens up a bunch of use cases. Classifiers are not new, but the packaging, lack of need to pre-train, and ease of use out of the box are pretty useful. Like OpenClaw that gave birth to many a grok-bot, instinct, kiroCrew and others, I believe this will just be the first one to open the door to imagining a general classifier future. a system one classifier is a useful tool in the toolbelt. Other projects claim to have been first: [Laya](https://huggingface.co/convaiinnovations/laya), for example. I have not tried it yet so cannot share my opinion. However, graphlin is pluggable, you could technically ask your agent to replace the decision service with laya and see what happens. --- ## About the author **Roy Osherove** - Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: [https://x.com/royosherove](https://x.com/royosherove) - LinkedIn: [https://www.linkedin.com/in/osherove/](https://www.linkedin.com/in/osherove/) ### Contact - Contact form: [https://forms.gle/jQSx5KoXvrVA1JCK7](https://forms.gle/jQSx5KoXvrVA1JCK7) ### License Content on robotpaper.ai is licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/): reuse, quote and adapt with attribution (Roy Osherove, link to the original post). More about Roy and his other sites and projects: [https://robotpaper.ai/about-roy.md](https://robotpaper.ai/about-roy.md)