Add agent-specific context with Hubs

Foundation Models have powerful generalized knowledge but will perform less well at business specific tasks, unless they have the right context. Hubs allows you to bring this business specific context directly into Go to better guide AI models.

A Hub houses universal files that can be used as inputs/references in any Go agent. You can create multiple Hubs.

How does this work?

1. First, you'll need to create a new Hub. Navigate to the "Knowledge" tab in your workspace, then select "Hubs" from the top.

2. Click "Create a hub". A clear name and description help Hubs generate the right context for every answer and workflow. Why Descrptions Matter.
3. Once created, you can upload new files to a Hub by clicking the "+" icon on the top right of the page, as below:

You can now use one or more of these Hubs as inputs within your agent workflow.

There are two ways to do this:

Reference a Hub as an input to a Property

When you want to reference the files within just a single Hub, you can add it as an input to a property (every row will use the same Hub).

1. Within a property, select the "@" icon to edit the inputs.
2. Select a Hub from the list.
   • Note: You MUST reference another property for this to work. If you only reference the Hub it will remain stuck in “Waiting for configuration”.

In this case, we've added 'Company Glossary' that will show GPT5 the company-specific language that our example user would like to see in the output.

Dedicated Hub Property

You can create a Hub property to dynamically change the selected Hub per entity, then reference the Hub property in downstream properties.

Practical Advice: When to Split Hubs

Why Descriptions Matter

• The Hub description is used as context for indexing and search. A clear, specific description helps the system understand the purpose of the files and deliver more relevant answers.
• When you search or ask questions, the Hub’s description guides the AI in providing contextually accurate responses.

When to Split Hubs

• Group files together only if they share the same purpose and description.
• Create a new Hub when:
  • You have files for a different company, project, or transaction.
  • The files serve a different business function (e.g., HR vs. M&A).
• Don’t mix unrelated files (e.g., contracts and HR policies) in the same Hub—this will reduce search quality and clarity.

Example:

• Good: All files for "Acme Corp Due Diligence" in one Hub with a clear description.
• Not Good: Mixing "Acme Corp Due Diligence" with "Internal HR Policies" in the same Hub.