October 15, 2026

From a clean repo to a working agent CLI

Four folders, two files at the root — cli/, config/, gateway/ and tools/ together give you a CLI that can load its config, call tools and run agents.

Zetelton-AgentArchitectureCLI

Zetelton-Agent is where the runtime lives. Four folders, two files at the root. Each part of the codebase has one job — and together they give you a CLI that can load its config, call tools and run agents.

What's inside

  • cli/ — entrypoint and commands
  • config/ — settings, per project
  • gateway/ — model and runtime bridge
  • tools/ — anything the agent can call

__init__.py and main.py sit at the root — a minimal codebase you can read in an afternoon.

One command later

Run uv run zetelton-agent and the agent starts: it reads the config, connects through the gateway and calls tools from the tools folder.

$ uv run zetelton-agent
› config loaded
› tool → search
✔ done

Because every layer is independent, you can swap the gateway, extend a tool or reshape the config without touching the rest of the codebase.