Skip to content

Introduction

Atlante is the configuration and build layer for a coding-agent harness. It keeps agents and skills in a structured, versioned source and tests the resulting harness through repeatable scenarios. A coding agent’s results depend on more than the selected model. The context supplied to the model shapes how it interprets tasks, follows project rules, and checks its work. Whether written by a person or generated by an agent, that context deserves the same care as code. It should be clear, easy to review, and tested against the work it is meant to guide. Reading the instructions explains their intent, but their effect becomes clear only when an agent uses them. Even a small change to that context can alter how the agent writes code.

Atlante keeps configuration, builds, and evaluation together in the repository. The host adapters materialize reusable context as native files for OpenCode and Claude Code, while evaluation checks the resulting harness against explicit expectations.

A project’s atlante.jsonc brings together the configuration and resources that define its agents and skills. It can extend a preset, compose content through templates, and supply project-specific values. Together, the configuration and selected resources are the source of the harness, which can evolve alongside the code it guides. Atlante validates that source before writing any files, then a successful build produces reproducible native output for the selected hosts. Each host discovers the generated agents and skills when it starts, and atlante eval uses them to run defined scenarios in disposable sandboxes.

From source to use and evaluation
Source Configuration and resources
Build Validate and materialize
Native output Generated agents and skills
Use / evaluate Host / atlante eval

Atlante prepares this structure but does not run it: model calls, permissions, tools, modes, and project execution remain with the host and configured model. Workflows describe a process for the model to follow, but Atlante does not schedule them, track their progress, or manage runtime checkpoints. Packs published as npm packages are listed in the pack explorer, a curated directory for inspecting a pack before installing it.

Follow Getting started to create your first configuration.