Getting Started

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

If you haven't read the Overview yet, start there — it covers the core concepts (workspaces, agents, skills, and recipes) that this guide builds on.

---

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. Organization management, team members, and user roles continue to be managed from the Classic interface.

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

From the Agentic dashboard, select New Workspace. You'll be prompted to choose how to create it:

Start from a recipe (recommended)

Recipes are pre-configured workspace templates for specific use cases. Choosing a recipe automatically provisions:

• The full agent team for that workflow
• All required MCP connections
• Agent skills and system instructions
• Human-in-the-loop tool settings
• A setup wizard to connect your environments

For most teams, starting from a recipe is the right choice. It removes the need to manually configure agents, tools, and connections — everything is ready to go once you've completed the setup wizard.

Available recipes:

Start from scratch

If you have a custom workflow that no recipe covers, you can build a workspace manually:

1. Create a workspace with a name and description
2. Add MCP connections to the external systems your agents need
3. Create agents, assign them roles, connect them to the relevant tools, and load skills
4. Configure human-in-the-loop behavior per tool
5. Add prompt templates for common tasks

Start-from-scratch workspaces are fully supported and can be as simple or as sophisticated as your use case requires. You can also use an existing recipe workspace as a reference point.

---

Step 3 — Connect your environments

When you create a workspace from a recipe, the setup wizard will prompt you to connect the external systems that recipe needs. For the XP → SitecoreAI CMS (XMC) migration recipe, these are:

For full environment setup instructions specific to this recipe, see Environment Setup.

📘

You don't need all environments fully ready before creating a workspace. You can create the workspace, explore the agent configuration, and return to connect environments when they're ready.

---

Step 4 — Explore your workspace

Once your workspace is created, you'll see three main areas:

Agents

A list of all agents provisioned for this workspace. Each agent has:

• System instructions — what the agent knows and how it behaves
• MCP connections — which tools it has access to
• Skills — the curated knowledge packages it draws from
• LLM setting — which model it uses, provisioned through Azure AI Foundry
• Tool permissions — per-tool human-in-the-loop settings (auto-approve or approval required)
• Prompt templates — reusable prompts you can invoke from the chat window

You don't need to configure any of this if you started from a recipe — it's all pre-configured. You can review, adjust, or extend it at any time.

Connections

All MCP connections registered in this workspace. Each connection exposes a set of tools that agents can use. You can add custom connections here — for example, an Atlassian MCP server to link Jira tickets to migration work, or any other remote MCP server your workflow requires.

Projects

Projects are the working areas inside a workspace. A workspace can have multiple projects — for example, one per client site or one per migration engagement. Each project contains its own chat sessions where you interact with agents directly.

To start working, create a new project inside your workspace, then open a chat session within that project.

⚠️

Do not run two code migration chat sessions in parallel within the same project. Code migration sessions share the same sandbox — running them concurrently can cause conflicts. You can however run a code migration session and a content migration session in parallel, as they operate on independent systems.

---

Step 5 — Start working with agents

From a project chat session, you interact with agents by typing naturally. Each recipe has a designated starting point — for the XP → SitecoreAI CMS (XMC) migration, you start by invoking the Discovery Orchestrator from a chat session inside your project.

The agent will:

1. Check that your workspace is configured correctly
2. Verify or ask for existing configuration
3. Kick off parallel discovery across your code and content
4. Produce a full discovery report as the foundation for all downstream phases

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.

For the full phase-by-phase workflow for the XP → SitecoreAI CMS (XMC) migration, see Phase 1 — Discovery.

---

Workspace tips

Sessions are resumable. Every phase saves its progress as artifacts in your workspace. If a session gets long, open a new chat session within the same project and continue — the agents will pick up from the last saved state.

You can customize any recipe workspace. Add agents, swap skills, adjust tool permissions, or connect additional MCP servers at any time. Recipes are a starting point, not a constraint.

Human-in-the-loop is configurable per tool. By default, high-impact tools require your approval before executing. Routine read operations are typically set to auto-approve. You can adjust any tool's setting in the agent configuration panel.

Multiple workspaces and projects are supported. Create one workspace per use case, and one project per engagement or client site. Workspaces are isolated — agents, connections, and sessions in one workspace don't affect another.

---

What's next