Skip to content
archeus
GitHub
FeaturesDownloadArchitectureChangelogBlogFAQCommunityAboutDocumentation

Architecture

Architecture

archeus is one engine with two front ends. Everything below runs locally, on the standard library, against files Claude Code already writes.

Read the sourceArchitecture docs

  1. The architecture graph

    Every module and its dependencies, expandable down to single files — across Python, C, C++, C# and JavaScript or TypeScript.

    The connections engine parses your source, resolves imports into real cross-module edges and ranks each node by importance. The result is written as a single self-contained HTML file inside the project and opened from the session browser. Nothing is uploaded, and nothing is served.

    The same graph is what the memory layer merges its summaries into, which is why the memory of a module knows what that module depends on.

    The archeus architecture graph expanding from repository level down to individual files, with dependency edges between modules.
    The graph archeus draws of a real repository — one self-contained HTML file, written into the project and opened locally.

  2. The layers

    Store and transcripts
    One reader per file format, and the reader streams. Transcripts reach a hundred megabytes, so they are iterated rather than read, with an optional substring prefilter tested against the raw line so a caller that wants only the tool calls never pays for a parse it discards.
    Memory
    A semantic graph in the project, consolidated under an importance cap, with superseded facts invalidated rather than deleted. An absent file is an empty state; a file that exists and will not parse is a fault, moved aside and reported rather than silently returned as empty.
    Jobs
    Long Claude calls run inline as a banner that survives navigation, and escalate to a modal only when the job actually parks at an approval gate — decided by what the job did, not by a per-kind allowlist that would go stale.
    The local HTTP API
    The GUI is a single-page app over a loopback server. A custom request header is not an auth boundary and neither is loopback, so the guard is a Host allowlist, a rejection of browser fetch metadata, and a per-run secret compared in constant time.
    Claude Code’s own state
    settings.json and the plugin caches are read-modify-written atomically, never rewritten. archeus shares those files with Claude Code, so a half-written one breaks your session, not just this tool.

  3. Principles the code is held to

    • Zero runtime dependencies. Everything is the Python standard library, so there is nothing to resolve, pin or break.
    • Read Claude Code’s state, never build on its naming. Where the documentation and the disk disagree, the disk wins and the unknown is reported as unknown rather than guessed.
    • Read-only where it matters. The checkpoint store is never written; restoring stays Claude Code’s job.
    • A verification tool that runs nothing reports success, so every gate has a floor on how much it did and every one has been mutation-verified against the bug it exists to catch.
    • The interface animates transform and opacity only. Anything that forces a GPU readback tears the compositor.