# Foldspace terms

The words Foldspace uses for its building blocks — agent, action, Agentic UI component, task agent, navigation, knowledge, publish — each in one sentence, with the words not to use.

One list, so every surface means the same thing by the same word: these docs, Agent Studio, the sign-up flow, the Foldspace MCP tools, and the coding agents that build on Foldspace. If you write about Foldspace anywhere — including instructions for an AI coding agent — use these words and link here rather than redefining them.

## The building blocks

| Say | What it is | Not |
| :--- | :--- | :--- |
| **agent** | The AI agent embedded in your product through the SDK. Your users talk to it instead of clicking through. See [Introduction](/start/introduction/). | bot, assistant. Older pages say *Copilot*; it is the same thing. |
| **Agent Studio** | Where you configure what the agent can do: actions, input schemas, knowledge, navigation, and how it looks. See [Agent Studio](/user-guides/agent-studio/). | dashboard, console |
| **action** | One thing the agent can *do* in your product: call your API, submit a form, navigate, or render a component. It has two halves — you **define** it in Agent Studio (name, description, input schema) and **implement** it in your code. See [Build actions](/guides/build-actions/). | skill, tool, function, ability |
| **action handler** | The code behind an action: `execute`, and optionally `render`. It runs in your user's browser, on your page, with their session. With a non-developer, say *the code behind the action*. See [Connect actions](/guides/connecting-actions/). | bundle, script |
| **Agentic UI component** | What an action renders in the chat — a card, a form, a picker, a confirmation. With a non-developer, say *a card*. See [UI components in chat](/guides/in-chat-ui/). | widget, chatterblock |
| **task agent** | A specialised sub-agent the main agent hands one focused job to, which keeps that reasoning out of the main conversation. See [Task agents](/user-guides/task-agents/). | sub-prompt, workflow |
| **navigation** | The routes that let the agent take the user to a page in your product. | links, redirects |
| **knowledge** | The content the agent answers from: crawled pages, articles, help-desk connectors. See [Adding knowledge sources](/user-guides/knowledge-sources/). | training data |
| **conversation starters** | The predefined prompts on the agent's entry screen, in two groups — KNOWLEDGE and ACTION. Set in Agent Studio; overridable per page from code. See [Conversation starters](/customize/conversation-starters/). | suggestions, quick replies |

## The verbs

| Say | What it means | Not |
| :--- | :--- | :--- |
| **publish** | Make a saved version available to the agent. Every save creates a version; an action is `Draft` until it is `Published`, and the agent can only use published ones. See [Authoring actions](/user-guides/authoring-actions/). | deploy, release, switch on, enable |
| **test mode** | Marks your own sessions as test traffic, so they stay out of analytics and out of the default Conversations list. See [Test mode](/reference/test-mode/). | sandbox, staging |

## For AI coding agents

When you build on Foldspace for someone who is not a developer, use the words in the **Say** column and explain each one the first time you use it. Never invent a substitute: a customer who saw *Actions* at sign-up and in Agent Studio has no way to know that a "skill" is the same thing. If the person uses technical words themselves, match theirs.