Hex.Frontier User Manual

User manual

Hex.Frontier

Frontier is an AI work partner that can explain, plan, use approved product tools, and keep you informed while it works. This manual is written for everyday users, including metrology teams.

01 · Welcome

What Frontier is

Think of Frontier as a careful coordinator. You describe an outcome in normal language. Frontier decides which instructions and connected product tools are relevant, performs the work step by step, checks the result, and reports back.

Conversation

You set the goal

Ask a question, request a report, describe a measurement task, or ask Frontier to diagnose a problem.

Agent work

Frontier handles the steps

It can read context, load a skill, use a connected service, and verify what happened.

Your control

You approve important choices

Measurement scope, online machine use, physical motion, and uncertain drawing results stay under your control.

The simplest way to use Frontier: say what you want, include the relevant file path or product name, and state any limits. You do not need to name a skill or MCP server.

Four parts you may hear about

Agent loop

The repeating cycle of understanding, acting, checking, and continuing until the task is complete or a decision is needed.

Skills

Task-specific playbooks. They tell Frontier the safe and reliable way to handle work such as PC-DMIS automation or CAD-to-program generation.

MCP servers

Product bridges. They let Frontier use approved functions in PC-DMIS, Metrology AI, and Orca without asking you to operate every screen manually.

Container / Arena

The desktop workspace that shows Frontier beside native applications. Arena makes the application being used visible; it does not own or terminate the application.

02 · First 5 minutes

Start, check, ask

  1. Open Frontier.Use the Frontier desktop shortcut. If Container is installed, Frontier opens inside it; otherwise it opens in your browser.
  2. Sign in if asked.Gateway installations show an organization sign-in page. Local-model installations usually go straight to the workspace.
  3. Wait for the green Connected status.If it says Reconnecting, give the service a moment before sending your first request.
  4. Type a request in normal language.Press Enter to send. Use Shift + Enter for a new line.
  5. Watch the progress card.Frontier shows the current activity. Open Details only when you want a closer look.
  6. Answer any choice card.Select the required options and press Submit. Work that needs your decision pauses safely.

A good first request

Please check the current Frontier connection and available product tools. Explain what is ready in plain language. Do not make any changes.

If a task appears to stop: read the latest message first. Frontier may be waiting for a file path, a measurement-scope choice, or permission for a safety-sensitive action.

03 · Screen tour

Know where to look

The main workspace stays deliberately simple: conversations on the left, work in the center, and controls close to the message box.

Hex.Frontier Connected
A

Header

Connection status, updates, optional Tool Log, light/dark mode, and sign out.

B

History

Open earlier conversations. Right-click one to rename, export, or delete it.

C

Conversation

Your messages, Frontier’s answer, progress cards, choice cards, reports, and delivered files.

D

Message box

Write the request here. The arrow sends; the square Stop button cancels the current run.

E

Toolbar

Agent, Heartbeat, Hooks, New, History, and token/cost information. Most users can leave Agent on Frontier.

Progress versus answer: a progress card tells you what Frontier is doing. The final message underneath is the result. Use Details to inspect individual tool steps when troubleshooting.

04 · How Frontier works

The agent loop, in plain language

Frontier does not send one guess and stop. It can repeat a controlled cycle until it has evidence that the task is done.

1

Understand

Reads your goal, limits, and conversation context.

2

Prepare

Chooses the right skill and plans the next safe step.

3

Act

Uses a product bridge or another approved tool.

4

Check

Reads the result and verifies that the expected change occurred.

5

Continue or ask

Proceeds, reports completion, or pauses for your decision.

What you may see during a run

“Checking measurement capabilities”

Frontier is reading what the connected product can safely do and which information it needs.

“Using a connected service”

A product bridge is reading or changing an application on Frontier’s behalf.

A choice card

The task reached a decision that Frontier should not make for you. Select an option and submit it.

A delivered file

The result contains an attachment. Click its name to open or download it.

Cancelled or timed out does not always mean “nothing happened.” A product may have completed part of an action before communication stopped. Ask Frontier to inspect the current state before repeating the action—especially around PC-DMIS or machine motion.

