Configure Documentation

Identity and memory infrastructure for AI agents.

Configure gives your agent persistent memory about users — identity, preferences, and per-app memories — along with access to their connected tools (Gmail, Calendar, Drive, Notion). Profiles persist across sessions and agents. Context follows the user, not the app.

What a profile looks like

Every user gets a structured profile that any agent can read. Profiles are built automatically from conversations, connected tools, and explicit memory saves.

{
  "identity": {
    "name": "Sarah Chen",
    "email": "s••••@chendesign.co",
    "phone": "+1 (415) •••-••42",
    "summary": "designer, frequent traveler, pescatarian"
  },
  "preferences": [
    "window seat, forward cabin",
    "pescatarian, no shellfish",
    "boutique hotels preferred, no chains",
    "never book before 10am"
  ],
  "memories": {
    "atlas": ["planning Kyoto trip, March 2026", "prefers direct flights, United loyalty"],
    "focusai": ["deep work blocks: Tue/Thu mornings"],
    "wealthbot": ["saving for house, risk tolerance: moderate"]
  },
  "tools": {
    "gmail": "synced",
    "calendar": "12 upcoming events",
    "drive": "847 files searchable",
    "notion": "3 workspaces"
  }
}

The same user, recognized by phone number, carries this profile across every agent they connect to.

How it works

1. User connects — call profile.get() and profile.format() to get user data as a string you inject into your own prompt. Use CONFIGURE_TOOLS for function calling
2. During conversation — search Gmail, Calendar, Drive, Notion, or the web for real-world context
3. After conversation — call profile.ingest() and Configure extracts and stores memories automatically
4. Next session — the profile is already enriched. Your agent picks up where it left off

Profiles start empty

New users have a blank profile. Connect Gmail, import chat history, or batch-import existing user data to get personalized responses from the first message. Learn about profile seeding →

Setup

Prompt-based (fastest)

Paste the Configure skill into your agent's system prompt — no SDK install required:

configure.dev/skill.md

Your agent gets the full API reference inline and can make REST calls directly. Works with any model, any framework.

SDK

npm

npm install configure

yarn

yarn add configure

pnpm

pnpm add configure

Get an API key

npx configure setup

Opens a browser session where you sign in, name your agent, and receive an API key. Save it as CONFIGURE_API_KEY in your environment.

You can also create keys manually at platform.configure.dev.

First API call

<!-- Drop-in auth component handles the entire phone OTP flow -->
<script src="https://unpkg.com/configure/dist/configure-components.global.js"></script>
<configure-auth api-key="pk_..." agent="your-agent"></configure-auth>
<script>
  document.querySelector('configure-auth')
    .addEventListener('configure:authenticated', (e) => {
      const { token, userId } = e.detail;
      // Pass token + userId to your backend
    });
</script>

import { ConfigureClient, CONFIGURE_TOOLS } from 'configure';

const client = new ConfigureClient('sk_...');

// token + userId come from the frontend after <configure-auth> authenticates
const profile = await client.profile.get(token, userId);
const context = profile.format();

// Your prompt, your rules — Configure doesn't touch it
const systemPrompt = `You are my agent.\n\n${context}`;

Key concepts

Memory Profile

A structured record of everything Configure knows about a user: name, email, occupation, interests, preferences, and per-app memories. Profiles are built automatically from conversations and connected tools.

Connected tools

OAuth integrations for Gmail, Calendar, Google Drive, and Notion. Once a user connects a tool, any agent with their token can search it. Web search is always available without a connection.

Agent Storage

A persistent virtual filesystem for your agent. Store your personality, operational memory, skills, and notes at paths like /soul/, /memory/, /skills/. State survives restarts, resets, and context window limits. Access it through client.self.

What's next

• Quick Start — Add Configure to your existing agent in 4 steps
• Installation — API keys, authentication, and setup
• SDK Reference — Complete API reference