Skip to content
Type Type Type Help
Changelog

Report a bug

Agent-readable Map

This page uses current product language first, followed by common implementation names.

Canonical terms

Section titled “Canonical terms”
User-facing termImplementation termMeaning
Spacechannel, agent, default channel agentShared computer for a department, with one harness and shared channels, threads, skills, connections, automations, memory, and Library
Channelroom, subchannelNamed area that organizes work inside a Space without duplicating its computer or setup
Threadsdefault roomConversations not assigned to a named channel
Space templateChannelCreationTemplate, legacy blueprint IDEditable starting prompt that can propose skills, automations, and connections
Threadthread, conversation messagesOne conversation in a Space, channel, Ping, Inbox, or Sidekick
Connectorintegration, toolkit, appApp, API, or data source Type supports
Connectioncredential, OAuth grant, API key configConfigured account or credential assigned to one or more Spaces
Skillskill, slash commandReusable Markdown instructions with optional scripts and assets
Automationtask, event source, ruleScheduled or event-driven work that runs in a Space
Memorymemory shard, MEMORY.md, memory_summary.mdContext scoped to a workspace, Space, or person
Documentdoc, editable fileEditable written file people and AI can create, revise, and share
Appapp, preview appAI-built web app with optional persistent data
Libraryfiles, Space libraryFiles, apps, and skills in a Space, plus accessible items across the workspace
Sidekicksidekick agentPrivate AI surface for one person
PingDM, direct messageOne-to-one human conversation
Inboxinbox itemPersonal queue with unread, read, and archived states
OverviewSpace overviewSpace front page with attention, recent work, and automation runs
HarnessAgentHarnessRuntime such as Type-hosted Claude or Codex

Product object map

Section titled “Product object map”
workspace:
  contains:
    - members
    - spaces
    - pings
    - sidekick
    - inbox
    - global_library


space:
  has:
    - shared_computer
    - harness
    - model
    - overview
    - threads
    - channels
    - library
    - connections
    - automations
    - memory
    - ai_defaults
    - visibility
    - members


channel:
  belongs_to: space
  contains:
    - threads
    - connected_sources
    - automations


thread:
  can_include:
    - team_messages
    - ai_responses
    - files
    - skill_invocations
    - app_mentions
    - person_mentions
    - tool_calls
    - previews
    - documents
    - apps

Main user journeys

Section titled “Main user journeys”
  1. Create a Space from Engineering, Marketing, Support, Sales, Data, HR & Ops, or a custom prompt.
  2. Choose Claude or Codex, then review proposed skills, automations, and connections in the setup thread.
  3. Configure identity, AI defaults, access, notifications, connections, automations, and memory in Space settings.
  4. Add skills from the Space Library.
  5. Use Threads for unassigned work and channels for durable topics or destinations.
  6. Start with AI response, or switch to Team message for a conversation that should not invoke AI.
  7. Invite coworkers to prompt, comment, and continue from the same shared thread.
  8. Build documents and apps that become part of the Space Library.
  9. Use the Space overview for shared attention and Inbox for personal notifications.

Template registry

Section titled “Template registry”

User-facing titles have changed, but implementation IDs remain stable for compatibility.

Current titleInternal template IDLegacy handle aliasesDefault access
Datadata-insightsdata-analystPublic
Engineeringproduct-expertsoftware-engineer, product-engineerPublic
Marketingmarket-pulsemarketing-managerPublic
Supportsupport-triagesupport-specialistPublic
Salessales-operationsNonePublic
HR & Opshr-partnerNonePrivate
Section titled “High-value docs links”