Complete Guide to the Agent Workspace

The Agent Workspace is your “control panel” for understanding how Hapax is working behind the scenes—not just what answer it gives you.

Instead of treating AI as a black box, the Agent Workspace shows you:

The plan Hapax is following
The files and artifacts it created or used
The processes and tools it has available (and may be using)

This guide explains each section of the Agent Workspace and how to use it to build trust, troubleshoot, and get more value out of Hapax.

1. What Is the Agent Workspace?

The Agent Workspace is the area of Hapax where you can see:

Current Plan – The step-by-step plan Hapax is following for complex or multi-stage tasks.
Context Files – The documents, data, and intermediate files Hapax has created or referenced in this conversation.
Available Processes – The list of structured workflows, tools, and agentic processes Hapax can use (or is using) for this session.

You can use the Agent Workspace to:

Understand how Hapax arrived at its answer
Confirm which files and tools were involved
Inspect intermediate outputs (JSON, scripts, markdown, etc.)
Gain confidence in the logic and auditability of the AI’s work

2. Current Plan

2.1 What Is “Current Plan”?

For complex or multi-step tasks, Hapax may generate a structured plan before it produces a final response.

The Current Plan section shows you that plan, including:

The steps Hapax intends to take
The sequence in which those steps will run
The logic behind the workflow

You can think of it as a live, readable checklist of what the agent is about to do.

2.2 When Does Current Plan Show Up?

Current Plan is most useful when you ask Hapax to do something that is:

Multi-step (e.g., “Review these documents, summarize key changes, then draft communication to staff.”)
Involves workflows (e.g., compliance checks, document analysis, data extraction)
Requires coordination of multiple tools or processes

In these cases, Hapax first builds a plan, then executes it step-by-step. The Current Plan section lets you see this planning phase.

2.3 Why It’s Useful

Current Plan helps you:

Understand the approach – You can see how Hapax is thinking about your request.
Catch misunderstandings early – If the plan doesn’t match what you intended, you can stop and adjust your prompt.
Build trust with stakeholders – For regulators, auditors, or internal reviewers, you can show the logic behind the AI’s actions.

2.4 How to Use Current Plan in Practice

Review the steps before Hapax finishes:
- If the plan is off, refine your prompt (e.g., “Don’t rewrite the whole policy, just summarize changes.”)
Use it as documentation:
- When explaining your work to others, you can describe the steps Hapax followed using the Current Plan as a reference.
Train staff:
- Show new users how a good, detailed prompt leads to a clear multi-step plan, which then leads to better outputs.

3. Context Files

3.1 What Are Context Files?

Context Files are the documents, data, and artifacts that Hapax creates or uses during this conversation.

This includes:

Files created by the agent (e.g., JSON outputs, Python scripts, markdown notes, structured data files)
Files produced by underlying workers or processes in the background
Any artifacts that Hapax relies on to answer your prompt

These files are clickable: you can open them, inspect their contents, or download them.

3.2 What Context Files Show You

The Context Files section displays:

Exactly which files were used to answer your prompt
Files created mid-workflow (for example, parsed data, intermediate analysis, or transformed documents)
Artifacts associated with different workers or processes involved in this session

This provides full transparency into:

“What did Hapax actually look at or generate to produce this answer?”

3.3 Why Context Files Matter

Context Files are especially valuable for:

Audit and compliance
- You can see and retain the intermediate artifacts that supported a recommendation or decision.
Troubleshooting
- If something looks off, you can inspect the underlying file (e.g., a JSON mapping or an extracted table) to find where the issue began.
Re-use
- Sometimes an intermediate file is useful on its own (e.g., a cleaned dataset, a summary markdown file). You can download and reuse it elsewhere.

3.4 How to Work with Context Files

Click on a file to open and inspect the content.
Use downloads to save outputs like structured data, scripts, or formatted reports.
When you’re unsure how Hapax got to a conclusion, check Context Files to see the supporting artifacts.

Practical examples of Context Files you might see:

A JSON file mapping fields from a loan package to your standard schema
A Python script used to process transaction data
A markdown summary of regulatory changes pulled out of a long proposal
A structured checklist produced mid-way through a workflow