05 · Ask clearly

Give Frontier the information a colleague would need

A useful request usually contains four things: the goal, the source, important choices, and the stopping point.

1 · Goal

What result do you want?

“Summarize the latest report” or “create a measurement program.”

2 · Source

Where is the information?

Give the product name and a full local file path when a CAD model, drawing, or report is involved.

3 · Choices

What rules matter?

State units, offline/online mode, features, datums, tolerances, probe constraints, or output format.

4 · Stop point

What must not happen yet?

For example: “prepare only,” “do not execute,” or “ask before moving hardware.”

Reusable request pattern

I want [outcome]. Use [product or full file path]. Important requirements: [units / scope / datum / output]. First [inspect / explain / prepare]. Do not [execute / move hardware / overwrite] until I confirm.

Small details that make a big difference

  • Use a full Windows path, for example D:\Inspection\Housing\housing.step.
  • Say whether units are millimetres or inches.
  • Name the part, routine, feature IDs, or drawing revision when known.
  • Say whether you want an explanation, a preview, a change, or execution.
  • If Frontier’s interpretation is wrong, correct it directly: “Use datum A-B-C, not A-C-B.”
  • Never paste passwords, access tokens, API keys, or other credentials into the conversation.

06 · Metrology playbook

Common metrology jobs

Frontier coordinates PC-DMIS, Metrology AI, and Orca. You keep control of measurement scope and every action that can move hardware.

CAD → PC-DMIS measurement program

Use when: you have a 3D CAD model and want a measurement program.

  • Paste the full path to the .cad, .igs/.iges, or .step file.
  • Frontier prepares PC-DMIS in offline mode by default and opens the model in Metrology AI.
  • Detected features and GD&T are presented as choices—not automatically treated as the measurement scope.
  • You confirm exactly what to measure. Frontier then prepares probes, generates the program, and checks required tip commands.
  • A .step model stays on the Metrology AI path where PC-DMIS CAD import is not used.
PC-DMIS routine work

Use when: you need routine setup, probes/tips, CAD graphics, features, dimensions, collision checks, or reports.

  • Frontier can attach to or start PC-DMIS, with offline mode as the default.
  • It can create and inspect routine content, set measurement context, simulate collision, and generate local reports.
  • Program execution, calibration, online machine use, and other motion require explicit confirmation.
Drawing / PDF → PMI extraction

Use when: dimensions, datums, or GD&T must be read from a drawing, PDF, or scan.

  • Orca detects and reads drawing items, with confidence and image location.
  • OCR is a suggestion, not a fact. You review uncertain values before they are used.
  • You confirm which drawing requirement belongs to which 3D model feature.
  • A drawing without a 3D model can be analysed, but it cannot by itself produce a CMM measurement program.
Reports and Data Page

Use when: you need a local report, failed-characteristic summary, or Data Page synchronization.

  • Reading an existing report does not require machine motion.
  • Generating a local report and synchronizing Data Page are different tasks.
  • Data Page synchronization executes the routine and can move hardware, so Frontier must warn you and receive confirmation first.

Example: safe CAD-to-program request

Create a PC-DMIS measurement program from D:\Inspection\Housing\housing.step. Use millimetres and offline mode. First list the detected features and GD&T and ask me to choose the measurement scope. Do not execute the routine or move hardware.

Example: inspect a report without running anything

Show the latest PC-DMIS measurement report and summarize failed characteristics, including nominal, measured value, tolerance, and deviation. Do not execute the routine.

Operator responsibility remains essential. Before physical execution, verify the correct machine, part setup, alignment, units, coordinate system, probe qualification, tip availability, clearance planes, and safe motion path according to your site procedure.

07 · Container & Arena

Keep Frontier and native apps in one workspace

HEX. Frontier Container is the optional desktop shell. Frontier remains your assistant, while Arena shows running applications such as PC-DMIS, Metrology AI, Data Page, or Log Viewer.

Important: Arena watches and displays applications. Selecting an Arena tab does not start, install, close, or terminate that application. When a supported application starts, Arena reconnects automatically.
Full workspace

