The workspace

The workspace is how you use your agent: a web page served from your own machine, which talks to the agent over the same end-to-end encrypted channel as everything else. It holds no identity and no model keys of its own, and closing it stops nothing that is running.

The examples on this page use a small sample handbook for a fictional company, Example Co, so you can follow along with documents of your own.

Sign in

Open the address the installer printed. Enter your email, choose Scan with HexaEight Authenticator, scan the QR code with the app, and type the access code it shows.

Scan the code with the Authenticator, then type the code the app shows.

The first time, you accept the workspace’s terms. On a business licence the privacy notice is part of them. Each acceptance is kept with the exact words, so you are asked again only when they change.

After a while without activity the workspace signs you out: 15 minutes by default on a business licence, 8 hours on a personal one. See Admin settings.

Home

The bar on the left holds one place for each job. Home shows them as tiles, with how many conversations each has.

Chat	ask, research and draft with the agent
Coding	work on one codebase: the agent searches the code, changes it and checks its own work
Missions	turn a process into a mission: describe it, review the flowchart, ingest it
Mission Runner	run a mission and check its answers
Memory	the documents and services the agent can search
Machines	servers the agent works on, with every command approved by you
HexaPilot	long jobs the agent runs on its own
Messages	messages to and from other people, delivered end to end to their agent
Keys	API keys the agent’s work may use

Give it documents: Memory

A memory is a named collection of documents the agent can search. Create one in Memory with a name and a one-line description. The description is how the agent decides when to search it, so say what is inside.

Then add documents: Upload them from your computer, or Add Files From Agent to pick files or a whole folder on the agent’s machine.

Pick a folder on the agent's machine and stage it.

Press Save & embed. The documents are indexed on the agent’s machine, on its CPU, and the memory shows what it holds:

See Memories for documents another agent serves, APIs, and very large collections.

Ask: Chat

Open Chat, choose New chat and ask in plain words. You don’t have to tell it where to look: the agent reads the descriptions of your memories and picks the one that fits. It may check with you before it searches.

Switch the view to Advanced to see how it got there. The thought process lists every step. Here it is one memory_search, with the passages it found and the document and section each came from, then the answer:

Default shows the answers; Advanced also shows the thinking and every step.

Under the message box:

• Attach gives the conversation files, uploaded or picked from the agent’s machine.
• The memory chip attaches one memory that the conversation consults on every turn. You rarely need it, because the agent can search any memory by name.
• The line underneath reminds everyone that they are working with an AI system.

Export a conversation with .md or PDF at the top. The export is labelled as AI-generated.

Make it repeatable: Missions

When a piece of work must be done the same way every time, build a mission. Open Missions and choose Build a new mission. Missions lists the conversations that build missions; the missions you have recorded are listed in Mission Runner.

Describe the process in plain words. For the sample handbook:

Build a mission that answers employees’ questions about Example Co’s policies, using the sample-handbook memory. For each question: decide whether it is about leave or about travel and expenses; search the sample-handbook memory; answer with the exact number or limit and name the document it came from. If the handbook does not cover the question, say so and point the person to the People team or Finance. Never guess a number.

The mission engine reads the memory first, then draws the process as a flowchart of capability cards and asks you to confirm it:

The flowchart the mission engine drew from that description.

In the workspace the flowchart sits beside the conversation. Change it by saying so, or type a change into Ask for a change to this picture:

Confirm the design and it writes the cards. Then give it a sample question to prove them: it walks the cards step by step and checks the answer against the memory.

When you are happy, press Ingest Mission and give the mission a name: the name is the memory the mission is written to. Before anything is written, it checks that every card’s dependencies are present and every reference is valid:

Press Ingest Mission in the dialog, and the flowchart and the cards are written:

The mission is now a memory of its own, here Handbook_Answers. See Missions.

Run it: Mission Runner

Open Mission Runner. Your recorded missions are listed on the left, the ones run most recently first, each with its runs beneath it. Pick one to see its cards and flowchart:

A mission's page: its cards, and what you can do with it.

Choose Run mission, or choose New Mission Runner session and pick the mission with Choose mission above the message box. Ask the kind of question your people will ask. The Advanced view lists every step the mission took, starting with its searches:

The answer says which card it used and what it found in the document, and ends with an answer card that names its source:

If an answer is wrong, choose Edit / duplicate on the mission’s page, change it in Missions and ingest it again.

To remove a mission you no longer need, choose Delete on its page, or select at the top of the list to delete several at once. The documents it searches are not touched, and its runs stay, listed last as orphaned.

Work on your servers: Machines

Machines lists the servers the agent can work on. The installer adds the computer the agent runs on (here it is called local). Add others with their address, the user to sign in as, and a password or key. The agent signs in first and seals the details only if that works. Nothing can read them back.

Choose Chat on a machine to open a conversation bound to it. It starts by surveying the machine, read only, and answers questions about it:

Every command waits for you. When the agent needs to run something, it appears on the right with Approve and Deny:

Approve it, and the command runs. Its output appears in the terminal on the right, and the agent explains it:

Long jobs: HexaPilot

For a job that runs for a long time on its own, open HexaPilot and choose New pilot. Jobs that need you are listed first.

Describe the job. The agent drafts it as a flowchart with numbered steps, and nothing runs until you press Start:

After Start it plans, works and checks its own work inside its own folder. Ask how it is going at any time, Pause or Stop it, and answer it when it needs you. A job can also run on a schedule: then the button is Approve schedule.

Keys

Keys holds API keys that the agent’s work may use, such as a key for a search or weather service. Values are sent encrypted, sealed on the agent and never shown again.

Privacy

On a business licence, Privacy at the bottom of the workspace shows your consent record and the privacy notice, and lets you withdraw your consent. After you withdraw, the workspace shows only the terms until you accept them again. See Admin settings.