---
title: The Glass Agent
summary: A glass agent is a customer-facing AI agent for the sales funnel that you — and the customer — can see straight through. It works only from an approved packet (the customer's own record plus a curated memory layer), holds no keys, sources every answer, and acts only within written permissions, with a human owning the threshold.
tags: [glass-agent, definition, sales-funnel, transparency]
updated: 2026-06-24
source: content/glass.md, architectures.md, founder direction 2026-06-24
---

# The glass agent

**A glass agent is a customer-facing AI agent for the sales funnel that works only from an
approved packet — the customer's own record plus a curated memory layer — and that you can see
straight through.**

That's the whole definition, and every word is load-bearing:

- **Customer-facing, in the sales funnel.** A glass agent lives at the edge where your business
  meets a prospect or customer — outreach, qualification, quoting, onboarding, renewals. The
  place where trust is scarce and every interaction can win or lose the deal.
- **Works from an approved packet.** Its context is assembled before it answers, from two inputs
  only: the **user object** (the customer's own record, pulled live from your systems) and a
  curated **[memory layer](about-okf.md)** (the durable knowledge the job needs). It's *handed*
  what the job needs up front — it doesn't go fishing for context the way a bolt-on retrieval
  (RAG) agent does. It can use nothing else.
- **You can see straight through it.** Every answer traces to a source you can read; its entire
  briefing is published as [the OKF bundle](about-okf.md). No black box.
- **Holds no keys.** No credentials, no database, no path to your systems. The shape
  that does this has a name — **Broker + Blind Agent** (*context, not access*): a
  trusted broker assembles the packet and also hands over the right slice of the
  memory layer at session time, so the agent is *given* its memory, not *searching*
  for it like a RAG bolt-on. (See [how it's built](architectures.md).)
- **Acts within written permissions.** It takes only the actions it's explicitly allowed, and a
  human owns the threshold where it stops and asks. Never "fully autonomous."

The point of the moniker is the contrast: most agents you're sold are opaque and over-permissioned.
A glass agent is the opposite — narrow, sourced, and legible by design — which is exactly what
lets you put one in front of a customer.

## The name, if it comes up

In this demo the glass agent goes by **Halia** — "of the sea," a nod to
[Thalatta](about-thalatta.md). It's a small thing; the definition above is what matters.