One coordinated window

Show Frontier and Arena together. Move Arena to either side and drag the divider to adjust width.

Floating mode

Compact panels plus assistant orb

Move and resize Frontier and Arena independently, pin them above other apps, magnetically dock them, or collapse to the orb.

Arena layouts

Agent, Split, Grid, or Chat

Agent shows one app; Split shows two; Grid shows up to four; Chat includes a Frontier region below the active app.

Agent switching

Visible work without stealing control

Frontier may request the relevant already-running app. Container can defer if you are active elsewhere or chose a multi-app layout.

Container shortcuts

Show or hide ArenaCtrl + Shift + A
Return to full workspaceCtrl + Shift + F
Dock Frontier on Arena’s leftCtrl + Shift + ←
Dock Frontier on Arena’s rightCtrl + Shift + →

Container remembers your layout, visibility, width, docking, pin state, and window positions between launches. The assistant orb can restore the previous panel combination; right-click it for additional workspace actions.

08 · Skills & connected products

Skills tell Frontier how; product bridges let it act

Most users never need to select these manually. Frontier matches your request to a skill, then uses the appropriate connected product service.

Skill + bridge
Metrology AI

For 3D CAD, features, PMI/GD&T, probe synchronization, and generating a PC-DMIS measurement program from your confirmed scope.

CADFeaturesGD&TProgram generation
Skill + bridge
PC-DMIS

For routines, probes and tips, CAD graphics, measurement context, native features/dimensions, collision simulation, reports, and Data Page workflows.

RoutineProbeCollisionReportsData Page
Skill + bridge
Orca

For detecting and reading PMI from 2D drawings, PDFs, or scans. It can compare and transform drawing information, but it does not generate a measurement program.

Drawing OCRPMI detectionTemplate match
Workspace skill
Container workspace

Keeps the native application Frontier is using visible in Arena. It switches presentation only and does not manage application processes.

VisibilityArena stateApp switching

Useful status checks

Type thisWhat it showsWhen to use it
/skillsAvailable skillsWhen you want to confirm that a task playbook is installed.
/mcpConfigured product bridges and their stateWhen PC-DMIS, Metrology AI, or Orca tools seem unavailable.
/statusCurrent session, model, and token estimateFor a quick workspace status summary.
/helpAll available slash commandsWhenever you forget a command.

Bundled skills and the predefined Metrology AI, PC-DMIS, and Orca connections are restored by Frontier at startup in a standard managed installation. A restart is often enough after an administrator updates them.

09 · Safety

Pause at the boundary between digital work and physical motion

Frontier can prepare complex work, but the operator remains responsible for machine safety, part protection, and measurement validity.

Safe default

Offline unless you explicitly approve online use

PC-DMIS startup and routine creation use offline mode by default. Frontier should not attach to an online machine without confirmation.

Scope control

You choose what will be measured

Detected features, GD&T, datums, and OCR results are menus for review. They are not automatic instructions to measure everything.

Motion control

Execution and calibration need approval

Routine execution, Data Page synchronization, probe calibration, homing, and other machine motion require an explicit go-ahead.

Uncertain state

Inspect before retrying

After a timeout, cancellation, or interrupted connection, verify the routine, probe, and application state before running the same action again.

Before approving physical execution

  • Confirm the correct CMM, routine, part, fixture, and measurement mode.
  • Check units, alignment, coordinate system, datum order, workplane, and clearance values.
  • Verify the active probe, qualified tips, extensions, stylus geometry, and calibration status.
  • Review the selected features and tolerances against the current drawing revision.
  • Run and review collision simulation where available; follow your organization’s independent safety checks.
  • Keep the machine within reach of the normal operator stop controls and supervise initial motion.
Do not approve a vague motion request. If the choice card does not identify the routine, machine, or action clearly enough, ask Frontier to explain the planned motion before you continue.

10 · History & files

Keep useful work easy to find

New

Start a separate conversation

Use New for a different part, project, or topic. A focused conversation reduces accidental carry-over.

