Missions

HexaEight has no prompts to write. In a chat you just talk to your agent and get the work done.

When a piece of work has to be done the same way every time — reviewing a request, checking a document against a policy, answering one kind of question for your customers — you do not write a long prompt and hope it is followed. You build a mission: you describe how the AI should go about the work, the agent turns that into a flowchart of capability cards, and from then on it follows that flowchart. The same kind of question takes the same path, every time.

	Chat	Mission
what you do	talk	describe the process once
what the agent does	works out each answer as it goes	follows the flowchart and its cards
good for	research, drafting, one-off questions	repeatable work — the same steps and the same checks, every time

What a mission is made of

• The flowchart — which card handles which kind of question.
• Capability cards — one for each kind of question: what to search, what to check, what to decide and what to answer with. The decisions are made on the cards.
• Its memories — the memories it may search, and only those.
• Its commands (optional) — the exact commands it may run, approved on your agent.

There is no code to write. You describe the process in plain words and correct it in the same conversation.

Build one

In the workspace, open Missions and choose Build a new mission:

1. Describe the process in plain words — what comes in, what to check, what to decide, what to answer.
2. Review the flowchart. The cards take shape beside the conversation. Change anything by saying so.
3. Ingest the mission. It becomes a mission your agent can run.

Run it and check it

Open Mission Runner, start a session, pick the mission from the list above the message box and ask it the questions it is meant to answer. Check the answers. If one is wrong, correct the card in Missions and ingest again — the next run follows the corrected card.

What keeps it on track

• Only its own memories. A mission searches only the memories it lists.
• Only approved commands. A mission runs a command only if that exact command was approved on your agent, pinned to the exact file it runs: change one byte of that file and it will not run until it is approved again.
• Its own folder. Each run works in a folder of its own, inside the agent’s sandbox.

Long jobs — HexaPilot

For a job that runs for a long time on its own, open HexaPilot: describe the job, review its flowchart, press Start, and watch it — or come back later. It plans, works and checks its own work, inside its own folder. You can ask how it is going, or stop it, at any time, and every command it runs goes through the same command gate, always enforced.

Move it, share it

hexaeight-activate mission-export --mission <name> --out <name>.zip
hexaeight-activate mission-import --in <name>.zip          # on the other agent

A bundle carries the flowchart, the cards, the mission’s own files and the memories it names — your own documents, and a pointer to each memory another agent serves. Very large memories are left out unless you add --include-large; --no-data leaves out your documents and keeps only the pointers.

A bundle never carries keys or secrets, policy rules, or permission to run a command. Those are set up again on the agent that imports it.

The two kinds

	Guided	Direct
a card says	steps: search this, read that, decide, answer	mode: direct, and one command
who decides	the agent’s model, following the flowchart and the card	nobody: every message goes to the command
the model	the harness’s model works through the card	the harness makes no model call; the command may call one
typical use	research, runbooks, compliance checks	a framework that does the work itself
cards	as many as the work needs	exactly one

A direct card:

## card: ask-runner
id:            ask-runner
mode:          direct
direct_input:  question.txt
direct_run:    "python3 runner.py --question-file question.txt"
resources:
  files:       [runner.py]
  commands:    ["python3 runner.py --question-file question.txt"]

The harness writes the message to question.txt, so the message never reaches a shell. It runs the one command through the command gate and returns what it printed, unchanged.

Frameworks as missions

An agent framework you already use — CrewAI, LangGraph, Pydantic AI or Agno — can run as a mission:

hexaeight-activate enable crewai

This installs the framework’s mission and has your agent approve the one command it runs. The framework does the work; identity, memories, policy and approvals come from HexaEight. See Frameworks.

Let other software use it

A mission can be offered to other software through a runner: an agent sealed to that one mission. Callers choose the question, never the mission. See Other software calling it.

Next

• A procedure it follows — the flowchart and the cards, field by field
• Memories — what a mission searches