Documentation updates

Author: KrisBraun

README.md

@@ -4,18 +4,18 @@
   </a>
 </p>
 <h1 align="center">
-  Plot Agent SDK
+  Plot Agent Builder
 </h1>
 <p align="center">
-  The official SDK for building <a href="https://plot.day">Plot</a> agents -<br/>
+  The official package for building <a href="https://plot.day">Plot</a> agents -<br/>
   custom code that organizes and prioritizes all your messages, tasks, and apps.
 </p>
 
 ## Packages
 
-- **[@plotday/agent](./agent)** - Core SDK with types, Agent class, built-in tool interfaces, and CLI
-- **[tools/](./tools)** - Tools for building agents, including integrations with popular services
-- **[agents/](./agents)** - Full source code for several Plot agents
+- **[@plotday/agent](./agent)** - Core agent builder package with the `plot` command, agent and tool SDK, and built-in tools
+- **[tools/](./tools)** - Additional tools for building agents, including integrations with popular services
+- **[agents/](./agents)** - Full source code for several agents
 
 ## Quick Start
 
@@ -35,11 +35,11 @@ npm run deploy
 
 ## Documentation
 
-See the [SDK documentation](./agent/README.md) for detailed guides and API reference.
+See the [Plot Agent Builder documentation](https://build.plot.day) for detailed guides and API reference.
 
 ## Changelog
 
-See the [SDK changelog](./agent/CHANGELOG.md) for version history and release notes.
+See the [builder changelog](./agent/CHANGELOG.md) for version history and release notes.
 
 ## License
 

RELEASING.md

@@ -1,18 +1,18 @@
 # Releasing Packages
 
-This repository uses [Changesets](https://github.com/changesets/changesets) to manage versioning and publishing of packages. This guide explains how to create releases for SDK and tools packages.
+This repository uses [Changesets](https://github.com/changesets/changesets) to manage versioning and publishing of packages. This guide explains how to create releases for builder and tools packages.
 
 ## Package Versioning Strategy
 
-- **SDK** (`@plotday/agent`): Independent versioning
+- **Agent Builder** (`@plotday/agent`): Independent versioning
 - **Tools** (`@plotday/tool-*`): Independent versioning
 - **Agents** (`@plotday/agent-*`): Not published, excluded from releases
 
 Each package maintains its own version and can be released independently.
 
 ## How to Add a Changeset
 
-When you make changes to the SDK or any tools package, you need to add a changeset before merging your PR.
+When you make changes to the builder or any tools package, you need to add a changeset before merging your PR.
 
 ### 1. Create a Changeset
 
@@ -25,7 +25,7 @@ This will prompt you with:
 1. **Which packages would you like to include?**
 
    - Select the packages you've modified (use space to select, enter to confirm)
-   - Only SDK and tools packages can be selected (agents are excluded)
+   - Only builder and tools packages can be selected (agents are excluded)
 
 2. **What kind of change is this?**
 
@@ -53,14 +53,14 @@ The changeset file will be created in `.changeset/` with a random name like `.ch
 
 1. **Developer makes changes**
 
-   - Make your changes to SDK or tools packages
+   - Make your changes to builder or tools packages
    - Run `pnpm changeset` to add a changeset
    - Commit the changeset file along with your changes
    - Open a PR to `main`
 
 2. **PR validation**
 
-   - GitHub Actions will check if SDK/tools were modified
+   - GitHub Actions will check if builder/tools were modified
    - If modified, it ensures a changeset file exists
    - PR cannot be merged without a changeset (or admin override)
 
@@ -79,7 +79,7 @@ The changeset file will be created in `.changeset/` with a random name like `.ch
      - Builds all packages
      - Publishes changed packages to npm
      - Creates GitHub releases with changelogs
-     - Tags each release (e.g., `sdk@0.9.1`, `tool-google-calendar@0.1.0`)
+     - Tags each release (e.g., `agent@0.9.1`, `tool-google-calendar@0.1.0`)
 
 ## GitHub Releases
 
@@ -89,7 +89,7 @@ When packages are published, GitHub releases are automatically created with the
 
 Each package gets its own tag based on its directory structure:
 
-- **SDK**: `sdk@0.9.1`
+- **Agent Builder**: `agent@0.9.1`
 - **Tools**: `tool-google-calendar@0.1.0`, `tool-outlook-calendar@0.1.0`, etc.
 
 This tagging convention allows you to:
@@ -112,16 +112,16 @@ View all releases at: `https://github.com/plotday/plot/releases`
 
 Or filter by package:
 
-- SDK releases: Search for tags starting with `sdk@`
+- Builder releases: Search for tags starting with `agent@`
 - Tool releases: Search for tags starting with `tool-`
 
 ### Manual GitHub Release
 
 If you need to create a GitHub release manually after publishing:
 
 ```bash
-# For SDK
-gh release create sdk@0.9.1 --title "@plotday/agent@0.9.1" --notes "Release notes here"
+# For Agent Builder
+gh release create agent@0.9.1 --title "@plotday/agent@0.9.1" --notes "Release notes here"
 
 # For a tool
 gh release create tool-google-calendar@0.1.0 --title "@plotday/tool-google-calendar@0.1.0" --notes "Release notes here"
@@ -198,7 +198,7 @@ git push
 pnpm release
 
 # 5. (Optional) Create GitHub release manually
-gh release create sdk@0.9.1 --title "@plotday/agent@0.9.1" --notes "Release notes"
+gh release create agent@0.9.1 --title "@plotday/agent@0.9.1" --notes "Release notes"
 ```
 
 ⚠️ This should only be done in emergencies. The automated workflow is preferred.
@@ -240,4 +240,4 @@ gh release create sdk@0.9.1 --title "@plotday/agent@0.9.1" --notes "Release note
 
 - [Changesets documentation](https://github.com/changesets/changesets)
 - [Semantic Versioning (semver)](https://semver.org/)
-- [Plot SDK repository](https://github.com/plotday/plot)
+- [Plot repository](https://github.com/plotday/plot)

builder/DOCS.md

@@ -4,7 +4,7 @@ This directory contains the TypeDoc-generated API documentation for the Plot Age
 
 ## Published Documentation
 
-The SDK documentation is automatically published to GitHub Pages whenever changes are pushed to the main branch:
+The Agent Builder documentation is automatically published to GitHub Pages whenever changes are pushed to the main branch:
 
 **Live Documentation**: [https://plotday.github.io/plot/](https://plotday.github.io/plot/)
 
@@ -79,7 +79,7 @@ When changes to the Builder are pushed to the main branch, a GitHub Action autom
 - Builds the Builder and generates the documentation
 - Deploys it to GitHub Pages at [https://plotday.github.io/plot/](https://plotday.github.io/plot/)
 
-**Workflow Location**: `.github/workflows/deploy-sdk-docs.yml`
+**Workflow Location**: `.github/workflows/deploy-docs.yml`
 
 **Trigger**: Automatic on push to `main` when files in `public/agent/**` change
 
@@ -99,13 +99,13 @@ If you need to enable or configure GitHub Pages for this repository:
 2. Under "Source", select: **GitHub Actions**
 3. The workflow will automatically handle deployment
 
-The `deploy-sdk-docs.yml` workflow includes all necessary permissions and configurations for GitHub Pages deployment.
+The `deploy-docs.yml` workflow includes all necessary permissions and configurations for GitHub Pages deployment.
 
 ## Configuration
 
 The documentation generation is configured in `typedoc.json`. Key settings:
 
-- **Entry Points**: Main SDK exports (agent, tool, plot, tools/\*)
+- **Entry Points**: Main Agent Builder exports (agent, tool, plot, tools/\*)
 - **Output**: `dist/docs/`
 - **Visibility**: Public APIs only (excludes private/protected/internal members)
 - **Theme**: Default TypeDoc theme optimized for GitHub Pages

builder/cli/commands/create.ts

@@ -85,7 +85,9 @@ export async function createCommand(options: CreateOptions) {
     const sdkPackage = JSON.parse(fs.readFileSync(sdkPackagePath, "utf-8"));
     sdkVersion = `^${sdkPackage.version}`;
   } catch (error) {
-    console.warn("Warning: Could not read SDK version, using fallback");
+    console.warn(
+      "Warning: Could not read Agent Builder version, using fallback"
+    );
   }
 
   // Generate a unique agent ID

builder/cli/commands/generate.ts

@@ -312,7 +312,7 @@ export async function generateCommand(options: GenerateOptions) {
 
     // Update @plotday/agent to latest and install packages
     try {
-      out.progress("Updating SDK to latest version...");
+      out.progress("Updating Agent Builder to latest version...");
 
       const updateCommand =
         packageManager === "npm"

builder/cli/utils/output.ts

@@ -121,8 +121,7 @@ export function blank() {
  */
 export function cliHeader(version: string) {
   const title = "Plot";
-  const subtitle = `SDK v${version}`;
-  // const title = `Plot SDK ${colors.dim(`v${version}`)}`;
+  const subtitle = `Agent Builder v${version}`;
   const underline = colors.brand(
     "─".repeat(title.length + subtitle.length + 1)
   );

builder/docs/BUILDING_TOOLS.md

@@ -37,7 +37,7 @@ Build custom tools when you need to:
 | ------------------------------ | ------------------------------------ |
 | Plot, Store, AI, Network, etc. | Your integrations and utilities      |
 | Access to Plot internals       | Built on top of built-in tools       |
-| Provided by SDK                | Created by you or installed from npm |
+| Provided by Agent Builder      | Created by you or installed from npm |
 | Always available               | Declared as dependencies             |
 
 ---

builder/tsconfig.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json.schemastore.org/tsconfig",
-  "display": "Plot SDK",
+  "display": "Plot Agent Builder",
   "compilerOptions": {
     "target": "ESNext",
     "lib": ["ES2021", "ES2022.error", "WebWorker"],

builder/typedoc.json

@@ -42,7 +42,7 @@
     "docs/RUNTIME.md",
     "docs/ADVANCED.md"
   ],
-  "name": "Build Plot Agents",
+  "name": "Plot Agent Builder",
   "includeVersion": false,
   "disableSources": false,
   "sourceLinkTemplate": "https://github.com/plotday/plot/blob/main/builder/{path}#L{line}",