No need to memorize these all at once. When you run into one you don’t know, look that one up; every explanation ties back to the Weekend Walk Club invitation page.
Agent
Short for AI agent: an AI system that works toward a goal by using tools, checking the results, and keeping the task moving. For example, when you ask it to make an invitation webpage, it creates the file, checks the content, then makes changes based on your feedback. What it can actually do depends on the model, Harness, tools, and environment; memory and Skills can help it work even better. Back to Chapter 1.
Model
The engine that processes context, understands requests, and generates content or suggested actions. For example, it turns “keep the tone light” into new invitation copy. Specific versions of GPT and Claude belong here. See how it splits the work with the Harness.
Harness
Software that organizes the model, context, tools, permissions, and how things run. For example, it keeps reading the invitation page, making the edit, and sending back the result happening one after another. Codex and Claude Code are the Agent products and Harness entry points this tutorial uses. Back to Chapter 2.
Tool
An interface that lets the Agent perform one specific action. For example, a tool that reads index.html returns the file’s contents; an editing tool changes the meeting time. Just because the model proposes an action doesn’t mean the matching tool is available. See how tools take part in a task.
Prompt
The input or task request you give an Agent. For example, “Move the meeting time under the heading and keep everything else.” A clear goal, materials, and a way to check the result help it understand you better than a string of mysterious keywords. Copy the task for your first webpage.
Context
The information the model can see while handling the current task. For example, the event plans you just gave, the webpage content it has already read, and the results tools sent back. Just because a history exists doesn’t mean all of it is visible right now. See how context differs from memory.
Memory
Information that’s saved so later tasks can use it again. For example, write the confirmed event plans into a project note, then have the Agent read that note first next time before editing the webpage. How things get saved and read back automatically varies by product, and you also need to check whether the content still holds. See how to leave memory and experience behind.
Skill
Instructions and supporting materials an Agent uses for related tasks; you’ll usually see them called Skills. For example, an event page handbook that says to confirm the time and place first, then build the page, and finally check the phone layout; it can also come with templates or small programs. A Skill provides the method; the actual actions still rely on tools. Meet the how-to handbook.
Plugin
An add-on package that gives the Agents in a Workspace new abilities, with Skills, tools that connect to other services, or both inside. You install plugins from “Plugin” in the Agent.Space left sidebar; install one once, and every Agent in the Workspace can use it. The abilities for building webpages, widgets, and scheduled tasks also come as built-in plugins. See how Skills and plugins relate.
Workspace
A project space that brings together members, files, Agents, and Sessions, and provides an environment to run things in when needed. The Weekend Walk Club is a Workspace. You and your friends can each call on Agents inside it and work together on the same invitation page. Meet the cloud Workspace, or try working together.
Session
An ongoing conversation with an Agent. In the same Workspace, members with edit access can keep sending requests in the same Session, or call on Agents separately in different Sessions. Switching Harnesses takes a new Session, along with a clear handoff of the background it needs; sharing files doesn’t mean all Agent context is shared automatically. Learn how to talk it over and split up the work.
Token
One of the units for measuring the text and other content a model processes. A Token doesn’t map neatly onto one word or one character. Reading materials, generating replies, and making repeated calls can all add to your usage. On Agent.Space, usage is deducted from your plan or credits based on the model you choose and is paid for by the Workspace owner; the product’s own details have the final say. See how to get usage ready before you start.
Preview
A way to look at your work before you share it for real. The file preview shows the current file; “Preview full website” prepares the whole webpage folder as a site at one specific version, so after you edit files you need to click “Update preview.” Temporary pages marked “Development preview” also depend on a running server. All of these previews are visible only to Workspace members. Tell the ways of viewing apart.
Site
A full website prepared from a webpage folder. At first, only Workspace members can see it; only after you deliberately choose “Publish site” do you get a fixed public link that anyone can open. All sites can be found under “Sites” in “More” in the left sidebar. See the steps for sites and publishing.
Publish
The deliberate step of putting a chosen version of a site on a public link. Saving files and updating the preview don’t change the public version on their own; when the site shows “Unpublished changes,” you need to click “Publish update” for it to switch over. After publishing, you can also roll back to an earlier version or take the site offline. See the steps for sharing.