4. Available Processes

4.1 What Are Available Processes?

Available Processes are the structured workflows, tools, and agentic operations that Hapax can use in this session.

Each process:

Represents a defined “playbook” or workflow (e.g., document compliance review, check hold analysis, business account verification)
Is authorized and available for the current conversation
May be called automatically by Hapax when it’s relevant to your request

The Agent Workspace shows you which processes:

Hapax used to answer your prompt
Hapax could use to complete your task

4.2 What You See in Available Processes

For each process, you will see:

The name of the process
A short description explaining what it does
The type of operation (e.g., retrieves documents, runs a compliance check, executes a workflow, performs data extraction, etc.)

You can select the dropdown for each process to view more details about:

What the process is designed to do
When it’s typically used
How it contributes to answering your request

4.3 Why Available Processes Are Important

Available Processes help you:

Understand capability – You can see what Hapax could do, not just what it did this time.
Discover tools you didn’t know existed – For example, a specific workflow for business account verification or ACH opportunity analysis.
Explain automation to others – When someone asks, “What did the AI actually run?”, you can point to the named process and description.

4.4 How to Use Available Processes in Your Work

Before you ask a question:
- Scan Available Processes to get ideas: “Oh, there’s a compliance review workflow — I can phrase my prompt to leverage that.”
After you get an answer:
- Check which processes were used so you understand the path taken.
When training users:
- Use the descriptions to show staff which workflows exist and how to ask questions that trigger them.

5. How the Agent Workspace Helps You Day-to-Day

Taken together, the three sections of the Agent Workspace give you:

Clarity – You see the plan (Current Plan).
Evidence – You see the supporting artifacts (Context Files).
Capability Awareness – You see the toolbox (Available Processes).

This is especially powerful for:

Complex workflows (e.g., business account verification, dispute handling, check holds, ACH analysis)
High-stakes decisions (compliance, risk, audit, policy changes)
Cross-team collaboration (operations, compliance, lending, IT)

Instead of saying, “The AI told me this,” you can say:

“Here’s the plan it followed.”
“Here are the files it created and used.”
“Here are the processes it ran.”

That level of detail supports better oversight, faster troubleshooting, and stronger trust.

6. Best Practices for Using the Agent Workspace

6.1 For Everyday Users

Glance at Current Plan when you run a big or complex request.
Check Context Files when you’re curious or something feels off.
Use Available Processes to learn what Hapax can do and refine your prompts to tap into those capabilities.

6.2 For Power Users & Admins

Use Context Files and Available Processes to validate that workflows are behaving as expected.
When something goes wrong, start with:
- Current Plan → Did Hapax understand the task correctly?
- Context Files → Did intermediate artifacts look correct?
- Available Processes → Did it use the right workflow or tool?
Use the Agent Workspace as a teaching tool to standardize how teams work with Hapax.

7. Common Questions About the Agent Workspace

Q: Why don’t I always see a detailed Current Plan?
A: Not every task requires a multi-step plan. For simple or direct questions, Hapax may not need to build a visible plan and can respond directly.

Q: I see files in Context Files that I don’t recognize. What are they?
A: Many workflows create intermediate artifacts (like JSON, scripts, or markdown summaries) to help the agent reason. You can click any file to inspect it and see what it contains.

Q: Can I control which processes are available?
A: Process availability is typically configured by your institution’s admins or workflow designers. The Agent Workspace simply shows you which ones are authorized and available for the current session.

Q: What should I do if the plan doesn’t match what I intended?
A: Refine your prompt. Be more explicit about what you want (and don’t want). You can use the Current Plan section to see exactly where Hapax misunderstood your request.

8. Summary

The Agent Workspace turns Hapax from a black-box AI into a transparent, auditable assistant:

Current Plan shows you the steps Hapax intends to take.
Context Files show you the actual artifacts created and used.
Available Processes show you the workflows and tools behind the scenes.

Use these three sections together to understand, trust, and fully leverage Hapax’s agentic capabilities in your day-to-day work.