Getting Started

This guide walks you through creating a Kajoo Agentic workspace, connecting your environments, and starting your first AI-assisted delivery workflow.

If you haven't read the Overview yet, start there — it covers what Kajoo Agentic does and who it's for. For a full explanation of platform concepts (workspaces, agents, skills, recipes), see Platform Concepts once you're ready to go deeper.

📘

This guide is written for developers and solution architects setting up the workspace, as well as delivery leads and project managers overseeing the migration. Technical steps are called out clearly — non-technical readers can follow the flow and hand off specific steps to their team.

---

Step 1 — Access Kajoo Agentic

If you're an existing Kajoo Classic subscriber

You already have access. Kajoo Agentic shares the same organization, users, and authentication as Kajoo Classic — no separate account or invitation required.

You'll see a Kajoo Agentic entry in the left navigation of your Classic dashboard, along with an introductory banner. Click either to launch the Agentic workspace. You can manage team members and their roles inside Kajoo Agentic, under General Settings → Teams. See Team, roles and sharing.

If a teammate invited you

1. Open the invitation email and click the link. It's valid for 7 days.
2. On the page that says you've been invited to your team's organization, click Set a password.
3. Choose a password, click Save Password, then Continue to Kajoo to sign in.

Once you have an account, you can also sign in with Google or LinkedIn using the same email. The first time, Kajoo asks for your Kajoo password once to link the two, and you keep the same organization and workspaces.

If you're new to Kajoo

Kajoo Agentic is currently available by invitation. Reach out to your Kajoo contact or contact us to get access.

📘

You can switch between Kajoo Classic and Kajoo Agentic at any time. Your organization, users, and billing are shared — there's no separate login or account to maintain.

---

Step 2 — Create a workspace

Open the user menu at the bottom of the sidebar, choose the workspace row, and click Create New Workspace. You'll be prompted to choose how to create it:

Start from a recipe (recommended)

Choose Start from Recipe and pick one from Select Recipe. Recipes are pre-configured workspace templates for specific delivery use cases. Choosing a recipe automatically provisions the full agent team, MCP connections, skills, and tool configurations — along with a setup wizard to connect your environments.

For most teams this is the right choice. Everything is pre-configured; you just connect your project and start working.

Recipes are grouped by library: Kajoo's own, and any your organization has added. See Recipes for the full list and roadmap.

Start from scratch

If no recipe covers your use case, you can build a workspace manually — adding your own agents, connections, skills, and prompt templates. Start-from-scratch workspaces are fully supported and can be as simple or sophisticated as your workflow requires.

📘

You can use an existing recipe workspace as a reference when building from scratch.

---

Good to know before you start

Sessions are resumable. Every phase saves progress as artifacts in your workspace. Open a new chat session at any time and agents pick up from where you left off.

Your plan lives on the task board. Work is organized as phases and tasks in each project. Agents update them as they go, so you always see what's done and what's next. See Tasks and phases.

You choose how often agents ask. Each chat has an approval mode: Default Approvals follows each tool's setting (high-impact tools need your approval; routine reads don't), Auto Approvals lets Kajoo run the safe actions without asking, and Bypass Approvals approves everything. See Working in chat.

Multiple workspaces and projects are supported. Create one workspace per use case and one project per engagement or client site. Workspaces are fully isolated from each other.

Don't run two code migration sessions in parallel. Code migration sessions share the same sandbox — running them concurrently causes conflicts. You can run code migration and content migration in parallel, as they operate on independent systems.

---

Step 3 — Connect your environments

When you create a workspace from a recipe, the setup wizard guides you through connecting the environments that recipe needs — typically source and target code repositories and CMS instances.

Each recipe has its own environment setup guide with the exact steps and credentials required:

📘

You don't need environments fully ready before creating a workspace. Create it, explore the configuration, and connect environments when they're ready.

---

Step 4 — Explore your workspace

Once your workspace is created, you'll find:

Agents — the AI workers provisioned for this workspace. Each agent has a role, tools, skills, and an LLM assigned to it. If you started from a recipe, everything is pre-configured. You can review, adjust, or extend any agent at any time.

Connections — the MCP servers registered in this workspace, under Workspace Settings → MCP Servers. Each connection exposes tools that agents can call. You can add your own here — for example GitHub, Azure DevOps, Figma, or any remote MCP server.

Models — the models your agents can use, under Workspace Settings → LLM Models. New workspaces start with every model turned on and Auto as the default.

Projects — the working areas inside the workspace. A workspace can have multiple projects (one per client site or engagement). Inside a project, the rail on the left has Chat, Plan, Artifacts, Scheduled jobs and Settings. On a phone, the same sections are in the menu at the top left, and a project opens on the chat, with its progress above it. Create a project, open a chat inside it, and you're ready to work.

For a full explanation of each concept — including workspaces, agents, skills, recipes, and MCP connections — see Platform Concepts.

---

Step 5 — Start working with agents

From a chat inside a project, interact with agents by typing naturally. Each recipe has a designated starting point that invokes the recipe's orchestrator and kicks off the workflow.

The orchestrator will:

1. Check that your workspace is correctly configured
2. Ask for any missing configuration
3. Begin the first phase of the workflow
4. Guide you through each step, asking for your approval before any meaningful action

You don't need to know which sub-agents are involved or what tools they're calling. The orchestrator manages that. Your job is to review what it produces and decide when to proceed.

You can also start any task straight from the task list or board with its Start button.

---

What's next