All activity
Archaic analyzes your codebase with AI and generates an interactive architecture map: services, connections, execution flows, and deep dives. But it's not just for you. Your AI agent can read it, reason about it, and update it as it works. The desktop app is local-first with your own LLM keys (Claude, GPT-4, Gemini, Ollama). An MCP server connects to Claude Code so your agent always knows how the system is structured. Create a task in Desktop, Claude implements it, and the diagram updates live.
Archaic AIA living architecture map — for you and your AI agent
Archaic AIstarted a discussion
How do you keep track of what your AI agent actually built?
We've been vibe coding more than ever — Cursor, Claude Code, Copilot agents spinning up entire features. But I keep running into the same issue: after a few sessions, I have no idea how the pieces actually fit together. The code works, but I couldn't draw the architecture on a whiteboard if someone asked me to. Curious how others deal with this. Do you just read through the code? Maintain docs...
Archaic AIleft a comment
Hey PH! I built Archaic because vibe coding has a problem: the more your AI agent builds, the less you understand what it actually built. You can read the code, but you lose the big picture — what connects to what, how data flows, and where the boundaries are. And when you try to explain the architecture to your agent in plain text, things get lost. It's hard to describe a system precisely...
Archaic AIA living architecture map — for you and your AI agent