Every turn starts with the model receiving context.
EONYX builds it from three parts.
AGENTS.md carries the project’s standing instructions.
Sessions hold the full history on disk.
Auto-summarization compacts the older turns as the window fills.

A skill is a folder with a SKILL.md inside.
It is an instruction the agent loads when the task calls for it.
Package a repetitive procedure once: a code review, a deploy checklist, a report format.
It then costs no context until it is actually needed.

EONYX is written in Go.
It builds into a single static binary.
Inside sits a small set of packages around one central abstraction.
Here is how it fits together.

An agent reads code, edits it and runs commands.
So it has to stay inside explicit permissions.
EONYX stacks several layers: a static gateway, a file sandbox, plan mode and a hard block on dangerous commands.

The main way to work with EONYX is the terminal interface.
Streaming answers, a command palette, pickers and dialogs.
Here is everything worth knowing to move fast.

A subagent is a separate instance of the agent.
EONYX hands it a slice of the work.
It runs in its own context window, with a reduced tool set, and returns only the result.
So the main conversation stays clean: the research never clutters it.