History

Return to an earlier conversation

Open the sidebar with History. Conversations are sorted with the most recently used first.

Right-click

Rename, export, or delete

Give important sessions useful names such as “Housing A – Rev C – offline program.” Export creates a JSON copy.

Files

Open delivered results

When Frontier delivers a report or artifact, click the file name. Images may also show an inline preview.

“Conversation history not saved” warning: copy or export important results immediately, then restart Frontier or contact support. A normal-looking conversation may be lost if the warning is ignored.

Good conversation hygiene for metrology

  • Use one conversation per part/revision or clearly announce when the part changes.
  • Include the drawing revision and CAD path in the first message.
  • Rename the conversation after the task is understood.
  • Ask for a final summary of scope, assumptions, files created, and actions not executed.

11 · Shortcuts & commands

Faster ways around Frontier

Conversation controls

Send messageEnter
New lineShift + Enter
Show command menu/
Cancel current runStop button ■

Helpful slash commands

CommandPurpose
/helpShow command help.
/statusShow session, model, and token estimate.
/compactCondense a long conversation while keeping useful context.
/clearClear the current conversation.
/costShow token usage and estimated cost.
/skillsList or invoke skills.
/mcpShow product-bridge status.
/agentsList configured agents.
/pluginsList installed plugins.
/versionShow Frontier version.
/exportExport the conversation to JSON.

Optional tools below the message box

Agent

Select a different configured agent. Leave this on Frontier unless your organization gives you a specific alternative.

Heartbeat

Manage repeated checks or monitoring tasks. Make the interval and stop condition clear.

Hooks

Manage event-triggered automation. This is normally configured by an advanced user or administrator.

12 · Troubleshooting

Start with the message you can see

Most problems fall into connection, product availability, missing input, or safety confirmation. The questions below cover the common cases.

Frontier says Disconnected or Reconnecting.
  1. Wait briefly for automatic reconnection.
  2. If it stays disconnected, close and reopen Frontier.
  3. If the sign-in page appears, sign in again.
  4. If your organization uses a local model, confirm that the local model service is running.
PC-DMIS, Metrology AI, or Orca is unavailable.
  1. Type /mcp and read the reported state.
  2. For visible desktop products, confirm the product is installed and can open normally.
  3. Restart Frontier after a product bridge or configuration update.
  4. For Orca, the shared Orca service must also be reachable; contact your administrator if its health check fails.
Arena did not switch to the application.

The application may not be running, Arena may be hidden, another application may own the foreground, or Arena may be in Split/Grid/Chat layout. Start the application through the requested task, bring Container forward, choose Agent/single layout if needed, and ask Frontier to show it again.

Frontier is waiting for input.

Look for a choice card or the latest question. Common missing inputs are a full file path, units, measurement scope, feature-to-drawing mapping, probe direction, or permission for online/motion work.

The drawing result looks wrong.

Ask Frontier to show the OCR confidence and drawing location for the item. Correct the value explicitly. Do not allow an uncertain OCR result to become GD&T in the 3D model until you have verified both the text and its matching feature.

A measurement action timed out or was cancelled.

Do not immediately repeat it. Ask: “Inspect the current PC-DMIS routine, probe, and application state. Tell me what completed and what did not. Make no further changes.” Save any open routine before approving recovery actions.

Only a 2D drawing is available and no program is generated.

This is expected. Orca can extract dimensions and GD&T from a drawing, but a 3D CAD model is needed to map requirements to measurable features and generate a CMM program.

What should I send to support?

Send the approximate time, what you asked, the visible status/message, product name/version, and a screenshot or exported conversation if permitted. Tool Log details can help. Remove part-sensitive data and never include passwords, tokens, or API keys.

A safe diagnostic request

Diagnose the current problem without making changes. Check Frontier, the relevant product connection, and the last known task state. Explain the likely cause and the safest next step in plain language.

Manual scope: current Frontier desktop workspace, bundled metrology skills, predefined Metrology AI / PC-DMIS / Orca product bridges, and optional HEX. Frontier Container. Prepared 28 August 2026.