HalosHalosDocs

Knowledge Base

Your knowledge base is the brain behind all your agents. It's a structured, searchable collection of everything your agents know about you — facts, preferences, context, and notes. Every agent on your account can access it, making it the shared foundation that powers personalized responses.

How It Works

The knowledge base stores discrete pieces of information as entries. Each entry has:

  • Content — The actual information (a fact, a preference, a note)
  • Type — What kind of information it is (fact, preference, knowledge, or note)
  • Title — A short label for easy identification
  • Importance — A priority score that helps agents decide what's most relevant
  • Source — Where the entry came from (onboarding, manual, import, etc.)

When an agent generates a response, it searches your knowledge base for relevant context and weaves it into its answer. This happens automatically — you don't need to tell the agent to "check the knowledge base."

Where Knowledge Comes From

Halo Onboarding

When you first sign up, your conversation with Halo is automatically analyzed and broken down into individual knowledge entries. If you told Halo "I'm a product manager at a SaaS company and I use Notion for everything," that becomes entries like:

  • Fact: "Works as a product manager"
  • Fact: "Works at a SaaS company"
  • Preference: "Uses Notion as primary knowledge management tool"

This is the fastest way to seed your knowledge base — a 10-minute conversation can generate 20-30 entries.

Manual Entries

You can add entries directly from the Knowledge page. This is best for:

  • Specific facts you want agents to know
  • Preferences about how you like things done
  • Context about projects, people, or processes
  • Reference material agents should have access to

Ongoing Conversations

As you continue chatting with your agents, they build up context through conversation. Important details are stored in their memory, and you can promote key memories to knowledge base entries.

Collections

Collections let you organize your knowledge base into logical groups. Think of them like folders or tags.

Default Collection

Every account has a default collection called "About Me" (or similar). This is where onboarding knowledge goes and where general personal context lives.

Creating Collections

You might want collections for:

  • Work — Job-related knowledge, company info, team details
  • Projects — Context for specific projects you're working on
  • Personal — Personal preferences, routines, goals
  • Reference — Documentation, specs, guides

To create a collection:

  1. Go to the Knowledge page
  2. Click New Collection
  3. Give it a name and optional description
  4. Start adding entries or move existing ones in

Agent Access

You can control which agents have access to which collections. For example:

  • Your email agent might access "Work" and "Reference" but not "Personal"
  • Your personal assistant might access everything
  • Your code agent might only need "Projects" and "Reference"

This lets you share context selectively rather than giving every agent your entire knowledge base.

Entry Types

Facts

Objective information about you, your work, or your world.

Examples:

  • "Works at Acme Corp as Director of Engineering"
  • "Team has 12 engineers across 3 time zones"
  • "Company uses AWS for cloud infrastructure"

Preferences

How you like things done — communication style, format preferences, priorities.

Examples:

  • "Prefers bullet points over long paragraphs"
  • "Likes to start emails with the recipient's first name"
  • "Prioritizes security concerns over performance in code reviews"

Knowledge

Domain knowledge, reference material, or expertise areas.

Examples:

  • "Expert in React and Next.js, familiar with Vue"
  • "Company return policy: 30 days, unused, original packaging"
  • "Q3 revenue target: $2.5M"

Notes

Temporary or contextual information.

Examples:

  • "Currently preparing for the board meeting on March 28"
  • "Working on migrating from REST to GraphQL"
  • "On vacation next week — all meetings rescheduled"

Managing Your Knowledge Base

Viewing Entries

The Knowledge page shows all your entries organized by collection. Each entry displays:

  • Title and content preview
  • Type badge (fact, preference, knowledge, note)
  • Source indicator (onboarding, manual, etc.)
  • Importance score

Editing

Click any entry to edit its content, type, title, or importance. Changes take effect immediately across all agents that have access to that collection.

Deleting

Remove entries that are no longer accurate or relevant. Deleted entries are permanently removed.

Searching

Use the search bar to find entries by keyword. This searches both titles and content.

Knowledge Base vs. Training Data

These two systems complement each other:

| | Knowledge Base | Training Data | |---|---------------|--------------| | Scope | Shared across all agents | Specific to one agent | | Contains | Facts about you, your work, your preferences | Instructions, examples, agent-specific knowledge | | How agents use it | Searched contextually for relevant background | Injected directly into the agent's system prompt | | Best for | "Who am I, what do I do, what matters to me" | "How should THIS agent behave" |

Rule of thumb: If the information is about you and relevant to multiple agents, put it in the knowledge base. If it's about how a specific agent should behave, put it in training data.

Exporting Your Knowledge

You own your data. You can export your entire knowledge base at any time from the Knowledge page. The export includes all entries across all collections in a structured format.

This is useful for:

  • Backing up your data
  • Migrating to a different platform
  • Reviewing what your agents know about you
  • Sharing context with a colleague or team

API Access

For advanced users, Halos provides API keys for external knowledge access. This lets you:

  • Read from your knowledge base programmatically
  • Write new entries from external tools or scripts
  • Build custom integrations that feed into your knowledge base

Generate API keys from the Knowledge page settings.

Tips for a Great Knowledge Base

Keep It Current

Review your knowledge base periodically. Outdated information — last quarter's targets, a former team member's role, old project details — can lead to inaccurate agent responses. Update or remove stale entries.

Be Specific

"Works in tech" is less useful than "Senior product manager at Acme Corp, a B2B SaaS company that makes project management tools for enterprise teams." The more specific your entries, the more personalized your agents' responses.

Use Importance Scores

High-importance entries (0.8-1.0) are more likely to be surfaced when agents generate responses. Mark critical context as high importance and background details as lower.

Organize with Collections

As your knowledge base grows, collections keep things manageable. A well-organized knowledge base with 50 entries beats a messy one with 200.

Next Steps

  • Agent Types — See which agents use knowledge most effectively
  • Training — Add agent-specific behavior rules
  • Integrations — Connect real tools so agents can act on data
  • Todos & Goals — Track tasks that reference your knowledge
  • Workflows — Put your knowledge to work with step-by-step tutorials