From 09d2710a34594bc53076eaa05210eba9dca32e08 Mon Sep 17 00:00:00 2001
From: Britannio Jarrett <33752528+britannio@users.noreply.github.com>
Date: Tue, 16 Sep 2025 20:46:57 +0000
Subject: [PATCH] Update all documentation (#718)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
* add AGENTS/CLAUDE.md file to docs/
* collapse supported coding agents (vibe-kanban 52fd2ae6)
docs/AGENTS.md
docs/docs.json
We have a section in the docs denoted 'Supported Coding Agents' but we don't need a separate sub page for each one, we can combine it into a single page.
* docs multiple dev servers (vibe-kanban 3e3a6195)
"At the moment only one dev server can be running for each project, so if you start one it will kill any that are already running."
This sentence in the docs is no longer true and should be removed
* docs update: reviewing code changes (vibe-kanban e3b5db87)
docs/AGENTS.md
docs/docs.json
Introduce a new page in the user guide that covers code review. After a task has completed, it will enter the 'in review' column. From there, the user can open the task in full screen and press on the 'Diff' tab to see each changed file in split or unified view. We also support attaching a review comment to a line by clicking on the plus icon at the start of the line. You can create several comments across files and even extend the review with general comments in the task chat field before submitting the review. It is turned into a single message for the coding agent to address.
* Document VS Code Extension Features (vibe-kanban e88b4bb9)
Create a comprehensive user guide page documenting the VS Code extension integration. It works with VSCode and forks of VSCode such as Cursor, Windsurf.
The IDE extension embeds the Logs, Diffs. and Processes view for a current task. It also has a text box to create new task attempts. After installing the extension, the easiest way to use it is by starting a task, opening it, in full screen mode, then pressing the 'Open in (VSCode/Cursor/Windsurf)' button. For troubleshooting, if you open your IDE but not in one of the worktrees created by a vibe kanban task, the extension UI will be empty because it won't find the associated task.
VSCode install link: https://marketplace.visualstudio.com/items?itemName=bloop.vibe-kanban
Cursor/Windsurf: https://open-vsx.org/extension/bloop/vibe-kanban
Id: bloop.vibe-kanban, users can search @id:bloop.vibe-kanban in any of the IDEs to find the extension. It's easiest to search the id if using Cursor/Windsurf as deeplinking from open vsx doesn't work.
* remove /docs prefix from internal links
* hackathon docs banner (vibe-kanban ce53b989)
# Banner
> Add a banner to display important site-wide announcements and notifications
Use banners to display important announcements, updates, or notifications across your entire documentation site. Banners appear at the top of every page, support Markdown formatting, and can be made dismissible.
To add a banner, use the `banner` property in your `docs.json`:
```json Product announcements wrap
"banner": {
"content": "🚀 Version 2.0 is now live! See our [changelog](/changelog) for details.",
"dismissible": true
}
```
```json Maintenance notices wrap
"banner": {
"content": "⚠️ Scheduled maintenance: API will be unavailable December 15, 2-4 AM UTC",
"dismissible": false
}
```
```json Required actions wrap
"banner": {
"content": "**Action required:** Migrate to our new version by January 1. [Migration guide](/migration)",
"dismissible": true
}
```
## Properties
The banner message. Supports plain text and Markdown formatting.
Whether users can dismiss the banner. When `true`, users can close the banner and it won't reappear for their session. Defaults to `false`.
We are hosting a hackathon in London on the 20th of September, so create a site-wide banner advertising this.
* update mcp server docs (vibe-kanban 94754ae1)
Update the documentation on the MCP server.
We have an existing page describing how it works, but it needs a bit of clarification because MCP support comes in two forms for us. Firstly, you can configure the MCP servers accessible to the coding agents you use within our product. And secondly, our product itself exposes an MCP server for other MCP clients to connect to, such as Claude Desktop, Raycast, or a coding agent that you're using either within Vive Kanban or outside Vive Kanban.
Our MCP server is a local MCP server as opposed to a remote MCP server and this means you can connect to it through apps that you've installed on your computer but you can't connect to clients that expect a publicly accessible URL.
The vibe-kanban-mcp-server docs page is exclusively focused on the MCP server that we expose but we should clarify this for users. This means we'll need a new page that focuses on the MCP Server configuration page that we have inside the app. And this is the page that lets users choose the MCP servers connected to each of the coding agents supported within Vibe Kanban. We also have a one-click installation feature for popular servers. such as, these are Context7 and Playwright.
# Update Media
Replace the main screenshot with /Users/britannio/Downloads/vk-mcp-server-config.jpeg by copying it into the project. This screenshot is taken from the MCP server's settings page and it's useful to show how we can add the Vibe Kanban MCP server to a coding agent that we're using within Vibe Kanban. We will also use this screenshot on the new page we're creating to show MCP server configuration, just to convey that you can bring your own MCP server or use one of our one-click installation popular servers for your coding agents.
/Users/britannio/Downloads/vk-raycast-mcp-part-2.png /Users/britannio/Downloads/vk-raycast-mcp-part-1.png
These screenshots are screenshots of the macOS Raycast app and they show you how you can configure the MCP server with it. Raycast is a popular MCP client just like Claude Desktop but many others are supported too.
* docs: creating task attempts - mintlify rules (vibe-kanban 2b54caea)
docs/user-guide/creating-task-attempts.mdx
Apply the Mintlify technical writing rules to this page.
* use british english in mintlify technical writing rule
* docs: agent configurations - mintlify rules (vibe-kanban 8e7d82ec)
docs/user-guide/agent-configurations.mdx
Apply the Mintlify technical writing rules to this page
* docs: creating projects (vibe-kanban 95cd181a)
docs/user-guide/creating-projects.mdx
Copy /Users/britannio/Downloads/vk-create-project.jpeg and use it as the screenshot
When the Create Project button is pressed, you have two options, either to create from an existing git repository or to create from a blank project. If you choose the former, then we will search your file system and show you a sorted list of git repositories that we find where the top project is the one that was most recently active.
In project settings, we not only let you control setup scripts, dev server scripts, and cleanup scripts, but we also let you specify a comma separated list of 'copy files'. And these are files like environment variables or other data that isn't tracked by git that you want to be present in the work tree created by every new task. Put this 'Copy Files' section above cleanup scripts.
How the codebase describes copy files: "Comma-separated list of files to copy from the original project directory to the worktree. These files will be copied after the worktree is created but before the setup script runs. Useful for environment-specific files like .env, configuration files, and local settings. Make sure these are gitignored or they could get committed!"
Since this page was created, we've changed the setup flow. So instead of configuring project settings during project creation, it's done afterwards. So once a user has created a project, they need to explicitly press the settings button in the top right to configure these scripts. As a result of this, it would be sensible to move all of the sections on project settings (git, setup scripts, etc) into a heading titled project settings.
From these project settings, you can also configure project task templates and we have more details about this in a subsection of a different page here: /user-guide/creating-task-templates#project-task-templates
* docs: getting started - minitlify (vibe-kanban 37318053)
{
"group": "Getting started",
"pages": ["index", "getting-started", "onboarding", "global-settings"]
},
Apply the Mintlify technical writing rules to these pages.
Additionally:
```
---
title: ""
description: ""
sidebarTitle: ""
---
```
These docs pages should have a title and description by including this block at the very top of the mdx file.
If the `title` attribute is equivalent to the first header, the header is redundant and can be removed.
sidebarTitle is optional and can be used if the main title os too verbose. The sidebar title should typically be two to three words.
* update creating projects text
* docs: creating tasks - mintlify (vibe-kanban a274f135)
docs/user-guide/creating-tasks.mdx
Apply the Mintlify technical writing rules to this page
* docs: creating task templates - mintlify (vibe-kanban 90f075a7)
docs/user-guide/creating-task-templates.mdx
Apply the Mintlify technical writing rules to this page
* update page title
* docs: keyboard shortcuts (vibe-kanban 8f39c2d0)
use the oracle to explore the codebase and learn how this feature works
add a new docs page covering each shortcut of significance (e.g. esc isn't significant)
* docs: task full screen mode (vibe-kanban a7e097dc)
Task details full screen mode: dev server, rebase, merge, subtask, new attempt, logs, diffs, processes.
Create a new docs page for this full scree mode explaining everything that can be done. Link to other docs for depth on each feature where appropriate.
use the oracle to explore the codebase and learn how this feature works
* docs: github features (vibe-kanban 29aa8f79)
add a docs page describing the features enabled by connecting to Github. Determine which screenshots will be needed and use placeholders for them until I give them to you.
use the oracle to explore the codebase and learn how this feature works
* docs: subtasks (vibe-kanban e038c1ad)
create a docs page for the subtask feature. Leave placeholders for screenshots: we need one for the full screen task view where you can see the button, one for viewing a task with subtasks, and one for viewing a subtask in full screen where it shows its parent task.
use the oracle to explore the codebase and learn how this feature works
* update subtask title
* docs: task templates (vibe-kanban 690b1933)
/Users/britannio/Downloads/vk-task-templates.png
/Users/britannio/Downloads/vk-proj-task-templates.png
Use these updated images in docs/user-guide/creating-task-templates.mdx
* docs: creating tasks screenshots (vibe-kanban 20f70e4f)
docs/user-guide/creating-tasks.mdx
/Users/britannio/Downloads/vk-create-task.png /Users/britannio/Downloads/vk-starting-task-attempt.png /Users/britannio/Downloads/vk-task-template.png
use these as the new screenshots
* docs: onboarding (vibe-kanban 631427c5)
docs/getting-started.mdx
docs/onboarding.mdx
In the documentation, we have an installation page and an onboarding page. But the onboarding page is a bit misleading because what actually happens when you set up the project and run the npx command for the first time is it will open the app and you'll see the projects page. There won't be any projects, so you'll have the chance to create your first project and create your first task. And then if you want to connect to GitHub, you have to manually go to settings and connect that. There isn't actually any encouragement for the user to do any of this. So, review those two pages and review the code base to double check that my understanding of the current onboarding flow is correct. And then update the documentation accordingly. We may not need the onboarding page at all if it's not relevant.
* docs: creating tasks (vibe-kanban 0eb62591)
docs/user-guide/creating-tasks.mdx
We should mention that tasks can be created by a coding agent or by an MCP client such as Claude Desktop or Raycast and then linked to the Vibe Kanban MCP server documentation. This isn't the expected use case for creating tasks but it can be useful for creating tasks in bulk based on existing data that you have or migrating tasks from a different system such as Linear, Github Issues
Conform to the mintlify technical writing rules.
* docs: settings (vibe-kanban 579e1663)
docs/global-settings.mdx
Use this screenshot instaed of screenshot-global-settings.png: /Users/britannio/Downloads/vk-settings.png
Don't change anything else.
* update creating tasks docs (vibe-kanban 140820a6)
docs/user-guide/creating-tasks.mdx
"After creating a project, add tasks by clicking the Add Task button in the navigation section of your project kanban page. Creating a task adds it to your kanban board without automatically starting a coding agent."
The button isn't an 'add task' button, it's a plus icon in the top right. You can also use the shortcut `c`.
* docs: creating task attempts (vibe-kanban fb8c5ad4)
docs/user-guide/creating-task-attempts.mdx
Review what is described in this documentation versus how it actually works in the frontend. For example, the previous documentation about the task attempt toolbar actions doesn't appear to hold anymore because the UI has changed. And the buttons in the image that it refers to are now only visible when viewing a task in full screen. And we have documentation on full screen mode. So that's an opportunity to backlink.
* update docs agents.md file
* Review and Harmonise All Documentation (vibe-kanban 7194a113)
Comprehensive review of all documentation pages to ensure:
- Consistent flow and navigation between pages
- Elimination of unnecessary information duplication
- Proper cross-referencing between related topics
- Consistent terminology and style
- Logical information architecture
- Updated navigation and table of contents
- Ensure docs conform to the mintlify technical rules, lean towards making smaller tweaks rather than larger rewrites as the content is already in a good state.
Deliverables:
- Updated navigation structure in docs.json
- Revised cross-references between pages
- Consolidated duplicate information
- Style and terminology consistency report
- Updated index and getting started pages to reflect new content
Location: Review all files in `/docs/` directory
* update image (vibe-kanban d0dcf34d)
docs/user-guide/creating-projects.mdx
/Users/britannio/Downloads/vk-create-proj.png
This is the new screenshot to use for the creating projects documentation. Just copy it and delete the old one.
* docs: delete unused images (vibe-kanban b8fdd325)
Find all unused images in the docs folder and remove them.
* remove review report
* move docs around (vibe-kanban 5ca2e108)
In the docs folder, we have a single subfolder called User Guide. But if you read docs.json, you'll see we now have four different sections of the documentation. I think the first section, being Getting Started, doesn't need its own folder, so the docs inside it can remain top level. But for all of the other sections, they should have their own folder named appropriately.
* update mintlify docs
* rename settings
* bring back ccr images (vibe-kanban 82c0f5d7)
Commit 1db2e0113ef491806b5bf1ac870e1b1db22475a2 introduced claude code router images and setup instructions. Bring it back inside docs/supported-coding-agents.mdx including the images.
* docs deadlink (vibe-kanban b033ffaa)
core-features/task-details-full-screen#subtasks the subtasks link in this section is incorrect. Fix it and fix all other broken docs links.
---
crates/executors/default_mcp.json | 2 +-
docs/{ai-tools/cursor.mdx => AGENTS.md} | 97 +++---
docs/CLAUDE.md | 1 +
docs/README.md | 12 +-
docs/ai-tools/claude-code.mdx | 76 -----
docs/ai-tools/windsurf.mdx | 96 ------
docs/api-reference/endpoint/create.mdx | 4 -
docs/api-reference/endpoint/delete.mdx | 4 -
docs/api-reference/endpoint/get.mdx | 4 -
docs/api-reference/endpoint/webhook.mdx | 4 -
docs/api-reference/introduction.mdx | 33 --
docs/api-reference/openapi.json | 217 ------------
.../agent-configurations.mdx | 215 ++++++++++++
.../creating-task-templates.mdx | 68 ++++
.../global-settings.mdx | 70 ++++
.../keyboard-shortcuts.mdx | 58 ++++
docs/core-features/creating-projects.mdx | 57 ++++
docs/core-features/creating-task-attempts.mdx | 78 +++++
docs/core-features/creating-tasks.mdx | 114 +++++++
docs/core-features/reviewing-code-changes.mdx | 100 ++++++
docs/core-features/subtasks.mdx | 128 +++++++
.../task-details-full-screen.mdx | 135 ++++++++
docs/development.mdx | 94 ------
docs/docs.json | 44 ++-
docs/essentials/code.mdx | 35 --
docs/essentials/images.mdx | 59 ----
docs/essentials/markdown.mdx | 88 -----
docs/essentials/navigation.mdx | 87 -----
docs/essentials/reusable-snippets.mdx | 110 ------
docs/essentials/settings.mdx | 318 ------------------
docs/getting-started.mdx | 63 +++-
docs/global-settings.mdx | 51 ---
docs/images/add-line-comment.png | Bin 0 -> 52229 bytes
docs/images/checks-passed.png | Bin 160724 -> 0 bytes
docs/images/github-connect-settings.png | Bin 0 -> 50266 bytes
docs/images/github-device-code.png | Bin 0 -> 83911 bytes
docs/images/hero-dark.png | Bin 110614 -> 0 bytes
docs/images/hero-light.png | Bin 104264 -> 0 bytes
docs/images/screenshot-agent-running-full.png | Bin 2380965 -> 0 bytes
docs/images/screenshot-agent-running.png | Bin 1865883 -> 0 bytes
docs/images/screenshot-create-project.png | Bin 1097868 -> 0 bytes
.../screenshot-create-subtask-button.png | Bin 0 -> 69509 bytes
.../images/screenshot-create-task-attempt.png | Bin 1576695 -> 297471 bytes
...reenshot-create-task-template-dropdown.png | Bin 311021 -> 448707 bytes
docs/images/screenshot-create-task.png | Bin 1746473 -> 329841 bytes
docs/images/screenshot-file-dropdown.png | Bin 121616 -> 0 bytes
docs/images/screenshot-global-settings.png | Bin 373965 -> 0 bytes
.../screenshot-global-task-templates.png | Bin 449574 -> 422824 bytes
docs/images/screenshot-mcp-servers.png | Bin 352562 -> 0 bytes
docs/images/screenshot-onboarding.png | Bin 333291 -> 0 bytes
docs/images/screenshot-overview-confetti.png | Bin 1497084 -> 0 bytes
.../screenshot-project-task-templates.png | Bin 246946 -> 281624 bytes
.../screenshot-setup-script-running.png | Bin 1856440 -> 0 bytes
.../images/screenshot-subtask-parent-info.png | Bin 0 -> 437946 bytes
.../screenshot-task-attempt-toolbar.png | Bin 83770 -> 0 bytes
docs/images/screenshot-task-with-subtasks.png | Bin 0 -> 791735 bytes
docs/images/task-attempt-push-button.png | Bin 0 -> 74335 bytes
docs/images/vibe-kanban-logo.svg | 294 ----------------
docs/images/vk-create-pr.png | Bin 0 -> 903768 bytes
docs/images/vk-create-project.png | Bin 0 -> 116572 bytes
docs/images/vk-diffs.png | Bin 0 -> 414052 bytes
docs/images/vk-logs.png | Bin 0 -> 364359 bytes
docs/images/vk-mcp-server-config.jpeg | Bin 0 -> 357252 bytes
docs/images/vk-popular-mcp-servers.png | Bin 0 -> 89255 bytes
docs/images/vk-processes.png | Bin 0 -> 230791 bytes
docs/images/vk-raycast-mcp-part-1.png | Bin 0 -> 629648 bytes
docs/images/vk-raycast-mcp-part-2.png | Bin 0 -> 556045 bytes
docs/images/vk-settings.png | Bin 0 -> 353819 bytes
docs/images/vk-task-detail.jpeg | Bin 0 -> 659876 bytes
docs/index.mdx | 19 +-
docs/integrations/github-integration.mdx | 86 +++++
.../integrations/mcp-server-configuration.mdx | 89 +++++
docs/integrations/vibe-kanban-mcp-server.mdx | 115 +++++++
docs/integrations/vscode-extension.mdx | 163 +++++++++
docs/onboarding.mdx | 11 -
docs/quickstart.mdx | 80 -----
docs/snippets/snippet-intro.mdx | 4 -
docs/supported-coding-agents.mdx | 186 +++++++++-
docs/supported-coding-agents/amp.mdx | 9 -
docs/supported-coding-agents/ccr.mdx | 93 -----
docs/supported-coding-agents/claude-code.mdx | 9 -
docs/supported-coding-agents/codex.mdx | 9 -
docs/supported-coding-agents/cursor-cli.mdx | 9 -
docs/supported-coding-agents/gemini-cli.mdx | 9 -
docs/supported-coding-agents/qwen-code.mdx | 9 -
docs/supported-coding-agents/sst-opencode.mdx | 9 -
docs/user-guide/agent-configurations.mdx | 102 ------
docs/user-guide/creating-projects.mdx | 31 --
docs/user-guide/creating-task-attempts.mdx | 40 ---
docs/user-guide/creating-task-templates.mdx | 23 --
docs/user-guide/creating-tasks.mdx | 33 --
docs/user-guide/vibe-kanban-mcp-server.mdx | 53 ---
92 files changed, 1779 insertions(+), 2228 deletions(-)
rename docs/{ai-tools/cursor.mdx => AGENTS.md} (84%)
create mode 120000 docs/CLAUDE.md
delete mode 100644 docs/ai-tools/claude-code.mdx
delete mode 100644 docs/ai-tools/windsurf.mdx
delete mode 100644 docs/api-reference/endpoint/create.mdx
delete mode 100644 docs/api-reference/endpoint/delete.mdx
delete mode 100644 docs/api-reference/endpoint/get.mdx
delete mode 100644 docs/api-reference/endpoint/webhook.mdx
delete mode 100644 docs/api-reference/introduction.mdx
delete mode 100644 docs/api-reference/openapi.json
create mode 100644 docs/configuration-customisation/agent-configurations.mdx
create mode 100644 docs/configuration-customisation/creating-task-templates.mdx
create mode 100644 docs/configuration-customisation/global-settings.mdx
create mode 100644 docs/configuration-customisation/keyboard-shortcuts.mdx
create mode 100644 docs/core-features/creating-projects.mdx
create mode 100644 docs/core-features/creating-task-attempts.mdx
create mode 100644 docs/core-features/creating-tasks.mdx
create mode 100644 docs/core-features/reviewing-code-changes.mdx
create mode 100644 docs/core-features/subtasks.mdx
create mode 100644 docs/core-features/task-details-full-screen.mdx
delete mode 100644 docs/development.mdx
delete mode 100644 docs/essentials/code.mdx
delete mode 100644 docs/essentials/images.mdx
delete mode 100644 docs/essentials/markdown.mdx
delete mode 100644 docs/essentials/navigation.mdx
delete mode 100644 docs/essentials/reusable-snippets.mdx
delete mode 100644 docs/essentials/settings.mdx
delete mode 100644 docs/global-settings.mdx
create mode 100644 docs/images/add-line-comment.png
delete mode 100644 docs/images/checks-passed.png
create mode 100644 docs/images/github-connect-settings.png
create mode 100644 docs/images/github-device-code.png
delete mode 100644 docs/images/hero-dark.png
delete mode 100644 docs/images/hero-light.png
delete mode 100644 docs/images/screenshot-agent-running-full.png
delete mode 100644 docs/images/screenshot-agent-running.png
delete mode 100644 docs/images/screenshot-create-project.png
create mode 100644 docs/images/screenshot-create-subtask-button.png
delete mode 100644 docs/images/screenshot-file-dropdown.png
delete mode 100644 docs/images/screenshot-global-settings.png
delete mode 100644 docs/images/screenshot-mcp-servers.png
delete mode 100644 docs/images/screenshot-onboarding.png
delete mode 100644 docs/images/screenshot-overview-confetti.png
delete mode 100644 docs/images/screenshot-setup-script-running.png
create mode 100644 docs/images/screenshot-subtask-parent-info.png
delete mode 100644 docs/images/screenshot-task-attempt-toolbar.png
create mode 100644 docs/images/screenshot-task-with-subtasks.png
create mode 100644 docs/images/task-attempt-push-button.png
delete mode 100644 docs/images/vibe-kanban-logo.svg
create mode 100644 docs/images/vk-create-pr.png
create mode 100644 docs/images/vk-create-project.png
create mode 100644 docs/images/vk-diffs.png
create mode 100644 docs/images/vk-logs.png
create mode 100644 docs/images/vk-mcp-server-config.jpeg
create mode 100644 docs/images/vk-popular-mcp-servers.png
create mode 100644 docs/images/vk-processes.png
create mode 100644 docs/images/vk-raycast-mcp-part-1.png
create mode 100644 docs/images/vk-raycast-mcp-part-2.png
create mode 100644 docs/images/vk-settings.png
create mode 100644 docs/images/vk-task-detail.jpeg
create mode 100644 docs/integrations/github-integration.mdx
create mode 100644 docs/integrations/mcp-server-configuration.mdx
create mode 100644 docs/integrations/vibe-kanban-mcp-server.mdx
create mode 100644 docs/integrations/vscode-extension.mdx
delete mode 100644 docs/onboarding.mdx
delete mode 100644 docs/quickstart.mdx
delete mode 100644 docs/snippets/snippet-intro.mdx
delete mode 100644 docs/supported-coding-agents/amp.mdx
delete mode 100644 docs/supported-coding-agents/ccr.mdx
delete mode 100644 docs/supported-coding-agents/claude-code.mdx
delete mode 100644 docs/supported-coding-agents/codex.mdx
delete mode 100644 docs/supported-coding-agents/cursor-cli.mdx
delete mode 100644 docs/supported-coding-agents/gemini-cli.mdx
delete mode 100644 docs/supported-coding-agents/qwen-code.mdx
delete mode 100644 docs/supported-coding-agents/sst-opencode.mdx
delete mode 100644 docs/user-guide/agent-configurations.mdx
delete mode 100644 docs/user-guide/creating-projects.mdx
delete mode 100644 docs/user-guide/creating-task-attempts.mdx
delete mode 100644 docs/user-guide/creating-task-templates.mdx
delete mode 100644 docs/user-guide/creating-tasks.mdx
delete mode 100644 docs/user-guide/vibe-kanban-mcp-server.mdx
diff --git a/crates/executors/default_mcp.json b/crates/executors/default_mcp.json
index cedf445f..8a0d1e32 100644
--- a/crates/executors/default_mcp.json
+++ b/crates/executors/default_mcp.json
@@ -24,7 +24,7 @@
"vibe_kanban": {
"name": "Vibe Kanban",
"description": "Create, update and delete Vibe Kanban tasks",
- "url": "https://www.vibekanban.com/docs/user-guide/vibe-kanban-mcp-server",
+ "url": "https://www.vibekanban.com/docs/integrations/vibe-kanban-mcp-server",
"icon": "viba-kanban-favicon.png"
},
"context7": {
diff --git a/docs/ai-tools/cursor.mdx b/docs/AGENTS.md
similarity index 84%
rename from docs/ai-tools/cursor.mdx
rename to docs/AGENTS.md
index fbb77616..cc3f9bf6 100644
--- a/docs/ai-tools/cursor.mdx
+++ b/docs/AGENTS.md
@@ -1,30 +1,16 @@
----
-title: "Cursor setup"
-description: "Configure Cursor for your documentation workflow"
-icon: "arrow-pointer"
----
-
-Use Cursor to help write and maintain your documentation. This guide shows how to configure Cursor for better results on technical writing tasks and using Mintlify components.
-
-## Prerequisites
-
-- Cursor editor installed
-- Access to your documentation repository
-
-## Project rules
-
-Create project rules that all team members can use. In your documentation repository root:
-
-```bash
-mkdir -p .cursor
-```
-
-Create `.cursor/rules.md`:
-
-````markdown
# Mintlify technical writing rule
-You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
+You are an AI writing assistant specialised in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
+
+## Working relationship
+- You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
+- ALWAYS ask for clarification rather than making assumptions
+- NEVER lie, guess, or make up information
+
+## Project context
+- Format: MDX files with YAML frontmatter
+- Config: docs.json for navigation, theme, settings
+- Components: Mintlify components
## Core writing principles
@@ -36,10 +22,11 @@ You are an AI writing assistant specialized in creating exceptional technical do
- Employ present tense for current states, future tense for outcomes
- Avoid jargon unless necessary and define terms when first used
- Maintain consistent terminology throughout all documentation
-- Keep sentences concise while providing necessary context
+- Keep sentences concise whilst providing necessary context
- Use parallel structure in lists, headings, and procedures
+- Use British English spelling and grammar
-### Content organization standards
+### Content organisation standards
- Lead with the most important information (inverted pyramid structure)
- Use progressive disclosure: basic concepts before advanced ones
@@ -48,8 +35,11 @@ You are an AI writing assistant specialized in creating exceptional technical do
- Provide expected outcomes for each major step
- Use descriptive, keyword-rich headings for navigation and SEO
- Group related information logically with clear section breaks
+- Make content evergreen when possible
+- Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason
+- Check existing patterns for consistency
-### User-centered approach
+### User-centred approach
- Focus on user goals and outcomes rather than system features
- Anticipate common questions and address them proactively
@@ -57,8 +47,22 @@ You are an AI writing assistant specialized in creating exceptional technical do
- Write for scannability with clear headings, lists, and white space
- Include verification steps to confirm success
+### Frontmatter requirements for pages
+- title: Clear, descriptive page title
+- description: Concise summary for SEO/navigation
+
+### Do not
+- Skip frontmatter on any MDX file
+- Use absolute URLs for internal links
+- Include untested code examples
+- Make assumptions - always ask for clarification
+
## Mintlify component reference
+### docs.json
+
+- Refer to the [docs.json schema](https://mintlify.com/docs.json) when building the docs.json file and site navigation
+
### Callout components
#### Note - Additional helpful information
@@ -102,7 +106,7 @@ const apiConfig = {
baseURL: 'https://api.example.com',
timeout: 5000,
headers: {
- 'Authorization': `Bearer ${process.env.API_TOKEN}`
+ 'Authorisation': `Bearer ${process.env.API_TOKEN}`
}
};
```
@@ -114,19 +118,19 @@ Example of a code group:
```javascript Node.js
const response = await fetch('/api/endpoint', {
- headers: { Authorization: `Bearer ${apiKey}` }
+ headers: { Authorisation: `Bearer ${apiKey}` }
});
```
```python Python
import requests
-response = requests.get('/api/endpoint',
- headers={'Authorization': f'Bearer {api_key}'})
+response = requests.get('/api/endpoint',
+ headers={'Authorisation': f'Bearer {api_key}'})
```
```curl cURL
curl -X GET '/api/endpoint' \
- -H 'Authorization: Bearer YOUR_API_KEY'
+ -H 'Authorisation: Bearer YOUR_API_KEY'
```
@@ -146,7 +150,7 @@ curl -X POST 'https://api.example.com/users' \
```json Success
{
"id": "user_123",
- "name": "John Doe",
+ "name": "John Doe",
"email": "john@example.com",
"created_at": "2024-01-15T10:30:00Z"
}
@@ -162,7 +166,7 @@ Example of step-by-step instructions:
Run `npm install` to install required packages.
-
+
Verify installation by running `npm list`.
@@ -170,11 +174,11 @@ Example of step-by-step instructions:
Create a `.env` file with your API credentials.
-
+
```bash
API_KEY=your_api_key_here
```
-
+
Never commit API keys to version control.
@@ -229,7 +233,7 @@ Example of accordion groups:
-### Cards and columns for emphasizing information
+### Cards and columns for emphasising information
Example of cards and card groups:
@@ -265,7 +269,7 @@ User's email address. Must be valid and unique within the system.
Maximum number of results to return. Range: 1-100.
-
+
Bearer token for API authentication. Format: `Bearer YOUR_API_KEY`
@@ -295,12 +299,12 @@ Complete user object with all associated data.
User profile information including personal details.
-
+
User's first name as entered during registration.
-
+
URL to user's profile picture. Returns null if no avatar is set.
@@ -390,14 +394,6 @@ description: "Concise description explaining page purpose and value"
- Add explanatory comments for complex logic
- Never include real API keys or secrets in code examples
-### API documentation requirements
-
-- Document all parameters including optional ones with clear descriptions
-- Show both success and error response examples with realistic data
-- Include rate limiting information with specific limits
-- Provide authentication examples showing proper format
-- Explain all HTTP status codes and error handling
-- Cover complete request/response cycles
### Accessibility requirements
@@ -405,7 +401,7 @@ description: "Concise description explaining page purpose and value"
- Use specific, actionable link text instead of "click here"
- Ensure proper heading hierarchy starting with H2
- Provide keyboard navigation considerations
-- Use sufficient color contrast in examples and visuals
+- Use sufficient colour contrast in examples and visuals
- Structure content for easy scanning with headers and lists
## Component selection logic
@@ -417,4 +413,3 @@ description: "Concise description explaining page purpose and value"
- Use **RequestExample/ResponseExample** specifically for API endpoint documentation
- Use **ParamField** for API parameters, **ResponseField** for API responses
- Use **Expandable** for nested object properties or hierarchical information
-````
diff --git a/docs/CLAUDE.md b/docs/CLAUDE.md
new file mode 120000
index 00000000..47dc3e3d
--- /dev/null
+++ b/docs/CLAUDE.md
@@ -0,0 +1 @@
+AGENTS.md
\ No newline at end of file
diff --git a/docs/README.md b/docs/README.md
index 66c5f11f..45c504c9 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -1,16 +1,6 @@
# Mintlify Starter Kit
-Use the starter kit to get your docs deployed and ready to customize.
-
-Click the green **Use this template** button at the top of this repo to copy the Mintlify starter kit. The starter kit contains examples with
-
-- Guide pages
-- Navigation
-- Customizations
-- API reference pages
-- Use of popular components
-
-**[Follow the full quickstart guide](https://starter.mintlify.com/quickstart)**
+**[Mintlify Quickstart Guide](https://starter.mintlify.com/quickstart)**
## Development
diff --git a/docs/ai-tools/claude-code.mdx b/docs/ai-tools/claude-code.mdx
deleted file mode 100644
index bdc4e04b..00000000
--- a/docs/ai-tools/claude-code.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: "Claude Code setup"
-description: "Configure Claude Code for your documentation workflow"
-icon: "asterisk"
----
-
-Claude Code is Anthropic's official CLI tool. This guide will help you set up Claude Code to help you write and maintain your documentation.
-
-## Prerequisites
-
-- Active Claude subscription (Pro, Max, or API access)
-
-## Setup
-
-1. Install Claude Code globally:
-
- ```bash
- npm install -g @anthropic-ai/claude-code
-```
-
-2. Navigate to your docs directory.
-3. (Optional) Add the `CLAUDE.md` file below to your project.
-4. Run `claude` to start.
-
-## Create `CLAUDE.md`
-
-Create a `CLAUDE.md` file at the root of your documentation repository to train Claude Code on your specific documentation standards:
-
-````markdown
-# Mintlify documentation
-
-## Working relationship
-- You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
-- ALWAYS ask for clarification rather than making assumptions
-- NEVER lie, guess, or make up information
-
-## Project context
-- Format: MDX files with YAML frontmatter
-- Config: docs.json for navigation, theme, settings
-- Components: Mintlify components
-
-## Content strategy
-- Document just enough for user success - not too much, not too little
-- Prioritize accuracy and usability of information
-- Make content evergreen when possible
-- Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason
-- Check existing patterns for consistency
-- Start by making the smallest reasonable changes
-
-## Frontmatter requirements for pages
-- title: Clear, descriptive page title
-- description: Concise summary for SEO/navigation
-
-## Writing standards
-- Second-person voice ("you")
-- Prerequisites at start of procedural content
-- Test all code examples before publishing
-- Match style and formatting of existing pages
-- Include both basic and advanced use cases
-- Language tags on all code blocks
-- Alt text on all images
-- Relative paths for internal links
-
-## Git workflow
-- NEVER use --no-verify when committing
-- Ask how to handle uncommitted changes before starting
-- Create a new branch when no clear branch exists for changes
-- Commit frequently throughout development
-- NEVER skip or disable pre-commit hooks
-
-## Do not
-- Skip frontmatter on any MDX file
-- Use absolute URLs for internal links
-- Include untested code examples
-- Make assumptions - always ask for clarification
-````
diff --git a/docs/ai-tools/windsurf.mdx b/docs/ai-tools/windsurf.mdx
deleted file mode 100644
index fce12bfd..00000000
--- a/docs/ai-tools/windsurf.mdx
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: "Windsurf setup"
-description: "Configure Windsurf for your documentation workflow"
-icon: "water"
----
-
-Configure Windsurf's Cascade AI assistant to help you write and maintain documentation. This guide shows how to set up Windsurf specifically for your Mintlify documentation workflow.
-
-## Prerequisites
-
-- Windsurf editor installed
-- Access to your documentation repository
-
-## Workspace rules
-
-Create workspace rules that provide Windsurf with context about your documentation project and standards.
-
-Create `.windsurf/rules.md` in your project root:
-
-````markdown
-# Mintlify technical writing rule
-
-## Project context
-
-- This is a documentation project on the Mintlify platform
-- We use MDX files with YAML frontmatter
-- Navigation is configured in `docs.json`
-- We follow technical writing best practices
-
-## Writing standards
-
-- Use second person ("you") for instructions
-- Write in active voice and present tense
-- Start procedures with prerequisites
-- Include expected outcomes for major steps
-- Use descriptive, keyword-rich headings
-- Keep sentences concise but informative
-
-## Required page structure
-
-Every page must start with frontmatter:
-
-```yaml
----
-title: "Clear, specific title"
-description: "Concise description for SEO and navigation"
----
-```
-
-## Mintlify components
-
-### Callouts
-
-- `` for helpful supplementary information
-- `` for important cautions and breaking changes
-- `` for best practices and expert advice
-- `` for neutral contextual information
-- `` for success confirmations
-
-### Code examples
-
-- When appropriate, include complete, runnable examples
-- Use `` for multiple language examples
-- Specify language tags on all code blocks
-- Include realistic data, not placeholders
-- Use `` and `` for API docs
-
-### Procedures
-
-- Use `` component for sequential instructions
-- Include verification steps with `` components when relevant
-- Break complex procedures into smaller steps
-
-### Content organization
-
-- Use `` for platform-specific content
-- Use `` for progressive disclosure
-- Use `` and `` for highlighting content
-- Wrap images in `` components with descriptive alt text
-
-## API documentation requirements
-
-- Document all parameters with ``
-- Show response structure with ``
-- Include both success and error examples
-- Use `` for nested object properties
-- Always include authentication examples
-
-## Quality standards
-
-- Test all code examples before publishing
-- Use relative paths for internal links
-- Include alt text for all images
-- Ensure proper heading hierarchy (start with h2)
-- Check existing patterns for consistency
-````
diff --git a/docs/api-reference/endpoint/create.mdx b/docs/api-reference/endpoint/create.mdx
deleted file mode 100644
index 5689f1b6..00000000
--- a/docs/api-reference/endpoint/create.mdx
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: 'Create Plant'
-openapi: 'POST /plants'
----
diff --git a/docs/api-reference/endpoint/delete.mdx b/docs/api-reference/endpoint/delete.mdx
deleted file mode 100644
index 657dfc87..00000000
--- a/docs/api-reference/endpoint/delete.mdx
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: 'Delete Plant'
-openapi: 'DELETE /plants/{id}'
----
diff --git a/docs/api-reference/endpoint/get.mdx b/docs/api-reference/endpoint/get.mdx
deleted file mode 100644
index 56aa09ec..00000000
--- a/docs/api-reference/endpoint/get.mdx
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: 'Get Plants'
-openapi: 'GET /plants'
----
diff --git a/docs/api-reference/endpoint/webhook.mdx b/docs/api-reference/endpoint/webhook.mdx
deleted file mode 100644
index 32913402..00000000
--- a/docs/api-reference/endpoint/webhook.mdx
+++ /dev/null
@@ -1,4 +0,0 @@
----
-title: 'New Plant'
-openapi: 'WEBHOOK /plant/webhook'
----
diff --git a/docs/api-reference/introduction.mdx b/docs/api-reference/introduction.mdx
deleted file mode 100644
index c835b78b..00000000
--- a/docs/api-reference/introduction.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: 'Introduction'
-description: 'Example section for showcasing API endpoints'
----
-
-
- If you're not looking to build API reference documentation, you can delete
- this section by removing the api-reference folder.
-
-
-## Welcome
-
-There are two ways to build API documentation: [OpenAPI](https://mintlify.com/docs/api-playground/openapi/setup) and [MDX components](https://mintlify.com/docs/api-playground/mdx/configuration). For the starter kit, we are using the following OpenAPI specification.
-
-
- View the OpenAPI specification file
-
-
-## Authentication
-
-All API endpoints are authenticated using Bearer tokens and picked up from the specification file.
-
-```json
-"security": [
- {
- "bearerAuth": []
- }
-]
-```
diff --git a/docs/api-reference/openapi.json b/docs/api-reference/openapi.json
deleted file mode 100644
index da5326ef..00000000
--- a/docs/api-reference/openapi.json
+++ /dev/null
@@ -1,217 +0,0 @@
-{
- "openapi": "3.1.0",
- "info": {
- "title": "OpenAPI Plant Store",
- "description": "A sample API that uses a plant store as an example to demonstrate features in the OpenAPI specification",
- "license": {
- "name": "MIT"
- },
- "version": "1.0.0"
- },
- "servers": [
- {
- "url": "http://sandbox.mintlify.com"
- }
- ],
- "security": [
- {
- "bearerAuth": []
- }
- ],
- "paths": {
- "/plants": {
- "get": {
- "description": "Returns all plants from the system that the user has access to",
- "parameters": [
- {
- "name": "limit",
- "in": "query",
- "description": "The maximum number of results to return",
- "schema": {
- "type": "integer",
- "format": "int32"
- }
- }
- ],
- "responses": {
- "200": {
- "description": "Plant response",
- "content": {
- "application/json": {
- "schema": {
- "type": "array",
- "items": {
- "$ref": "#/components/schemas/Plant"
- }
- }
- }
- }
- },
- "400": {
- "description": "Unexpected error",
- "content": {
- "application/json": {
- "schema": {
- "$ref": "#/components/schemas/Error"
- }
- }
- }
- }
- }
- },
- "post": {
- "description": "Creates a new plant in the store",
- "requestBody": {
- "description": "Plant to add to the store",
- "content": {
- "application/json": {
- "schema": {
- "$ref": "#/components/schemas/NewPlant"
- }
- }
- },
- "required": true
- },
- "responses": {
- "200": {
- "description": "plant response",
- "content": {
- "application/json": {
- "schema": {
- "$ref": "#/components/schemas/Plant"
- }
- }
- }
- },
- "400": {
- "description": "unexpected error",
- "content": {
- "application/json": {
- "schema": {
- "$ref": "#/components/schemas/Error"
- }
- }
- }
- }
- }
- }
- },
- "/plants/{id}": {
- "delete": {
- "description": "Deletes a single plant based on the ID supplied",
- "parameters": [
- {
- "name": "id",
- "in": "path",
- "description": "ID of plant to delete",
- "required": true,
- "schema": {
- "type": "integer",
- "format": "int64"
- }
- }
- ],
- "responses": {
- "204": {
- "description": "Plant deleted",
- "content": {}
- },
- "400": {
- "description": "unexpected error",
- "content": {
- "application/json": {
- "schema": {
- "$ref": "#/components/schemas/Error"
- }
- }
- }
- }
- }
- }
- }
- },
- "webhooks": {
- "/plant/webhook": {
- "post": {
- "description": "Information about a new plant added to the store",
- "requestBody": {
- "description": "Plant added to the store",
- "content": {
- "application/json": {
- "schema": {
- "$ref": "#/components/schemas/NewPlant"
- }
- }
- }
- },
- "responses": {
- "200": {
- "description": "Return a 200 status to indicate that the data was received successfully"
- }
- }
- }
- }
- },
- "components": {
- "schemas": {
- "Plant": {
- "required": [
- "name"
- ],
- "type": "object",
- "properties": {
- "name": {
- "description": "The name of the plant",
- "type": "string"
- },
- "tag": {
- "description": "Tag to specify the type",
- "type": "string"
- }
- }
- },
- "NewPlant": {
- "allOf": [
- {
- "$ref": "#/components/schemas/Plant"
- },
- {
- "required": [
- "id"
- ],
- "type": "object",
- "properties": {
- "id": {
- "description": "Identification number of the plant",
- "type": "integer",
- "format": "int64"
- }
- }
- }
- ]
- },
- "Error": {
- "required": [
- "error",
- "message"
- ],
- "type": "object",
- "properties": {
- "error": {
- "type": "integer",
- "format": "int32"
- },
- "message": {
- "type": "string"
- }
- }
- }
- },
- "securitySchemes": {
- "bearerAuth": {
- "type": "http",
- "scheme": "bearer"
- }
- }
- }
-}
\ No newline at end of file
diff --git a/docs/configuration-customisation/agent-configurations.mdx b/docs/configuration-customisation/agent-configurations.mdx
new file mode 100644
index 00000000..6d1ffe17
--- /dev/null
+++ b/docs/configuration-customisation/agent-configurations.mdx
@@ -0,0 +1,215 @@
+---
+title: "Agent Profiles & Configuration"
+description: "Configure and customise coding agent variants with different settings for planning, models, and sandbox permissions"
+---
+
+Agent profiles let you define multiple named variants for each supported coding agent. Variants capture configuration differences like planning mode, model choice, and sandbox permissions that you can quickly select when creating attempts.
+
+
+Agent profiles are used throughout Vibe Kanban wherever agents run: onboarding, default settings, attempt creation, and follow-ups.
+
+
+## Configuration Access
+
+You can configure agent profiles in two ways through Settings → Agents:
+
+
+
+ Use the guided interface with form fields for each agent setting.
+
+
+
+
+
+
+
+ Edit the underlying `profiles.json` file directly for advanced configurations.
+
+
+
+
+
+
+
+
+The configuration page displays the exact file path where your settings are stored. Vibe Kanban saves only your overrides whilst preserving built-in defaults.
+
+
+## Configuration Structure
+
+The profiles configuration uses a JSON structure with an `executors` object containing agent variants:
+
+```json profiles.json
+{
+ "executors": {
+ "CLAUDE_CODE": {
+ "DEFAULT": { "CLAUDE_CODE": { "dangerously_skip_permissions": true } },
+ "PLAN": { "CLAUDE_CODE": { "plan": true } },
+ "ROUTER": { "CLAUDE_CODE": { "claude_code_router": true, "dangerously_skip_permissions": true } }
+ },
+ "GEMINI": {
+ "DEFAULT": { "GEMINI": { "model": "default", "yolo": true } },
+ "FLASH": { "GEMINI": { "model": "flash", "yolo": true } }
+ },
+ "CODEX": {
+ "DEFAULT": { "CODEX": { "sandbox": "danger-full-access" } },
+ "HIGH": { "CODEX": { "sandbox": "danger-full-access", "model_reasoning_effort": "high" } }
+ }
+ }
+}
+```
+
+
+
+ - **Variant names**: Case-insensitive and normalised to SCREAMING_SNAKE_CASE
+ - **DEFAULT variant**: Reserved and always present for each agent
+ - **Custom variants**: Add new variants like `PLAN`, `FLASH`, `HIGH` as needed
+ - **Built-in protection**: Cannot remove built-in executors, but can override values
+
+
+
+ - Your custom settings override built-in defaults
+ - Built-in configurations remain available as fallbacks
+ - Each variant contains a complete configuration object for its agent
+
+
+
+## Agent Configuration Options
+
+
+
+
+ Enable planning mode for complex tasks
+
+
+
+ Route requests across multiple Claude Code instances
+
+
+
+ Skip permission prompts (use with caution)
+
+
+ [View full CLI reference →](https://docs.anthropic.com/en/docs/claude-code/cli-reference#cli-flags)
+
+
+
+
+ Choose model variant: `"default"` or `"flash"`
+
+
+
+ Run without confirmations
+
+
+ [View full CLI reference →](https://google-gemini.github.io/gemini-cli/)
+
+
+
+
+ Allow all actions without restrictions (unsafe)
+
+
+ [View full documentation →](https://ampcode.com/manual#cli)
+
+
+
+
+ Execution environment: `"read-only"`, `"workspace-write"`, or `"danger-full-access"`
+
+
+
+ Approval level: `"untrusted"`, `"on-failure"`, `"on-request"`, or `"never"`
+
+
+
+ Reasoning depth: `"low"`, `"medium"`, or `"high"`
+
+
+
+ Summary style: `"auto"`, `"concise"`, `"detailed"`, or `"none"`
+
+
+ [View full documentation →](https://github.com/openai/codex)
+
+
+
+
+ Force execution without confirmation
+
+
+
+ Specify model to use
+
+
+ [View full CLI reference →](https://docs.cursor.com/en/cli/reference/parameters)
+
+
+
+
+ Specify model to use
+
+
+
+ Choose agent type
+
+
+ [View full documentation →](https://opencode.ai/docs/cli/#flags-1)
+
+
+
+
+ Run without confirmations
+
+
+ [View full documentation →](https://qwenlm.github.io/qwen-code-docs/en/cli/index)
+
+
+
+### Universal Options
+
+These options work across multiple agent types:
+
+
+Text appended to the system prompt
+
+
+
+Override the underlying CLI command
+
+
+
+Additional CLI arguments to pass
+
+
+
+Options prefixed with "dangerously_" bypass safety confirmations and can perform destructive actions. Use with extreme caution.
+
+
+## Using Agent Configurations
+
+
+
+ Set your default agent and variant in **Settings → General → Default Agent Configuration** for consistent behaviour across all attempts.
+
+
+
+ Override defaults when creating attempts by selecting different agent/variant combinations in the attempt dialogue.
+
+
+
+## Related Configuration
+
+
+MCP (Model Context Protocol) servers are configured separately under **Settings → MCP Servers** but work alongside agent profiles to extend functionality.
+
+
+
+
+ Configure MCP servers within Vibe Kanban for your coding agents
+
+
+
+ Connect external MCP clients to Vibe Kanban's MCP server
+
+
diff --git a/docs/configuration-customisation/creating-task-templates.mdx b/docs/configuration-customisation/creating-task-templates.mdx
new file mode 100644
index 00000000..fdd18c5c
--- /dev/null
+++ b/docs/configuration-customisation/creating-task-templates.mdx
@@ -0,0 +1,68 @@
+---
+title: "Creating Task Templates"
+description: "Create reusable task formats that speed up task creation. You can create templates globally (across all projects) or for specific projects."
+---
+
+## Managing global task templates
+
+Access global templates from **Global Settings → Task Templates**. These templates are available across every project in your workspace.
+
+
+
+
+
+
+
+ Click **Add Template** to create a new global template.
+
+
+
+ Use the edit icon (✏️) to modify template content.
+
+
+
+ Click the delete icon (🗑️) to remove templates you no longer need.
+
+
+
+## Managing project task templates
+
+Create templates scoped to individual projects for project-specific workflows.
+
+
+
+
+
+
+
+ 1. Open your project
+ 2. Click the library icon in the project header
+ 3. Select **Manage Templates**
+
+
+
+ Use **Add Template**, **Edit** (✏️), and **Remove** (🗑️) controls to manage project-specific templates.
+
+
+
+## Using templates
+
+Apply templates when creating tasks to prefill content and maintain consistency.
+
+
+
+ When creating a new task, click the **Use a template** dropdown.
+
+
+
+ Select from your global or project-specific templates.
+
+
+ The template automatically prefills the task title and description.
+
+
+
+
+
+Global templates appear in all projects, whilst project templates only appear in their specific project. Use global templates for common task types and project templates for specialised workflows.
+
diff --git a/docs/configuration-customisation/global-settings.mdx b/docs/configuration-customisation/global-settings.mdx
new file mode 100644
index 00000000..d4c11d5b
--- /dev/null
+++ b/docs/configuration-customisation/global-settings.mdx
@@ -0,0 +1,70 @@
+---
+title: "Global Settings"
+description: "Configure application-wide settings including themes, agents, GitHub integration, and more"
+sidebarTitle: "Settings"
+---
+
+You can configure application-wide settings via the **Settings** page. To access it, click the ⚙️ icon in the sidebar or select "Settings" from the top-right menu.
+
+
+
+
+
+## Themes
+
+Switch between light and dark themes to suit your preference.
+
+## Default Agent Configuration
+
+Choose the default agent and variant for new task attempts. This profile is pre-selected when creating new task attempts and follow-ups.
+
+1. **Select an agent** (e.g., Claude Code, Gemini CLI, Codex)
+2. **Choose a variant** if available (e.g., Default, Plan, Router)
+
+
+You can override the default agent configuration per attempt in the create attempt dialog.
+
+
+## Editor Integration
+
+Configure integration with your preferred code editor (e.g., VS Code) for a seamless development workflow.
+
+## GitHub Integration
+
+Link your GitHub account by providing a Personal Access Token (PAT) to enable:
+
+- Automatic branch management
+- Pull request creation and tracking
+- Status synchronisation directly from Vibe Kanban
+
+## Notifications
+
+Toggle sound effects and push notifications to stay informed about task status changes.
+
+## Telemetry
+
+Enable or disable telemetry data collection to help improve Vibe Kanban.
+
+## Task Templates
+
+Manage global task templates to accelerate task creation across all projects. Templates allow you to define reusable titles and descriptions for common tasks.
+
+
+ Complete guide to creating and managing task templates
+
+
+## Agent Settings (Profiles & Variants)
+
+Define and customise agent variants under **Settings → Agents**. Variants let you maintain multiple configurations for the same agent (for example, a Claude Code "PLAN" variant).
+
+
+ Detailed guide with examples for configuring agent variants
+
+
+## Safety & Disclaimers
+
+Manage acknowledgments and reset options for onboarding, safety disclaimers, and telemetry notices.
+
+- **Onboarding**: Reset the onboarding process to rerun the initial setup.
+- **Safety Disclaimer**: Reset or review the safety disclaimer prompt.
+- **Telemetry Notice**: Reset or review the telemetry data collection acknowledgment.
diff --git a/docs/configuration-customisation/keyboard-shortcuts.mdx b/docs/configuration-customisation/keyboard-shortcuts.mdx
new file mode 100644
index 00000000..f54fbaed
--- /dev/null
+++ b/docs/configuration-customisation/keyboard-shortcuts.mdx
@@ -0,0 +1,58 @@
+---
+title: "Keyboard Shortcuts"
+description: "Complete guide to keyboard shortcuts for efficient navigation and interaction in Vibe Kanban"
+---
+
+Vibe Kanban provides comprehensive keyboard shortcuts to help you navigate and interact with the application efficiently. These shortcuts are organised by scope and context.
+
+## Platform Keys
+
+- **⌘** = Mac Command key
+- **Ctrl** = Windows/Linux Control key
+
+## Global Shortcuts
+
+These shortcuts work anywhere in the application (unless you're typing in an input field):
+
+| Shortcut | Action | Description |
+|----------|--------|-------------|
+| `C` | Create Task | Opens the Task Form dialog to create a new task |
+| `⌘/Ctrl + S` | Focus Search | Puts keyboard focus into the global search input |
+
+## Board Navigation
+
+These shortcuts work when a task card is highlighted with the blue focus ring:
+
+| Shortcut | Action | Description |
+|----------|--------|-------------|
+| `↑` / `↓` | Vertical Navigation | Move focus to previous/next task in the current column |
+| `←` / `→` | Horizontal Navigation | Move focus to first task in previous/next non-empty column |
+| `Enter` / `Space` | Open Task | Open the Task Details panel for the focused task |
+| `Backspace` | Delete Task | Delete the currently focused task |
+
+## Form Submission
+
+These shortcuts work in various forms and dialogs:
+
+| Shortcut | Action | Context |
+|----------|--------|---------|
+| `⌘/Ctrl + Enter` | Submit | Create & Start (Task Form), Save (Template Editor) |
+| `⌘/Ctrl + Enter` | Send | Send follow-up message in Task Details |
+| `⌘/Ctrl + Enter` | Save Comment | Add or save comment in Diff Review |
+| `Escape` | Cancel/Clear | Clear draft in follow-up, cancel comment editing |
+
+## Search
+
+| Shortcut | Action | Description |
+|----------|--------|-------------|
+| `⌘/Ctrl + S` | Focus Search | Move cursor to the search input field |
+| `Escape` | Clear Search | Clear search text and remove focus (when in search field) |
+
+*Note: The search field displays a "⌘S" badge to help you discover this shortcut.*
+
+## Tips
+
+- **Focus Indicators**: Look for blue focus rings around task cards to know when board navigation shortcuts are active
+- **Input Fields**: Global shortcuts are disabled when typing in text fields to avoid conflicts
+- **Visual Cues**: Some shortcuts display badges or hints in the interface (like the "⌘S" next to search)
+- **Modifier Keys**: Global shortcuts are disabled when holding Ctrl/⌘/Alt unless the shortcut specifically uses those modifiers
diff --git a/docs/core-features/creating-projects.mdx b/docs/core-features/creating-projects.mdx
new file mode 100644
index 00000000..38c26bcc
--- /dev/null
+++ b/docs/core-features/creating-projects.mdx
@@ -0,0 +1,57 @@
+---
+title: "Creating Projects"
+description: "Learn how to create and configure projects in Vibe Kanban"
+---
+
+Before you can create tasks and execute coding agents, you must create a project.
+
+
+
+
+
+## Creating Your Project
+Click the **Create Project** button to choose from two options:
+- **From existing git repository**: Browse your file system and select from a list of git repositories sorted by recent activity
+- **Create blank project**: Generate a new git repository from scratch
+Each project represents a git repository. After creation, you can configure it with setup scripts, dev server scripts, and other settings.
+
+
+
+After creating a project, you need to press the settings button in the top right to configure project scripts and settings.
+
+
+## Project Settings
+
+Once you've created a project, you can access the project settings by clicking the settings button in the top right corner. From here, you can configure various aspects of your project.
+
+### Setup Scripts
+
+Setup scripts will be run before the coding agent is executed. This is useful for installing dependencies, for example you might run `npm install` or `cargo build`. This will save you time as your agent won't need to figure out that these commands haven't already been run.
+
+
+Each time a coding agent is executed it runs in a [git worktree](https://git-scm.com/docs/git-worktree) which is unlikely to contain your dependencies, configs, .env etc.
+
+
+### Dev Server Scripts
+
+The dev server script is run whenever you press the "run dev server" button. It's useful for quickly reviewing work after a coding agent has run.
+
+### Copy Files
+
+Comma-separated list of files to copy from the original project directory to the worktree. These files will be copied after the worktree is created but before the setup script runs. Useful for environment-specific files like `.env`, configuration files, and local settings.
+
+
+Make sure these files are gitignored or they could get committed!
+
+
+### Project Task Templates
+
+From project settings, you can also configure project-specific task templates. For more details about this feature, see the [project task templates section](/configuration-customisation/creating-task-templates#project-task-templates).
+
+### Cleanup Scripts
+
+Cleanup scripts run after a coding agent finishes. You can use these to tidy up the workspace, remove temporary files, or perform any post-execution cleanup. For example, you might run:
+
+```bash
+npm run clean
+```
diff --git a/docs/core-features/creating-task-attempts.mdx b/docs/core-features/creating-task-attempts.mdx
new file mode 100644
index 00000000..561d0611
--- /dev/null
+++ b/docs/core-features/creating-task-attempts.mdx
@@ -0,0 +1,78 @@
+---
+title: "Creating Task Attempts"
+description: "Understand when and why to create multiple task attempts for fresh restarts with different configurations."
+sidebarTitle: "Creating Task Attempts"
+---
+
+A task attempt represents a single execution of a coding agent against a task. Most tasks only need one attempt, but you may need additional attempts for fresh restarts.
+
+## When to Create New Task Attempts
+
+Create a new task attempt when you want to:
+
+- **Start from scratch** with a different approach after an unsuccessful attempt
+- **Try a different coding agent** (e.g., switching from Claude to Codex)
+- **Use a different agent profile or variant** for specialised behaviour
+- **Work from a different base branch** to incorporate recent changes
+- **Reset the conversation context** for a completely fresh start
+
+
+Most users will only need one attempt per task. Only create additional attempts if the first approach didn't work as expected.
+
+
+## Creating Additional Attempts
+
+To create a new task attempt for an existing task:
+
+
+
+ Open the task that needs a fresh attempt.
+
+
+
+ In the task interface, click the **New Attempt** button.
+
+
+
+ Choose your agent profile, variant, and base branch. These can be different from previous attempts.
+
+
+
+ Click **Create Attempt** to begin a fresh execution with the new configuration.
+
+
+
+## Impact on Subtasks
+
+
+Creating new task attempts affects subtasks. Subtasks are linked to specific task attempts, not tasks themselves.
+
+
+When you create a new task attempt:
+
+- **Existing subtasks** remain linked to their original parent attempt
+- **New subtasks** created from the new attempt will use the new attempt's branch as their base
+- This allows you to maintain different subtask workflows for different approaches
+
+
+For more details about how subtasks work with task attempts, see [Creating Subtasks](/core-features/subtasks).
+
+
+## What Happens Next
+
+After creating a task attempt:
+
+1. **Setup scripts run** automatically (if configured in project settings)
+2. **Agent executes** using your task title and description
+3. **Real-time monitoring** shows progress through streaming logs
+4. **Follow-up questions** can be asked to refine results
+
+For detailed task management after execution, including development server controls, git operations, and monitoring features, see [Task Details Full Screen Mode](/core-features/task-details-full-screen).
+
+## Git Worktrees
+
+Vibe Kanban uses Git worktrees to create isolated environments for each task attempt. These environments are ephemeral and automatically cleaned up after execution completes.
+
+
+Worktrees ensure task attempts don't interfere with each other or your main working directory.
+
diff --git a/docs/core-features/creating-tasks.mdx b/docs/core-features/creating-tasks.mdx
new file mode 100644
index 00000000..918164d4
--- /dev/null
+++ b/docs/core-features/creating-tasks.mdx
@@ -0,0 +1,114 @@
+---
+title: "Creating Tasks"
+description: "Learn how to create and manage tasks on your kanban board, including using templates, starting coding agents, and understanding task states"
+---
+
+
+
+
+
+After creating a project, add tasks by clicking the **plus (+) icon** in the top right of your project kanban page, or by using the keyboard shortcut **`c`**. Creating a task adds it to your kanban board without automatically starting a coding agent.
+
+## Using Templates
+
+
+
+
+
+When adding a task, you can select from your saved templates:
+
+1. Click the **Use a template** dropdown
+2. Choose from available global or project templates
+3. The template automatically populates the task title and description
+
+
+Templates save time by reusing common task structures. Learn more about creating templates in the [Task Templates](/configuration-customisation/creating-task-templates) guide.
+
+
+## Starting Your First Task Attempt
+
+
+
+
+
+To activate a coding agent on your task, create a task attempt:
+
+
+
+ Choose from available agents (e.g., CLAUDE_CODE, GEMINI, CODEX). Your default configuration from Settings is pre-selected.
+
+
+
+ If your selected agent has variants, pick the appropriate one (e.g., DEFAULT, PLAN).
+
+
+
+ Specify which branch the agent should work from. Your current branch is selected by default.
+
+
+
+
+Use **Create & Start** to add the task and immediately create a task attempt with your default settings in one action.
+
+
+### What Happens During Execution
+
+1. **Setup Scripts Run**: Any setup script defined in your project settings runs automatically
+2. **Agent Execution**: The coding agent processes your task using the title and description
+3. **Real-time Monitoring**: Watch progress through streaming logs in the task interface
+4. **Follow-up Questions**: Continue the conversation after execution to refine results
+
+Most tasks only need a single attempt. You'll only need additional attempts if you want to restart from scratch with different settings.
+
+
+For detailed task management after execution, see [Task Details Full Screen Mode](/core-features/task-details-full-screen). To understand when you might need multiple attempts, see [Creating Task Attempts](/core-features/creating-task-attempts).
+
+
+## Creating Tasks via MCP Clients
+
+
+This is not the typical method for creating tasks but can be valuable for bulk task creation or migrating from other systems.
+
+
+Tasks can also be created programmatically using coding agents or MCP (Model Context Protocol) clients such as Claude Desktop or Raycast. This approach is particularly useful for:
+
+- **Bulk task creation** based on existing data or project specifications
+- **Migration from other systems** like Linear, GitHub Issues, or Jira
+- **Automated task generation** from project plans or requirements documents
+
+
+For detailed setup instructions and examples, see the [Vibe Kanban MCP Server](/integrations/vibe-kanban-mcp-server) documentation.
+
+
+### Example MCP Task Creation
+
+Once configured with an MCP client, you can create multiple tasks from a project description:
+
+```
+I need to implement user authentication with:
+- Email/password registration
+- Login with session management
+- Password reset functionality
+- Email verification
+- Protected route middleware
+
+Please create individual tasks for each component.
+```
+
+The MCP client will automatically generate structured tasks in your Vibe Kanban project based on this description.
+
+## Understanding Task Columns
+
+Tasks begin in the "To do" column and move automatically based on their progress:
+
+| Action | Column |
+|--------|---------|
+| Task created | To do |
+| Task attempt started | In Progress |
+| Task attempt completed (success or failure) | In Review |
+| Task attempt merged | Done |
+| PR merged on GitHub | Done |
+
+
+You can manually drag tasks between columns, but this won't trigger any functionality. Task movement is primarily driven by coding agent actions and GitHub integration (which polls every 60 seconds).
+
diff --git a/docs/core-features/reviewing-code-changes.mdx b/docs/core-features/reviewing-code-changes.mdx
new file mode 100644
index 00000000..32029844
--- /dev/null
+++ b/docs/core-features/reviewing-code-changes.mdx
@@ -0,0 +1,100 @@
+---
+title: "Reviewing Code Changes"
+description: "Learn how to review and provide feedback on code changes made by coding agents"
+---
+
+When a coding agent completes a task, it automatically moves to the **In Review** column. This is where you can examine the changes, provide feedback, and ensure the implementation meets your requirements.
+
+
+
+## Opening the Code Review Interface
+
+
+
+ Click on any task in the **In Review** column to open it in full screen mode.
+
+
+
+ Once the task is open, click on the **Diffs** tab to view all the code changes made by the agent.
+
+
+
+## Adding Review Comments
+
+### Line-Specific Comments
+
+To provide feedback on specific lines of code:
+
+
+
+ Find the line you want to comment on in the diffs view.
+
+
+
+ Click the **plus icon** (+) at the beginning of the line to create a review comment.
+
+
+
+
+
+
+
+ Enter your comment in the text field that appears. You can provide suggestions, ask questions, or request changes.
+
+
+
+### Multiple Comments Across Files
+
+You can create several review comments across different files in the same review:
+
+- Add comments to multiple lines within a single file
+- Switch between different changed files and add comments to each
+- All comments will be collected and submitted together as part of your review
+
+
+Review comments are not submitted individually. They are collected and sent as a complete review when you submit your feedback.
+
+
+## General Review Comments
+
+In addition to line-specific feedback, you can provide general comments about the entire implementation:
+
+
+
+ Navigate to the task chat field at the bottom of the review interface.
+
+
+
+ Enter broader comments about the implementation, such as:
+ - Overall code quality assessment
+ - Architectural concerns
+ - Performance considerations
+ - Testing requirements
+
+
+
+## Submitting Your Review
+
+
+
+ Before submitting, review all the line-specific and general comments you've added.
+
+
+
+ Click the **Send** button to send all your feedback to the coding agent.
+
+
+ All comments (line-specific and general) are combined into a single message for the coding agent to address.
+
+
+
+
+ Once submitted, the task returns to the **In Progress** column where the agent will address your feedback and implement the requested changes.
+
+
+
+
diff --git a/docs/core-features/subtasks.mdx b/docs/core-features/subtasks.mdx
new file mode 100644
index 00000000..c6cc35eb
--- /dev/null
+++ b/docs/core-features/subtasks.mdx
@@ -0,0 +1,128 @@
+---
+title: "Creating Subtasks"
+description: "Learn how to create and manage subtasks to break down complex work into smaller, manageable pieces"
+---
+
+Subtasks allow you to break down complex tasks into smaller, more manageable pieces. Each subtask is linked to a specific task attempt and inherits the same project and branch context.
+
+## Creating Subtasks
+
+
+
+
+
+To create a subtask from an existing task attempt:
+
+
+
+ Open the task you want to create subtasks for.
+
+
+
+ In the actions toolbar, click the **Create Subtask** button (marked with a fork icon).
+
+
+
+ The task creation dialog opens with the parent task attempt and base branch automatically set. Add your subtask title and description.
+
+
+
+ Click **Save** to create the subtask. It will appear as a new task on your kanban board.
+
+
+
+
+When you create a subtask, it automatically inherits the base branch from its parent task attempt, ensuring consistency in your development workflow.
+
+
+## Viewing Tasks with Subtasks
+
+
+
+
+
+When viewing a parent task, you can see its subtasks in the **Task Relationships** panel. This collapsible section shows:
+
+- **Child Tasks** with a count (e.g., "CHILD TASKS (1)")
+- Individual subtask titles with links to view them
+- Easy navigation between parent and child tasks
+
+This helps you track progress across all related work items and understand the task hierarchy at a glance.
+
+## Viewing Subtask Details
+
+
+
+
+
+When viewing a subtask, the **Task Relationships** panel displays:
+
+- **Parent Task** section showing the parent task title
+- Direct link to navigate to the parent task
+- Clear visual indication that this is a child task
+- Context about the parent-child relationship
+
+The subtask also shows its own **Create Subtask** button, allowing you to create nested subtasks if needed.
+
+## How Subtasks Work
+
+Subtasks in Vibe Kanban follow these key principles:
+
+### Git Branching Workflow
+
+Subtasks create their own feature branches that can work independently while maintaining connection to the parent task:
+
+```mermaid
+gitGraph
+ commit id: "main"
+ branch feature/parent-task
+ checkout feature/parent-task
+ commit id: "Parent Task Start"
+ commit id: "Initial work"
+
+ branch feature/subtask-1
+ checkout feature/subtask-1
+ commit id: "Subtask 1: Backend API"
+ commit id: "API implementation"
+ commit id: "API tests"
+
+ checkout feature/parent-task
+ branch feature/subtask-2
+ checkout feature/subtask-2
+ commit id: "Subtask 2: Frontend UI"
+ commit id: "Component creation"
+ commit id: "UI styling"
+
+ checkout feature/parent-task
+ branch feature/subtask-3
+ checkout feature/subtask-3
+ commit id: "Subtask 3: Integration"
+ commit id: "Connect API to UI"
+
+ checkout feature/parent-task
+ merge feature/subtask-1
+ merge feature/subtask-2
+ merge feature/subtask-3
+ commit id: "Parent Task Complete"
+
+ checkout main
+ merge feature/parent-task
+```
+
+### Parent-Child Relationships
+
+- Subtasks are linked to specific **task attempts**, not just tasks
+- Each subtask knows which attempt created it
+- Multiple subtasks can be created from the same parent attempt
+
+### Branch Inheritance
+
+- Subtasks automatically inherit the base branch from their parent attempt
+- This ensures subtasks work within the same development context
+- You can modify the branch when creating the subtask if needed
+
+### Independent Task Lifecycle
+
+- Subtasks appear as regular tasks on your kanban board
+- Each subtask has its own lifecycle (To do → In Progress → In Review → Done)
+- Subtasks can have their own task attempts and coding agents
diff --git a/docs/core-features/task-details-full-screen.mdx b/docs/core-features/task-details-full-screen.mdx
new file mode 100644
index 00000000..582e9a8b
--- /dev/null
+++ b/docs/core-features/task-details-full-screen.mdx
@@ -0,0 +1,135 @@
+---
+title: "Task Details Full Screen Mode"
+sidebarTitle: "Full Screen Mode"
+description: "Complete guide to using the task details full screen mode for development workflows, including dev server, git operations, logs, diffs, and process monitoring"
+---
+
+## Accessing Full Screen Mode
+
+Click the **Maximise** button (⛶) in the task details header to expand the view to occupy the full right side of your screen. Some task actions (like "View full diff") automatically switch to full screen mode for better visibility.
+
+
+
+
+
+## Interface Layout
+
+Full screen mode uses a two-column layout:
+
+### Left Sidebar
+- **Task Information**: Title, description, and metadata
+- **Development Toolbar**: Primary development actions
+- **TODOs**: Task checklist and progress tracking
+- **Relationships**: Subtasks and parent task links
+
+### Right Panel
+- **Tab Navigation**: Switch between Logs, Diffs, and Processes
+- **Content Area**: Active tab content with real-time updates
+- **Follow-up Section**: Additional context and actions
+
+## Core Features
+
+### Development Server
+
+Start and manage your project's development environment directly from the task interface.
+
+**Controls:**
+- **Dev** (▶️): Start the development server using your project's configured dev script
+- **Stop Dev** (⏹️): Terminate the running development server
+- **View Logs** (📄): Jump to process logs to monitor server output
+
+The development server runs in a git worktree environment and streams all output to the Processes tab. Click the logs button next to the dev server control to jump directly to the process logs for real-time monitoring.
+
+### Git Operations
+
+#### Rebase
+Keep your task branch up-to-date with the latest changes from the base branch.
+
+- **Automatic Detection**: The rebase button appears when your branch is behind the base branch
+- **Conflict Handling**: Any merge conflicts are displayed in the Diffs tab
+
+#### Merge
+Integrate your completed work back into the base branch.
+
+- **Availability**: Disabled when an open pull request exists
+- **Success Indication**: A "Merged!" notification confirms successful integration
+
+#### Push & Pull Request Management
+- **Create PR**: Opens pull request creation dialog for new branches
+- **Push to PR**: Updates existing pull request with latest changes
+- **Auto-detection**: Automatically detects existing PRs and adjusts button behavior
+
+### Task Management
+
+#### History & Attempts
+View and manage all task attempts from the full screen interface.
+
+- **History**: View all previous attempts for this task, review execution status and outcomes, and switch between different attempts to compare results
+- **New Attempt**: Create additional attempts when previous approaches didn't work as expected or when testing different implementation strategies
+
+
+For detailed information about when and why to create new attempts, see [Creating Task Attempts](/core-features/creating-task-attempts).
+
+
+#### Subtasks
+Break down complex tasks into manageable pieces.
+
+- **Create Subtask** (🔀): Opens task creation form with:
+ - Parent task automatically linked
+ - Initial base branch set to the current attempt's branch
+ - Subtasks link to specific task attempts, not tasks themselves
+
+
+Creating new task attempts affects existing subtasks, as they remain linked to their original parent attempt.
+
+
+Learn more in [Creating Subtasks](/core-features/subtasks).
+
+### Monitoring & Analysis
+
+#### Logs Tab
+The Logs tab provides real-time streaming of coding agent activities and reasoning. You can see the agent's thought process, actions being taken, and responses as tasks are executed. Process events from development servers, builds, and script execution are also logged here.
+
+
+
+
+
+#### Diffs Tab
+The Diffs tab provides a visual representation of all code changes made during task execution. It shows a git diff between your branch and the base branch, with syntax highlighting and language-aware code formatting. You can see a summary of added, modified, and deleted files with precise line-by-line change tracking and context.
+
+
+
+
+
+Learn more in [Reviewing Code Changes](/core-features/reviewing-code-changes).
+
+#### Processes Tab
+The Processes tab displays a timeline view of all running and completed processes. You can track the status of running, completed, failed, and stopped processes with their complete execution timeline. Click any process to view its specific output logs, and use the interactive controls to stop running processes directly from the interface.
+
+
+
+
+
+## Navigation & Controls
+
+### Keyboard Shortcuts
+- **Escape**: Exit full screen mode and return to sidebar view
+- **Tab Navigation**: Use browser tab controls to switch between Logs, Diffs, and Processes
+
+
+
+## Exiting Full Screen Mode
+
+- Click the **Minimize** button in the header
+- Press **Escape** key
+- Click the **×** button to close the task panel entirely
+- Navigate to a different task or project
+
+The interface gracefully transitions back to the compact sidebar view while preserving your work context.
+
+## Related Documentation
+
+- [Creating Task Attempts](/core-features/creating-task-attempts) - Learn about task attempt lifecycle
+- [Reviewing Code Changes](/core-features/reviewing-code-changes) - Deep dive into diff analysis
+- [Creating Tasks](/core-features/creating-tasks) - Task creation and management
+- [Agent Configurations](/configuration-customisation/agent-configurations) - Customise AI agent behaviour
diff --git a/docs/development.mdx b/docs/development.mdx
deleted file mode 100644
index ac633bad..00000000
--- a/docs/development.mdx
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: 'Development'
-description: 'Preview changes locally to update your docs'
----
-
-
- **Prerequisites**:
- - Node.js version 19 or higher
- - A docs repository with a `docs.json` file
-
-
-Follow these steps to install and run Mintlify on your operating system.
-
-
-
-
-```bash
-npm i -g mint
-```
-
-
-
-
-Navigate to your docs directory where your `docs.json` file is located, and run the following command:
-
-```bash
-mint dev
-```
-
-A local preview of your documentation will be available at `http://localhost:3000`.
-
-
-
-
-## Custom ports
-
-By default, Mintlify uses port 3000. You can customize the port Mintlify runs on by using the `--port` flag. For example, to run Mintlify on port 3333, use this command:
-
-```bash
-mint dev --port 3333
-```
-
-If you attempt to run Mintlify on a port that's already in use, it will use the next available port:
-
-```md
-Port 3000 is already in use. Trying 3001 instead.
-```
-
-## Mintlify versions
-
-Please note that each CLI release is associated with a specific version of Mintlify. If your local preview does not align with the production version, please update the CLI:
-
-```bash
-npm mint update
-```
-
-## Validating links
-
-The CLI can assist with validating links in your documentation. To identify any broken links, use the following command:
-
-```bash
-mint broken-links
-```
-
-## Deployment
-
-If the deployment is successful, you should see the following:
-
-
-
-
-
-## Code formatting
-
-We suggest using extensions on your IDE to recognize and format MDX. If you're a VSCode user, consider the [MDX VSCode extension](https://marketplace.visualstudio.com/items?itemName=unifiedjs.vscode-mdx) for syntax highlighting, and [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) for code formatting.
-
-## Troubleshooting
-
-
-
-
- This may be due to an outdated version of node. Try the following:
- 1. Remove the currently-installed version of the CLI: `npm remove -g mint`
- 2. Upgrade to Node v19 or higher.
- 3. Reinstall the CLI: `npm i -g mint`
-
-
-
-
- Solution: Go to the root of your device and delete the `~/.mintlify` folder. Then run `mint dev` again.
-
-
-
-Curious about what changed in the latest CLI version? Check out the [CLI changelog](https://www.npmjs.com/package/mintlify?activeTab=versions).
diff --git a/docs/docs.json b/docs/docs.json
index c6936ef3..346a1b21 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -3,6 +3,10 @@
"theme": "mint",
"name": "Vibe Kanban",
"description": "A kanban board for developers to track coding tasks with AI coding agents",
+ "banner": {
+ "content": "🎉 **Ultimate Agents Hackathon** - London, September 20th | £10k in prizes! [Register now](https://london.aitinkerers.org/p/ultimate-agents-hackathon-10k-total-prizes)",
+ "dismissible": true
+ },
"colors": {
"primary": "#000000",
"light": "#fefefe",
@@ -19,31 +23,35 @@
"groups": [
{
"group": "Getting started",
- "pages": ["index", "getting-started", "onboarding", "global-settings"]
+ "pages": ["index", "getting-started", "supported-coding-agents"]
},
{
- "group": "Supported Coding Agents",
+ "group": "Core Features",
"pages": [
- "supported-coding-agents",
- "supported-coding-agents/amp",
- "supported-coding-agents/claude-code",
- "supported-coding-agents/cursor-cli",
- "supported-coding-agents/ccr",
- "supported-coding-agents/codex",
- "supported-coding-agents/gemini-cli",
- "supported-coding-agents/sst-opencode",
- "supported-coding-agents/qwen-code"
+ "core-features/creating-projects",
+ "core-features/creating-tasks",
+ "core-features/subtasks",
+ "core-features/creating-task-attempts",
+ "core-features/reviewing-code-changes",
+ "core-features/task-details-full-screen"
]
},
{
- "group": "User Guide",
+ "group": "Configuration & Customisation",
"pages": [
- "user-guide/creating-projects",
- "user-guide/creating-tasks",
- "user-guide/creating-task-attempts",
- "user-guide/creating-task-templates",
- "user-guide/agent-configurations",
- "user-guide/vibe-kanban-mcp-server"
+ "configuration-customisation/global-settings",
+ "configuration-customisation/agent-configurations",
+ "configuration-customisation/creating-task-templates",
+ "configuration-customisation/keyboard-shortcuts"
+ ]
+ },
+ {
+ "group": "Integrations",
+ "pages": [
+ "integrations/github-integration",
+ "integrations/vscode-extension",
+ "integrations/mcp-server-configuration",
+ "integrations/vibe-kanban-mcp-server"
]
}
]
diff --git a/docs/essentials/code.mdx b/docs/essentials/code.mdx
deleted file mode 100644
index ae2abbfe..00000000
--- a/docs/essentials/code.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: 'Code blocks'
-description: 'Display inline code and code blocks'
-icon: 'code'
----
-
-## Inline code
-
-To denote a `word` or `phrase` as code, enclose it in backticks (`).
-
-```
-To denote a `word` or `phrase` as code, enclose it in backticks (`).
-```
-
-## Code blocks
-
-Use [fenced code blocks](https://www.markdownguide.org/extended-syntax/#fenced-code-blocks) by enclosing code in three backticks and follow the leading ticks with the programming language of your snippet to get syntax highlighting. Optionally, you can also write the name of your code after the programming language.
-
-```java HelloWorld.java
-class HelloWorld {
- public static void main(String[] args) {
- System.out.println("Hello, World!");
- }
-}
-```
-
-````md
-```java HelloWorld.java
-class HelloWorld {
- public static void main(String[] args) {
- System.out.println("Hello, World!");
- }
-}
-```
-````
diff --git a/docs/essentials/images.mdx b/docs/essentials/images.mdx
deleted file mode 100644
index 1144eb2c..00000000
--- a/docs/essentials/images.mdx
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: 'Images and embeds'
-description: 'Add image, video, and other HTML elements'
-icon: 'image'
----
-
-
-
-## Image
-
-### Using Markdown
-
-The [markdown syntax](https://www.markdownguide.org/basic-syntax/#images) lets you add images using the following code
-
-```md
-
-```
-
-Note that the image file size must be less than 5MB. Otherwise, we recommend hosting on a service like [Cloudinary](https://cloudinary.com/) or [S3](https://aws.amazon.com/s3/). You can then use that URL and embed.
-
-### Using embeds
-
-To get more customizability with images, you can also use [embeds](/writing-content/embed) to add images
-
-```html
-
-```
-
-## Embeds and HTML elements
-
-
-
-
-
-
-
-Mintlify supports [HTML tags in Markdown](https://www.markdownguide.org/basic-syntax/#html). This is helpful if you prefer HTML tags to Markdown syntax, and lets you create documentation with infinite flexibility.
-
-
-
-### iFrames
-
-Loads another HTML page within the document. Most commonly used for embedding videos.
-
-```html
-
-```
diff --git a/docs/essentials/markdown.mdx b/docs/essentials/markdown.mdx
deleted file mode 100644
index a45c1d56..00000000
--- a/docs/essentials/markdown.mdx
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: 'Markdown syntax'
-description: 'Text, title, and styling in standard markdown'
-icon: 'text-size'
----
-
-## Titles
-
-Best used for section headers.
-
-```md
-## Titles
-```
-
-### Subtitles
-
-Best used for subsection headers.
-
-```md
-### Subtitles
-```
-
-
-
-Each **title** and **subtitle** creates an anchor and also shows up on the table of contents on the right.
-
-
-
-## Text formatting
-
-We support most markdown formatting. Simply add `**`, `_`, or `~` around text to format it.
-
-| Style | How to write it | Result |
-| ------------- | ----------------- | --------------- |
-| Bold | `**bold**` | **bold** |
-| Italic | `_italic_` | _italic_ |
-| Strikethrough | `~strikethrough~` | ~strikethrough~ |
-
-You can combine these. For example, write `**_bold and italic_**` to get **_bold and italic_** text.
-
-You need to use HTML to write superscript and subscript text. That is, add `` or `` around your text.
-
-| Text Size | How to write it | Result |
-| ----------- | ------------------------ | ---------------------- |
-| Superscript | `superscript` | superscript |
-| Subscript | `subscript` | subscript |
-
-## Linking to pages
-
-You can add a link by wrapping text in `[]()`. You would write `[link to google](https://google.com)` to [link to google](https://google.com).
-
-Links to pages in your docs need to be root-relative. Basically, you should include the entire folder path. For example, `[link to text](/writing-content/text)` links to the page "Text" in our components section.
-
-Relative links like `[link to text](../text)` will open slower because we cannot optimize them as easily.
-
-## Blockquotes
-
-### Singleline
-
-To create a blockquote, add a `>` in front of a paragraph.
-
-> Dorothy followed her through many of the beautiful rooms in her castle.
-
-```md
-> Dorothy followed her through many of the beautiful rooms in her castle.
-```
-
-### Multiline
-
-> Dorothy followed her through many of the beautiful rooms in her castle.
->
-> The Witch bade her clean the pots and kettles and sweep the floor and keep the fire fed with wood.
-
-```md
-> Dorothy followed her through many of the beautiful rooms in her castle.
->
-> The Witch bade her clean the pots and kettles and sweep the floor and keep the fire fed with wood.
-```
-
-### LaTeX
-
-Mintlify supports [LaTeX](https://www.latex-project.org) through the Latex component.
-
-8 x (vk x H1 - H2) = (0,1)
-
-```md
-8 x (vk x H1 - H2) = (0,1)
-```
diff --git a/docs/essentials/navigation.mdx b/docs/essentials/navigation.mdx
deleted file mode 100644
index 60adeff2..00000000
--- a/docs/essentials/navigation.mdx
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: 'Navigation'
-description: 'The navigation field in docs.json defines the pages that go in the navigation menu'
-icon: 'map'
----
-
-The navigation menu is the list of links on every website.
-
-You will likely update `docs.json` every time you add a new page. Pages do not show up automatically.
-
-## Navigation syntax
-
-Our navigation syntax is recursive which means you can make nested navigation groups. You don't need to include `.mdx` in page names.
-
-
-
-```json Regular Navigation
-"navigation": {
- "tabs": [
- {
- "tab": "Docs",
- "groups": [
- {
- "group": "Getting Started",
- "pages": ["quickstart"]
- }
- ]
- }
- ]
-}
-```
-
-```json Nested Navigation
-"navigation": {
- "tabs": [
- {
- "tab": "Docs",
- "groups": [
- {
- "group": "Getting Started",
- "pages": [
- "quickstart",
- {
- "group": "Nested Reference Pages",
- "pages": ["nested-reference-page"]
- }
- ]
- }
- ]
- }
- ]
-}
-```
-
-
-
-## Folders
-
-Simply put your MDX files in folders and update the paths in `docs.json`.
-
-For example, to have a page at `https://yoursite.com/your-folder/your-page` you would make a folder called `your-folder` containing an MDX file called `your-page.mdx`.
-
-
-
-You cannot use `api` for the name of a folder unless you nest it inside another folder. Mintlify uses Next.js which reserves the top-level `api` folder for internal server calls. A folder name such as `api-reference` would be accepted.
-
-
-
-```json Navigation With Folder
-"navigation": {
- "tabs": [
- {
- "tab": "Docs",
- "groups": [
- {
- "group": "Group Name",
- "pages": ["your-folder/your-page"]
- }
- ]
- }
- ]
-}
-```
-
-## Hidden pages
-
-MDX files not included in `docs.json` will not show up in the sidebar but are accessible through the search bar and by linking directly to them.
diff --git a/docs/essentials/reusable-snippets.mdx b/docs/essentials/reusable-snippets.mdx
deleted file mode 100644
index 376e27bd..00000000
--- a/docs/essentials/reusable-snippets.mdx
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: "Reusable snippets"
-description: "Reusable, custom snippets to keep content in sync"
-icon: "recycle"
----
-
-import SnippetIntro from '/snippets/snippet-intro.mdx';
-
-
-
-## Creating a custom snippet
-
-**Pre-condition**: You must create your snippet file in the `snippets` directory.
-
-
- Any page in the `snippets` directory will be treated as a snippet and will not
- be rendered into a standalone page. If you want to create a standalone page
- from the snippet, import the snippet into another file and call it as a
- component.
-
-
-### Default export
-
-1. Add content to your snippet file that you want to re-use across multiple
- locations. Optionally, you can add variables that can be filled in via props
- when you import the snippet.
-
-```mdx snippets/my-snippet.mdx
-Hello world! This is my content I want to reuse across pages. My keyword of the
-day is {word}.
-```
-
-
- The content that you want to reuse must be inside the `snippets` directory in
- order for the import to work.
-
-
-2. Import the snippet into your destination file.
-
-```mdx destination-file.mdx
----
-title: My title
-description: My Description
----
-
-import MySnippet from '/snippets/path/to/my-snippet.mdx';
-
-## Header
-
-Lorem impsum dolor sit amet.
-
-
-```
-
-### Reusable variables
-
-1. Export a variable from your snippet file:
-
-```mdx snippets/path/to/custom-variables.mdx
-export const myName = 'my name';
-
-export const myObject = { fruit: 'strawberries' };
-```
-
-2. Import the snippet from your destination file and use the variable:
-
-```mdx destination-file.mdx
----
-title: My title
-description: My Description
----
-
-import { myName, myObject } from '/snippets/path/to/custom-variables.mdx';
-
-Hello, my name is {myName} and I like {myObject.fruit}.
-```
-
-### Reusable components
-
-1. Inside your snippet file, create a component that takes in props by exporting
- your component in the form of an arrow function.
-
-```mdx snippets/custom-component.mdx
-export const MyComponent = ({ title }) => (
-
-
{title}
-
... snippet content ...
-
-);
-```
-
-
- MDX does not compile inside the body of an arrow function. Stick to HTML
- syntax when you can or use a default export if you need to use MDX.
-
-
-2. Import the snippet into your destination file and pass in the props
-
-```mdx destination-file.mdx
----
-title: My title
-description: My Description
----
-
-import { MyComponent } from '/snippets/custom-component.mdx';
-
-Lorem ipsum dolor sit amet.
-
-
-```
diff --git a/docs/essentials/settings.mdx b/docs/essentials/settings.mdx
deleted file mode 100644
index 884de13a..00000000
--- a/docs/essentials/settings.mdx
+++ /dev/null
@@ -1,318 +0,0 @@
----
-title: 'Global Settings'
-description: 'Mintlify gives you complete control over the look and feel of your documentation using the docs.json file'
-icon: 'gear'
----
-
-Every Mintlify site needs a `docs.json` file with the core configuration settings. Learn more about the [properties](#properties) below.
-
-## Properties
-
-
-Name of your project. Used for the global title.
-
-Example: `mintlify`
-
-
-
-
- An array of groups with all the pages within that group
-
-
- The name of the group.
-
- Example: `Settings`
-
-
-
- The relative paths to the markdown files that will serve as pages.
-
- Example: `["customization", "page"]`
-
-
-
-
-
-
-
- Path to logo image or object with path to "light" and "dark" mode logo images
-
-
- Path to the logo in light mode
-
-
- Path to the logo in dark mode
-
-
- Where clicking on the logo links you to
-
-
-
-
-
- Path to the favicon image
-
-
-
- Hex color codes for your global theme
-
-
- The primary color. Used for most often for highlighted content, section
- headers, accents, in light mode
-
-
- The primary color for dark mode. Used for most often for highlighted
- content, section headers, accents, in dark mode
-
-
- The primary color for important buttons
-
-
- The color of the background in both light and dark mode
-
-
- The hex color code of the background in light mode
-
-
- The hex color code of the background in dark mode
-
-
-
-
-
-
-
- Array of `name`s and `url`s of links you want to include in the topbar
-
-
- The name of the button.
-
- Example: `Contact us`
-
-
- The url once you click on the button. Example: `https://mintlify.com/docs`
-
-
-
-
-
-
-
-
- Link shows a button. GitHub shows the repo information at the url provided including the number of GitHub stars.
-
-
- If `link`: What the button links to.
-
- If `github`: Link to the repository to load GitHub information from.
-
-
- Text inside the button. Only required if `type` is a `link`.
-
-
-
-
-
-
- Array of version names. Only use this if you want to show different versions
- of docs with a dropdown in the navigation bar.
-
-
-
- An array of the anchors, includes the `icon`, `color`, and `url`.
-
-
- The [Font Awesome](https://fontawesome.com/search?q=heart) icon used to feature the anchor.
-
- Example: `comments`
-
-
- The name of the anchor label.
-
- Example: `Community`
-
-
- The start of the URL that marks what pages go in the anchor. Generally, this is the name of the folder you put your pages in.
-
-
- The hex color of the anchor icon background. Can also be a gradient if you pass an object with the properties `from` and `to` that are each a hex color.
-
-
- Used if you want to hide an anchor until the correct docs version is selected.
-
-
- Pass `true` if you want to hide the anchor until you directly link someone to docs inside it.
-
-
- One of: "brands", "duotone", "light", "sharp-solid", "solid", or "thin"
-
-
-
-
-
-
- Override the default configurations for the top-most anchor.
-
-
- The name of the top-most anchor
-
-
- Font Awesome icon.
-
-
- One of: "brands", "duotone", "light", "sharp-solid", "solid", or "thin"
-
-
-
-
-
- An array of navigational tabs.
-
-
- The name of the tab label.
-
-
- The start of the URL that marks what pages go in the tab. Generally, this
- is the name of the folder you put your pages in.
-
-
-
-
-
- Configuration for API settings. Learn more about API pages at [API Components](/api-playground/demo).
-
-
- The base url for all API endpoints. If `baseUrl` is an array, it will enable for multiple base url
- options that the user can toggle.
-
-
-
-
-
- The authentication strategy used for all API endpoints.
-
-
- The name of the authentication parameter used in the API playground.
-
- If method is `basic`, the format should be `[usernameName]:[passwordName]`
-
-
- The default value that's designed to be a prefix for the authentication input field.
-
- E.g. If an `inputPrefix` of `AuthKey` would inherit the default input result of the authentication field as `AuthKey`.
-
-
-
-
-
- Configurations for the API playground
-
-
-
- Whether the playground is showing, hidden, or only displaying the endpoint with no added user interactivity `simple`
-
- Learn more at the [playground guides](/api-playground/demo)
-
-
-
-
-
- Enabling this flag ensures that key ordering in OpenAPI pages matches the key ordering defined in the OpenAPI file.
-
- This behavior will soon be enabled by default, at which point this field will be deprecated.
-
-
-
-
-
-
- A string or an array of strings of URL(s) or relative path(s) pointing to your
- OpenAPI file.
-
- Examples:
-
- ```json Absolute
- "openapi": "https://example.com/openapi.json"
- ```
- ```json Relative
- "openapi": "/openapi.json"
- ```
- ```json Multiple
- "openapi": ["https://example.com/openapi1.json", "/openapi2.json", "/openapi3.json"]
- ```
-
-
-
-
-
- An object of social media accounts where the key:property pair represents the social media platform and the account url.
-
- Example:
- ```json
- {
- "x": "https://x.com/mintlify",
- "website": "https://mintlify.com"
- }
- ```
-
-
- One of the following values `website`, `facebook`, `x`, `discord`, `slack`, `github`, `linkedin`, `instagram`, `hacker-news`
-
- Example: `x`
-
-
- The URL to the social platform.
-
- Example: `https://x.com/mintlify`
-
-
-
-
-
- Configurations to enable feedback buttons
-
-
-
- Enables a button to allow users to suggest edits via pull requests
-
-
- Enables a button to allow users to raise an issue about the documentation
-
-
-
-
-
- Customize the dark mode toggle.
-
-
- Set if you always want to show light or dark mode for new users. When not
- set, we default to the same mode as the user's operating system.
-
-
- Set to true to hide the dark/light mode toggle. You can combine `isHidden` with `default` to force your docs to only use light or dark mode. For example:
-
-
- ```json Only Dark Mode
- "modeToggle": {
- "default": "dark",
- "isHidden": true
- }
- ```
-
- ```json Only Light Mode
- "modeToggle": {
- "default": "light",
- "isHidden": true
- }
- ```
-
-
-
-
-
-
-
-
- A background image to be displayed behind every page. See example with
- [Infisical](https://infisical.com/docs) and [FRPC](https://frpc.io).
-
diff --git a/docs/getting-started.mdx b/docs/getting-started.mdx
index e9b9b431..8bb13428 100644
--- a/docs/getting-started.mdx
+++ b/docs/getting-started.mdx
@@ -1,4 +1,8 @@
-# Install & Run Vibe Kanban
+---
+title: "Install & Run Vibe Kanban"
+description: "Complete installation guide for Vibe Kanban on macOS, Linux, and Windows"
+sidebarTitle: "Installation"
+---
## Supported Systems
@@ -8,30 +12,53 @@ We build and test Vibe Kanban on the following systems:
- Linux
- Windows
-## Pre-requisites
+## Prerequisites
-- Node.js
-- Coding agent authenticated
- - All supported coding agents can now be used via npx (no separate installation required)
- - You still need to authenticate with each coding agent outside of Vibe Kanban
- - You can find authentication instructions for each coding agent on their respective [websites](./supported-coding-agents).
+Before installing Vibe Kanban, ensure you have:
-## Running Vibe Kanban
+- **Node.js**: Latest LTS version recommended
+- **Coding agent authentication**: Authenticate with your preferred coding agents outside of Vibe Kanban
-1. Open a terminal and run:
+
+All supported coding agents can be used via npx without separate installation. You can find authentication instructions for each coding agent on their respective [websites](./supported-coding-agents).
+
-```
-npx vibe-kanban
-```
+## Installation & Setup
-2. [Complete the onboarding steps](/docs/getting-started/onboarding) in the application
+
+
+ Open a terminal and run:
-3. [Configure Global Settings](/docs/getting-started/global-settings) to personalize your experience
+ ```bash
+ npx vibe-kanban
+ ```
-4. [Create a project](/docs/user-guide/creating-projects)
+
+ The application will bind to a random free port, print the URL in the terminal, and automatically open in your default browser.
+
+
-5. [Create tasks](/docs/user-guide/creating-tasks)
+
+ Complete the setup dialogs to configure your coding agent and editor preferences. GitHub authentication is optional and can be configured later.
+
-6. Optional: [Set up MCP integration](/docs/user-guide/vibe-kanban-mcp-server) to streamline task creation with coding agents
+
+ You'll land on an empty Projects page. Click "Create your first project" to set up your initial project.
+
-A note on ports: By default the application will bind to a random free port, print the URL in the terminal and attempt to open the link in the default browser. If you would like to use a fixed port you can optionally specify the `PORT` environment variable, so to force Vibe Kanban to start on port 8080 you would run `PORT=8080 npx vibe-kanban`.
+
+ Start tracking your work by [creating tasks](/core-features/creating-tasks) within your project.
+
+
+
+ Connect to GitHub in [Settings](/configuration-customisation/global-settings) to enable branch management and pull request creation.
+
+
+
+ Streamline task creation with coding agents by [setting up MCP integration](/integrations/vibe-kanban-mcp-server).
+
+
+
+
+To use a fixed port, specify the `PORT` environment variable: `PORT=8080 npx vibe-kanban`
+
diff --git a/docs/global-settings.mdx b/docs/global-settings.mdx
deleted file mode 100644
index c004ccac..00000000
--- a/docs/global-settings.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
-# Global Settings
-
-You can configure application-wide settings via the **Settings** page. To access it, click the ⚙️ icon in the sidebar or select "Settings" from the top-right menu.
-
-
-
-## Themes
-
-Switch between light and dark themes to suit your preference.
-
-## Default Agent Configuration
-
-Choose the default agent and, if available, a variant. This profile is pre-selected when creating new task attempts and follow-ups.
-
-- Pick an agent (e.g., CLAUDE_CODE, GEMINI, CODEX)
-- If that agent has variants, pick one (e.g., DEFAULT, PLAN, ROUTER)
-- You can change this per attempt in the create attempt dialog
-
-## Editor Integration
-
-Configure integration with your preferred code editor (e.g., VS Code) for a seamless development workflow.
-
-## GitHub Integration
-
-Link your GitHub account by providing a Personal Access Token (PAT) and authenticating. This enables branch management, pull request creation, and status tracking directly from Vibe Kanban.
-
-## Notifications
-
-Toggle sound effects and push notifications to stay informed about task status changes.
-
-## Telemetry
-
-Enable or disable telemetry data collection to help improve Vibe Kanban.
-
-## Task Templates
-
-Manage global task templates to accelerate task creation across all projects. Templates allow you to define a default title and description that can be reused when adding new tasks.
-
-You can learn more about task templates on the [Task Templates](/docs/user-guide/creating-task-templates) page.
-
-## Agent Settings (Profiles & Variants)
-
-Define and customize agent variants under Settings → Agents. Variants let you maintain multiple configurations for the same agent (for example a CLAUDE_CODE "PLAN" variant). See the [Agent Profiles & Variants](/docs/user-guide/agent-configurations) guide for details and examples.
-
-## Safety & Disclaimers
-
-Manage acknowledgments and reset options for onboarding, safety disclaimers, and telemetry notices.
-
-- **Onboarding**: Reset the onboarding process to rerun the initial setup.
-- **Safety Disclaimer**: Reset or review the safety disclaimer prompt.
-- **Telemetry Notice**: Reset or review the telemetry data collection acknowledgment.
diff --git a/docs/images/add-line-comment.png b/docs/images/add-line-comment.png
new file mode 100644
index 0000000000000000000000000000000000000000..e73257535c9160b6bfbf7338a48aea844daf6016
GIT binary patch
literal 52229
zcmd40WmsKF(=Ln#3vR*P-CYt0?(Qx@HnQ>H7Tn!QaCdhIuEA~NE*p0{SLVF$%ro=M
z`F?-<>K|)$bys!WeRox@-eF1#lE{eoh!7AE$kI~cDi9DbJP;6&Wbp4GARufWWp5!M
zpy;jCw4Al%<@inQ0nEl`_9o`c?f?gf-#ET-
zO)hy>c?U7`FIG}tf##}T71T_>+L-d0k&6f;3cB;V0~`S6&c>wf09!jJes>}AKlJk3
zIr0DQW+5m2V~Dej5V@AT5~-Ly(43T;nU$H9To{p55NKw>uOcq-Ka+uG7DD7-oShx`
zSyA@;{&p
zBMP$oxqZTje-Xgk&P<3LNG>9r&fb#<0r6hWN=!^iT1<>o321L&Wor%rAr+RS38$qx
zjFYXaLIwjbE-G^%j~0g^Dg)2tcTFBDBLx+NVfsm_CNBc9QeV9KM;U225n7G0CQd(C
z2M39s;n<|7vK;}^c}cUAXPw9G^=UHAcY@DtZ%qJVYUM%23Z)c5w31R02lHeSKP7RD
z+y#n#3YPZ+!uxxumPAZ!Y!oBBFK-5GAehkFj=kL3N6R-~CY?`ldJqs8u#V|U%tOKV
zq!8{2qV%KCezd{u53_ud~c%8
z=p9T*nk?&dKl3)}{CpOlk@q3B4`1U(PFpIH-6FM#W+|aBQHy8`HNHMnDzpJo)Ul>|
z(jY7?Ej-peNywTa*2#DR0&|P)GE>VygoI)TF6g5zykjdR4SD-|A*()Ne!c&L*yvA>
zcHYn%(n^eBXwxTv!VvY~`!P=r{ej)_aab?O4r1OhfA3e}&qrZs+A)bTJ+W!E*+&e}?HT`v=Q527cF
zVRCFNKS&J6M^X|8bByul?Oegk##n}r
zf#-og4H8KB8C*+d5Dj~(BvLFQVkNQ%*A$Rm*(?G^p8L)|@e|n(8Vt3+xzXuhp*aM6
zdeN{5<`RFhM}IyKdOW37z)EC~+>)%p<5%fZ=yOr}oOVodm3PSnU|nDB$^L%jN_WQ&X*VW4~JqMjz
zspFCJrB91xHN3zu|lI2pV+WXd^xWzBZ`b=htEbd;1?xoec1G
zy8=9KZV>G;cel614->(}a7H--UQ~py6HC>bMW2!Vu0miDwL8Q6l5nBCoTfIxGjIdl
zgp1wonf?UlP(Gw+K><=|aPi&Z2j0|r`|PaPV=z~u=(LcdJ@`r}-2N50h$ru!J_>z-
zqUq6gK+uEa>DF)l%HNGNg}mlJ2_F!PhTkiCjgI*fqee0loqH<~hI~`%eSAD-X;4l59&#jl>sEjC1o<`VxQ$fTIRG!Xy0#(`8~6mW`_6D7;f
zB3E?^${Dg1i%E>(m;M)`uNWOcYoaT^aKE6wW95nrOEW?FK(K8Rr^TKeJzTw{#ikLi
zZqlGd;We>P?OKlX6pHEiZlafH0}-WX+YwS2HYbXuXY_);9YrL{u#aR5bk747Wh7Ni
zm_2>Bed_fg-DKatUrSfrP-JVKao5SUs6FX<>;@86SyP
zxnKEODuQ%zSY+n>=6L1=1#!T%>5mU`b3b%cJ4zg98IJ_5@fwo9e)}5pC?PLDE;la5
zq$6L>tyv)ls9N@D2(c!aYnVHoZ8@SlLcA$B5|~viURU-N%llRS#i!m(hZsOtk?tCP
z>v#Jx@cU+Q&kUON*stQL;+f{si+F|ay3>5uVb@S!>0TgS*gIqsepnR@&+XVu%$H9I
zmV3z7Nk)9!sm{&WhvtlOYyC1PRp-sxQmnbDY~t!bvQ
z^8uPmxr;l$Ha``An~RQ1t4o86zB8tC(V@lx@f^U?M2>+vCaq6zV0E&6_?dI;%LmKU
zFN<5o4Skg;o>e@0lZuM@n&nNBXW!Onypw%$eHvd8U%tLPy=(T*`dHti78v!;@_p;K
ze?#gagcJ
zoO+)cDzA}2$ny|bFuGL@)G{xhDYsJPn3=Sgx45tfw(uMSXQ+-Z?H%rw
zjc1IvG08Cw=#14D*W8cCn+!LO)$7@KOk8#(HK_lX`&9O|Y=8diyx=j^G5)b9Hz$E%
z1|4@2_W~fS(RRgl1-Vi4L`guiO|A{GZS=OdBco%{C(wHZz85|QJsv%Y!j7+4z=80R
z$eNItpPi_W2#M&J$S}J8Lz*D4f5?fVi?4-$mlxpFDj?&jc2L}_9F=Dvu)>Fw$>U
zQy7JUFJ$T5cc969%S@gU#oVNiS81w`+sfVM4_%zEVSp&>EU(ld^L8pdiIc#5~$g@pis4MT0R&$U`uedxH6V;*3sVv3fWCKs#_`o
zEzG8z=^j1}O|B{)G=a|W29p!|m-;;p&vsa@M0Vb?kB77Rh0y(AVc@Xf>fc$z4ZtPC
z3B$7^jlh>89HF=(XQO+O2cco$)ROPuOoq~Is9&{;fy69>vr$x0Baj(TJ+bU?nUU-X
zBchRs+N@7H;78%5#l0y*cRp8!x09F?aZw#fakBB#w~{|vjTNV+vF)4S)g+j>4Rl6a
z#pvR=@vKoBps#0&DoRNgE4b%;h;3%C@m?KrtQ*jmVVA<7;i624$Bb{Hxr;<4?6UBZ
z47ZU{9vMfN$1Id@X8mPkGVwDn;UM8Y0VN+p1yj|n&}UQflHozfs=fZk3ItVYRIw2}
zrP!>qNOy@-fh8n+r(l@&D%dArsxDz!Xm4R5jN3JWIJ}&ABP_t~Dd}pjU^0=d
z2eh*W8;3Pg>H@#kUhG&UtmNNLlUqGuP14yEI*<06t?Y(+1+9Le#|R%*x^Ia`gWd(1Jw#hV`r}A14u4elY*3DmVjYGva52
z4sMJ=yWK^TiSb20Mp689Jc}%hEc2`2(SB`?XG$RpK!2~%b{n__9KOt8@X}PPnAOp)
zzPu={DLc}r)4;9rX|tG4M=D@0$e34Ipr3C{2~OcEuhVMs0;ODzT@qlwVtdXLR2sIw
zzP#J~Rz~o`J#WXptX6wCV{x&!q8rdOtFEJ-Y)54`zW(T}+uP{WRqb1{W>?)|_Ow70
zPjsrzre0JADl2ot2kU7B&eK}+yA_OCG=_jzyI@(ZZmw)F)#PbssGiv$it@eAb@4W?(0gLRe~9
z<_&>uY71M-zyr+%L)3=WhIxJ0u2qNrZ5h**)J9WH@2c!}9EZ~rm$e&N9&)>SP-K_K
zlg3EJ?Mm;;ZRc}Zcre;NJFr0w8ZfnxCoyxgdWMQgmnA%mU5UGIzs2-
zyv|6v^>k(ELY#o!`C-o%6+xhVh9;eW&drlVo%gTPTW?X-4n4Q6_UK)xU*$Zv4?mK7
z3|tq}%~f-O6kG9yzKt$Q-f`AZ(kQV=_<_>w11?QzUICmQ(3Z;(r*$<5r^2gm8
z@_-)_ck`yfHvY=t#WAIQ{3M;i+RrfE%;v!kBfV~J?!q*auV)>IX!6D62-2bU*>QVE
zb_uQx3^h7JAvudJPDQV0Cm@0SY(7lak6}tuelY*ia-%W6C`qo2TO>dr#Qt~lqZZwL
z2M6_UBGD{r(OrqGPA^-*e-lF_5fDOCibDN&b4iCtB5--UthxAa8Ko$cnw`V@e_06x
z!mJgPn%(T-=-|M=t~Ce~^7lGEK>0qbI9+aa87AcCH^!$f>QttAwXC|1B4c1;0^(s#
z_isacF6HT?`rK*wWZ
zYO<4cS2(&~XE9pfDIq&kD1Xw=D))Cdl}2HDXJKwXF)e84&6%6;4{i2Y0k5@M&CGYT
zT>1xj;u3dIrW<4}trn}lV;ia)Jw@xs`#c9J%y;U?PZ+9aw|aH*KeGmP>Rxx~DZRDF
z`9nWS*WDMcQJSagP%EjZki)_T$Gh&NK2KKVB=W5@PciY<+via>$d~WV-)n$+&yq*-
z%j{;;);yogtx^(;u`jSn6b7->}FOduC95=*_39h~L7VA7Z*{ax7B+0c$csP~xtHg+=mMTH6%UCt7}P3qTUc^L98NVVjbk
zegwepY4(j>d%fNx0~>ptvz}(>^<2R5GO@p;RP^xSN}X!+Awrx~P*87c%cQ_Ert-3F
z{kd1gj!@W(@*s)8)vPZBSz~1E_Ler~e2NU(g^*F$E9u~X*5f4PZrJecwf%X0W^#1W
z_coN%9_P%4O-}Lez@w2ukrk{~a~#GmOY1a#VP>mgQ*o}8as@9}tW8Gmk=dL@`Zw@4j#|oDbr*;wzgcUw*qhx$*R*v
z!w`FI5Lc{VA-4td-IGn=&_H=n{__Ff$?O+?d=1tb>ol|iFuLCja(|Mj
z^?tO*PVH{lPaoSX2gLTPwZY4?l(lM;&7buE6N2N^|8VUOH`o7QpgL%BXsABE{>$1b
z;tF&KO2HvWnS8D`Ia{c8NpbF}n&&x_EK6wuA89gc=9gCdrxF2}^nOj=p`UiVSej5o
z0@S*3i{8PX{>~l;NBCKS-FJ<)K_tlVgi#WoKewWZ6j5*5Bn|VLP38IoWKqzX!?bVi
zN6)Rjz*QW$N&_lbp?ee|*3q5Dg)<(KTn7lAD=I-ajaHzM(kWX!z-QKf1X?8_#|l+hy|peyZtK^#JED>k~eu1|c20`|nF~bCseA`3mz?RRvVE
zcitDH5O&=^uRAk*Up*3WFMmGb@lD)Mx*Dspn5=-VsCuC0{xT){czsyH!0*`mbQ){Z
zX;Kg_z1sZPwL=z>`83zx8}#^#w=!9gkk>)W&|3?jL=W%YS4Hmf`C#Ka
zdv@q|ieHG#E_BW}JJPkDPu35+m|ZC>otYGG?zii$51RUX$_~-w7`OywY*^UXp26Fb
zzV}gr7xyt0^-Q|;)xG~r7iux0Lkv8wr)vx=ZYT53{4O#YD?eRb$<$SV2J_{h+-=X>
z1A6%kPDg1~LyF%pBNNu8gDBE}_8%39f~VP-n-LfdYV|5RE)@KCB{Ey1n?S(8{CwxB
z6(%^hQJX3krPq%b811SmeiW~?|Hxtf6ll{UQGsx%qmRfLTow8G;&|*|{MIn$@eFmA
z(T7I`%JNK2Om@yUDKsz`hgsvZvhpUmY!{W342mO~o>v`tU5@Je>l1*K;T7(5E-~FP
zK94~fwz<1Dn#^eY!7lCJ(zLa4ax@T_h!ihF{|35L?mT=@IdJ=+##vh#Y?+tzHIE;7
zuhjGC?go5)_F!1na?nC=><&vPg7HO1-vn;osM=b7VmUw(aqC!j+la-^%3NJTh
z&lJ!!(-x9%*+Zn~Ue)8Lg^2pFPOz7n^AA@WBuOcg2$Vz_wOc=_+O9Dg3`7!_WNLF?
zOEox}nSSJVQ~CN`t+p0;O-IXB-6>2?-m5lT1U~4p&cJJ3&ASH9)wcLSM>Jto{2xW4fY}+8Ci226KDl68jrS~Qb%?h$u
zeahbx&#v=Z{G+hxc7q}-TIJ1hl)&+6QcL)auU;AXWu002d|#oO(flzo
z?NMzo(QG%Cvpy?IBP55Tsn5zvL#-%!SR>WHRW{d3_3UM;{jGNxaGc
zL?s}gNwhtwY+~{Q);AFm%73fLa?(eimQjD1y0N6#?>qlz2nA!hY=oVC+#%Vj&JxV$
zgI{o^YCpa*hgtq3Dn3)8sf-+%*_FF~^*pQAQpe`iRNINA
zlsm9pfP_c=o55Usm{rfka*2;UvHeZb0cV)uN?G}7Hn{LUAt>sM(uc*3?+a%2q1MOr
zjkt(ARol@Sw|j4EB&r!p+^UH8Sj~iu=PpmKSPozH93RY~7})I1Z;ozIq^nwi0ex(L
zH{}Q8MT4f2OmMo~kfdwhx#otLw9}2k;Lltaf5d!LB6=RE7_W3E3sh!NLDochW9JY~
zqk2LiOk~n+JYH^fJv_Nlpc8OCX)MQ!eHdOBaa1NeFLWg-Ux_}|jv-nr?3;LVIptHk
zU2(l}6gFJC_|ZRFo@MrWJA1|;d*py3z%gD!7X^OnA&Osa$rHmT{zo}_uRxlgNYLq)
z!zbkja{|K+SU%c#@4Ptm@$#9&_d@4mjq{RB887W;yH>|i7rhxsH`!c7L?j`Nj1;%|
z-OQrXA6b~4HxnWJMwD2jY^LpMS0KPP6KE(^|%ygb_*<4-?`j$OC
zEK=N!I=y+(?>vp6#Q$e4Aqqgt1?F+n)}de&)4)8U5K>r4Mq62SMC?ss*fWtGArLRM
zx`dp7d_~>du8TLPYd>E-PP^PD{4MZUCqg6O3qWB-!
z{V&+?@cyhfuEJ(x`0N~YW)rKyNdaNe(ecul1JY`0iDLZrmlEPZqfrZrjzhRIaBHmR
zKT!#}?UxF%39?g3&#)5)WVZ*Rgs6=F?Zfq6j&z5S=e<93Nmjmj#2yAF0mbM2aI^hN
z5b#p%+wZ6xo@BE-?U+Z!$T&vnb}zn`n))S#moO+KgpoO=^Ksqtg2E8N^SLmyA
z((fc^V3&O&;2`z8##*YAV_tKz3Z;$D+I`{+Bm@F0@!1>PDg^u8dF@yjG_;6O{L>xL7L2Y%`$`-plzU
zMQnuZ&;U=^wwkiu)>vV#Y_jy8in2cTBlHsj;WzM7o8k0yv`h%fDWxu8+{WFcDbfGs
zX`aFEgz>*T5*^1Z#vO^8o>tLrv99>+v^e!qW07x4g0IVVtv&5><(JeMIL>va_%#T6
zx?eVVcrJkj_vD>Q&QDz*{Wj-ht=&7bi)m~XcW`Eb98?)j_#u_4gp^snWr2#f$w=ql
zV)-9&9VS|I5thoIftgo!x!$A9c3rvA%w(#&bGkvcR8~w@WV7RVW{)xdPNC@X>J
zs`ULI`SACvXfAwE`|dy`$g={02MbeQMWD?b&KG}kGddiZGRQX+(weTn=6ZWMV0-b`
zHo4d;4tjjt+T}{qTW)`gXOr6DN>R$L?)L2Ad%%r~#Y?RowIQD}K4-CJr>z*!wp#Tc
zr6(mCBh06--#pGYi~%l?i;LOLL%ER239^RF5LhH(VHGYoj7_xk^tV)=S@Oq7BHMEH
z(t73B$15u;wz*g5s?&!3A9FW&eV&6*u0;M~#h>(mhw+b9w<8ovW@Z?9v8`8`V3tH7
zIZ9~|-Ij=AT+`~rINCxIVFdY4LrtsHxLPLtn%)cLlH_wM_bJr?S^u_EF$#%l1c%ZhwD|H3bM2J=^3L<-|4|^Q4o?Rbc4o7{B`~?)`7pmFhP9eX%k$GJ*3HAF|6Z@4hpm
zODFtz4YtY($(sUs-X4lDOw+}tFDnaByM&{piTU2&9M9-R6EUnP?@et|1c>nBGSMc3;X=*xFy!o{WJ0|SYMv%yJ
z^|j^nPuV$*wk$>r2SV#ac`b715*_l{64h{*?EeZVq>#T!!@3JG4L)W=GoN2#-*BVg
zVNsmG&YnrQl!zjb&a4#f=8{Y;|AjVwFr1L|JiKUsVf-i9
zelSPBWk=V$rrZBIvv_smUuZ%KiBUWQQ@mO{lM)j}^KVe(0s~F|!^&S4a}_Xifq4ps
z!ra;a(filX5#;E9(?{yhFYh-J#qa&F=>8X7|Ku&{ZwLR4O}`!VKR>l}oj*jWzMwRM
z7nc-IC;gYhb%YM7V>g=@F<$xKA@z6BoeQMEs-k}q|F4}9g}MoaNFum7FsUp1XN>y2
zapAu=uD@(V_#anze{7r(x#+HhQ0w9e{eR^R2!tSVNP3=67p1j||DsnZ20myZud}vH
z7^B%?GXM(*OU6tsKPWi(A(6mi5*w$aJ<5Az@F%4b3Bt*Wi`FzsfvlWu{d>HnLCBtx
zZA-J$5hfHz-h!VXDr~&nIg>O3_4oWb)hFX5CZSJ}x51a?vNNt%fOVU)=4(
zzU;ix)HXMZb$!FCy7G`o_1VcEOKVWeAr`PI&OQ(*0yO}-7!B(`N*Zziyp)6?GPuvy
z97P-Lml=MsDKn2mao}k`W=h)#6L5YJ-Tf9&<8&;%RJWbWX@!5>1l+!_nW;T#bHR74
zdes-C=aHG+v0f<@+EdZW`68yTYNy71TOR#@PRqzkbI$~iikh<6{6$2j^r1YJGiQ7>
z<()BdzOB3!|NBRu+iZiLp9P`#S
zI2&k~DcgFtelM=UsDF%>laWDltZ6^*>n7q{rxN?#fp;>nRm|w_78^yV}f6+h5dwhiL^U*$f%D+jRB_Q*)LCehgsfAA9kuU{Ig6_d))B+21v)`Qvab^
zfnA9K249jJ*i3z_VOKYxQ^A>wqF#HRfn94lDhx=vK4-B*K1$vu=CRzv01c45UUFC1
zzCU_b=lCb_QDBN!9lCp<#WvzEC@85KI=)g&f10458Gv19OzLPum9nsCY=0S%yj*-+
zJ*!qTf7;VeHi6b4<^l12-WT$@&iA^Xw*)@U;w9O)vd7sngh^M(b3K=f!E_pG-AWM5
z!|HpwUbpU+CEL|bM}Ii(Q29BcHVIw*?m(cp?X&T4I~NeF7w0l2x&hza4q^m^sUf~s
zget>(;^M1+qfH{nHkzxu_ZRa-z$yc*T)9wgUa0||LIiksjF;cjlH>$Y*@Ad(1h
z(S54bi3+GI5~?z2O$Sgl_xjjS#*gQ!+613wM}bD`#!C&RIhn#~WC#_yI#!)8mjVpW
z6b1LJ4;ceIaXGJ#WDlp4Z>5t}28|yJ*PMfs8Y^LePM5Q~S1O>cZ^#7m4SSkx9U-?Q
znD-QZ-6w0hB#h^6wH_dpEYxG4GMl3cqzzw6r9PP4)pPR}b!489{)LZFViGqMffW`B
z(DHuUq*LO@79NCfE?2EJb1oUb|E7C-gss0}(&0{EC^FbYD0K4n>QMM43R=Fl9ETw-hKhg4RRbTe9p#Dz6q3Fa)V
z8ny0gE;W%9CPrPmS*ZuzL!sP=1(047u&g1-WVRr%eL`~vVN-#5qza?cvh
z&tVUN#!s3^M^?81>t~jc_CyJ$Wn#iK9c?Y}G2oUGqkB=sp{k60kU<_nhFtvKk(S;L3iTERap
zA&KVcj&Ob(&G;Tgl!T4AU7dJ&MOS?>r$*DcQtS3akajR8TO<6GW7&hDlR@aI@aPy&
z_0-<_E@R=W_J=}#ioWDMXtDZh8+HuD0K&jGfr|o#{b#Ml2F-@MeBgj5`%8VM=6VAT
z!o{>Q-=@oLpg$Fd#S;ENcAUJ88$a*Q0j@)l{185X_m3>Ci7m!rRN0YI48y^;uDjgQ
z+bV5y>y&{IaoR%m@CZRJrXl#a~lUOADZ>pnnkdwC*Z$-{;o2u~o?j=d5riKdkgD
z_J8=MW=Xi%#bERS9la8aUCyczJ$7aJ7kveW0uET7;N_1xs4mlcXo
zqdq^5x!ACa+)A_Py0rP$nXPmuct6nRRwo-1Jzf4eVI+K)4+EYLO3f~4m8zlzC3uNg
z6ra1ixuh?>N9xlt4)wwLQXybTjF{NrLd<`cIkENQ#(j5onNmv`y%tG2NS2?Fje4_3H4m(q*6lcN!<@pD+y}@BI3M{db}Tg+#G%Hu;@fhJu%fptsiAp8YC16@Ri~R{cKGmkct63l7^rzP
zq)iV~m4v#QW9>mAx*&^HSwVGh%&b>Sw?o#1G9!rYQ8$G
zMnOk?2`Gxb|p47z&=Rzjmt~V=bE{5@_Tj8tL&y2<*P2
z)?W8f-dkPFCN_ONA`oKWDHT|IX@Of>*_U-+(;Q8NT~kP5ytn)0KvdNQh##dST==Eu
zbdq^{V;SN6^@;=xt%SAe`o_iF#h|1#p4K4lYP)6=f9%PKwP$gd>e3q{YImz$7PTff
zaOy2%n_@)AQ_6vIvW^`YqAttL?=^{XB1C?iB$6XQ+&+H_gN@kyP?y4YO&neFT~E-r
zbIWaj%%A_<{N&?>StXg5zWOdJ-U!-ulf|`pAavoX*8L5lzX<~3`&Hj$W{2yucd&}-
zkI{y{PrDj!zb21fUwafk5PokoZR;kio8(fd#uSmDV>pt2gk(aAsm_?S=aE_ye;3KC
z57ow7aj>HG(G`2Ik?pZ6|38T3~cM3}1WHN9Y7Fie}?2I@k-XVt`4
zIotJiNsf?d82hT_BFa{?{)SK{O_OeErgB|tm5so?C!lQcw-I(2)G{SAQMy1!zsDMe
zUqUf@XSaanD!`TH36UxyU!*QYYITz>HjCw~u9qDD1*q=<&eyf9Aku#qg_>027A&aO
z2pxv+=Kao<OoBXUl~*m$S$nAnoP>|c9$6r<4F-s7*y
z>e`Wk^K04tKjY?y)XG?ytspLfbanD0!lP%c(7&CiwB5OHpYxz?gHk+|w2w>gL>hxa
zHax@5l&+HHZ`cw8QooptbzWV{c^vFFxf9kY*&4OGX_^+tEps8sAj@fdkLsnT^6-`_1P^970^m{rX#zi6prCPsQHZl5b_4=GtN@*Q_Joki`#h{oYf}`$AlQMm<
zP`&XCVoEnwekZZcqDQeH*EU8um!qUa(EqOaRw>zHG0Jv-9&vCT1B3~I
zzIL&OAsW!n2XlHiiDCzCLJ2E#grK4-4<)^S894ired!o@#)P%%S^_>JF*ry)hHR|<
z=1-0^iChe4x|X2kM!4ZKQ=3G9B<6C)p3G4^v-AluIo1C42~$YHfw-%Lh`*8P=_L?0
zia%yu;IY)BcQpKvz6qYlm_i|5Q@jT4-CvL2gbgpGi5;Qg_w++tHju
zbLwMFK$5ZPBOfE~RM^Oy7|D6^Or)yTulBoTxpAMvXD+)YvVmr9J3B`r3*X1Ajv>Eq
zlcfN>l(LFXWC#0zJN-P5RGG1rPqf19WH}{FL{#JUq9kBa`PROoM
z;J3TvI|C-uw)2eL`5mMa8o5fXS~v~>ZSjvEd4yY_oA0eI>9u3GQ@oA7lVcuo`8?&z
zb|^Rd=dxpSxI!9HK+{Z>AL@;S-B?h^#BCUyr@1P*?u$LcI|#Gxce})9N0k$n`<26A
zix?OY9JBQ{qd3-3#A-s<5fw3MBO^RXI+PV_r@n2bT&HMeKPdU~e3xsCagkf(E^gXJ
zV+?HG4_UC`@FYaV|D{V;E!+ey3cZqK_2`GeTjyJ42`OIxHUfi)2A{mMsI6v6$h+XQ
zouzpMm`C>=4*Gt1E1PrZ+S3cWj_m2(obz#{Geflj3TlvI5PAAe)^e08Gf>U)#JKkT
zuEb*;d%vN!H2AG)eWB)=Z3?RYUE)5^noF>Xfkt9Xfy&@CeKyC-!;65{>sVl8UpTWi
z-O*{lEd!QKzJPr~9@cNBxiO
z6>Zsu%U=oc^9Iy?lu8Q-_x2Hb3kcOO>KK0Zer^UYi!yG5FEi!U2%?*i{)WhcJBw7u
za*gHBohSap7ixBkhcIsLEjlPhFtRG`*jJ52hmtWQCxAvB*$_Az%l>!tgMAcOBogcj
z=IObk`!EecWgr^pvE%W4d{hxve>y%Gd(tQq=)q$9)!ja{_sxuSzW4ooQ@g5zTH(lQ
zL0=^exqp^AEi`&-@S;K1F}Il?TWC1$0jf6bn#$R17USGk^No{Dpa;LarCv6E`dF{p
zfpJZo9DefOS8hI&cA2Yv;Dsm+EL8$
zyp^5vd3Tavqq+vMl7G_t80~?v>U43t2#+PX7>696m;7xJRz~7VsOJps8SX>ROP*wo
zn$w3^MGgBu_3ph%R0WQz7ZGWkpeLO18NuTGXy*
zpyASqob|4gv2ZE?LgPBCs{716uT`Fb-E4jL^cZ88KlzMD3q$4L0GIj5vcd>SxcVz=eYZBpwN18u01{c)Vw;Uj(;ce)}YC?J(Mk9lvDAg7ixc>p%-?U;Tpj9EwsRexhZQho
z=kuGQMyEw}17R5*SYSCQENbn2WKY8J6R6R0+zb6UPD+2~tat5=^iBTz_Rq_8YD0FuI)$c&01lJ^sAne8n=QRY>$mov+6d
z8E6U}+UzErox!h=+YkmNEZ`uwIbS?_C3%{c2N@NA!ruSXo-=c1q2IKPZzr?{x*gmL
zxqC`P{UcU+M11}MZs|CnU2d`bvua8c?~wHxX$!-O1wc7y*&?j9NjuujJ$-
zYpgi9IXu#H8I|EpqBV|Sn)%Qskz%d1GQ4hG$r;ynP>o1XE5o!Ni`%|e6jBo)&K8Tv
zn7it7bJJWz0CzTdL?W^PiTV~ifHcw*Nc9*50<0on(Sa`qlFlsr1eeuTuAI8sOrY^C
zHOJIks$?l
z`n6UiqHC)?;7&g&SG=0V;{!O^kGz~&EgR#j^F;5wT2$}XUQOD~97r)W^$!ws=tQC_
zaZC>9)uJ~3o*IOJ~*v*J=tG@yV%+^I_c5Wq_D^
zL5Y6j4r5fIyVpNv`SU&yFE1x7a=O*Kr6Ht*M=57qSB;ifFzN8@%+PR`;7dWRPQN`(
zxkq6am#!u(65c&#K;K2W-kQJX+jWzrZg{g%y($V)0B`>z8$Z)De=C}Z}!fs-Z87pFL3;oadM{`#u$h3
zHPN5D-!HJcsVNknOt6(5joj^O5Tq90s!d=7%CjN_Be>c=CT0R-bb-oP;xJe*&UjHhAA&r+)E%o?l4r#b0PK
zwT@3e8PF2QOa*bu01#z8@!+4>@qz*^LiOoNDMsG<>}5$|NBfL^1>@oi%6a4F-g2D}}W^z;qB$9di)D{3zO2^?tt
z`tX$@0yH}v{=OE%r@AV0>mZ9z{-+87qdcClb*vtLO|O+fEZ6$ko>7|+#{&tMPwc|(
zCQ}F-6G`E`Rz`?e6;g3rvUO=|8pd&>}LUe4ac=;V_uFXWDM`si*nqB
z+1es|{Apd4FDS>;c^VXY;;P!r(=?#oN#zow=ZgLM>Ri)tdIUawVtm6pO-R`Jo&y3@
zWZgBsZ!f6n64GroDwtSSp@SO>jA$}v(?7-N?mH?4qJkVub`LB3+ceUMR9MlEM4Ef?
z(%b5B8BkV)J}uV+4y&8WewYEc9U6lHa-A2f
z_$L88-_hhOPVDpK+QxSf2QS7Muz2MBYQs#>TWl23-0;ZE7@=Ql)a
zYMm#%i@`M_rl_MGk&7uask~Jpqw-1*csa9>g%fJhUbXG3@+s8CpSD(JCusUevee&@$
zgst&KXN5jfjN+KzX*EW(BVL$fHHDhx`GqTsyavGFah)O(TU{I)7Ml)B
z7=+cE(RV>g?Zt)CJb;
zxvr;FM-v44OByP@`~zRfF-iy@ANC
zf_Nv=)}U(?rb4l98;+b__qelP-oTav!9QSFaPc@4;?;63*Pm+b(jz|Fnn50(8YhXb
z?Q^=Qe#%j_&=ZXLlH2hVWsHipuIU_*1%AL?9TCO%s9s=1mwo-0e`Uw!Z2|wSdr*zu
zP$;O%KMZNsGIzi;cUe`N&(#nWOzkw1wT)KD9
zaLV$WZz>X*HS>y>H`
zo3SO|P^ud!h!03d=fuBu0cC7p?By1Uk70UtWwKHC=9TX;0Z#HKg*OfomdW8>JeI-f;s7TlrH_z)VRH@CkM3R3$R$yoPu@J
zs%|+L*I^zW5|>f3hrLr2$;T~{9Jm`Fr9ougrFcB+Bpu8poqHtVZE=VVt~lUnR1dDR
z)bdIjCIhQxXSTd6Wl~Rqrh@ij6zzt(6S~Uk?Z6xp3==V(JV`gvO4XOmbhET7O0L$k
zz1Y7)6>u7VcF5LP{7`xS)Bg1FlE?(Af-&b}f@fZ~;MguBe~>&I^ThXd9pgM$9icJs
z+lI$p;6m3d3&1((5fv~X8_QzJ82k3zal*HnxlMx*#O{Bt1SWjiBY@-`WnVES-_Kz2
zJ*a`W&r9`s5f8Z%Xgryp5GNuZMa^AwKe>2f9Peu5bRh$;h1mVl4K8$M^n}*MT|SW|
za4T^s7zj7Ic0a4&W=-p+#G3XL)$|W+G)gkIj;dbT!bvcE-ZY+LwCdiO>3mO)_R<|h
zD3gSF^bso=i{*J2Ae6>a?pPDBMi8Mi*jfLuyr|Y}E^z3}PKiSM)JXv3pe)-liW3G^
zRPnVnHc|6M^zYy|^t!DWcesHi22*{A{ow|EdMsDlAp6r9Q^D?F3XlS!k=$+B;HA)#
zOBu8@l_sM>)5J*Bu9npImq2FNuAY7Nss3RJ>4iWahDVpY*Pi>Ho7%e>+Rkx5K_lDa
z+$@Ltb>_ANA|2b!@m3m9&xk~+NbY)Hm$NA?-d&N$la$*-K}Vwexdy?nGX#eUzJ~J)cBH_uvZclmR1hLPXZ!3Ft;hz06Z}**~
zV+89yW~U*)fA)ZbeeFvG2n#Q44vUAz%Pp2>D6ZzrObFuvPwCvpb{%YyTu>`8%Pj()
zZ#ug40%;vn{^ck;bsA%!2=saS1|hzB9d@6@Wi1L-SAxvrLj+9sdjSJ?Xg&JQYG_`i
zjYgIW(_;!(>1rR_O7`L=3D<)dvVLvoJ6Hvu7+On>%<+e-C)k3Sc_f%E!T{#e=M?v$
zUIWGsu^B>GMd5i+lFz+((idM>*-EzlR=7_0V?d4R07O@$dS&XvSs3fJbC>hiaW+ZQ
za;$DlbU0_o+GV&Kx?_>I^AG!Ffki{VYn%>aHwp5hTJ8?X-kzq%r&qTLm(wd`Vo=`h
zZ5|$MiPU$CaqI<$@Sy9Ry6|*)d`2!hH_J)^&0W$wo3Y6aV^vXVe5Flsm6f4ODg6Aa
z$VTICPf!8waDGtSsjP~e%hpNX
zUY{VyQKUGw6#NRvZ-%tWlz|Fzpa_i*u?!9ThtHNJtx4!AC
z2w34;t6g{vv1fG?C4M2Xin9HVr%ALRUbf(KUeLhhwm5Ll>fJZr(-yUoS$g}Z8HyGaG6U~>D5~qq@0Heh
zk!Q}-A7IYZ&ZKst{8Jb8t9|eGVEjf=n}z&lU3_6frAyJNTg55=pk4!$!PmaKNt-T%
zQ_#K5%ELt6tPJAbQ`Aauh)%*zgN^H6Wgz0srVlLhnmM2+<+L4q7*OyO0_+U-TT%Yg
z-V?9;=TDYVtW3xZA?)d+HPdpIt-PRPC3Vx@AAEw-lkb5n6{@^en$mm)PblDu)A^dG
zmHow7S6jl_s^5hKZEQK|vUP2>(mmbgxH+yM*NaQrZ02bvidzKYXCFXWqN8Q~RqsLX#
za5kN?sHoxMZ1Ig0Z%{$Eb0+r=6b9cV%tC3))x)A>ezon}=9QBBWI4_xh~!)9~cAkAw7XTE5rllkpGZBYQXux8nfR
z3cmG}5MdMd634NOD%kS*U(m?p7pTMqON+h9Ug`z>YC9JV@|y7m?&MrX-aH9|T(X}_
zEQA=+?o3~(ri$epEt{m}=CnZI0a1>ZL7F_x
zh)L{#_V9~lmfPnxqM3&mD2->m-JR4K8N7|NV#>4e*ITrQix${{9lH@EL_GQigdZ}C
zLf1(q(SEEDw4A9S=Z$0NnGQW2GI#0PyeKL*e3b%^y@VD4Y6cIAT0?70fD&0l&I5AS
zw{s8kg<>s}A@~2K5%zxhIskj=eA;Lei{j&sr
zlJ}8O^$9p4{$s?yA1c!Vazl;E00F(R5qfNQXSi7{#dxm1&0+hTd1!1TCiZGi7Y~bQ
zc7g&K?N8O8NlNB#%}z(;FR(WWW4g-A`9|dbMamOeAxEueFdF#Pyx>&NGYyZKMi;w~
zF&_8Ju^ohXsIRsu)wGdX;aQ>DWN`?6uv!y#MML!8nwaTt@4!}9m^yKCtK$;U!}(}}
zMV-W7wE)J+x193lR&Lar3=mo!z$OkWavDh@KL1TioK}JaBq&QT0jN1Wdkz^c`+Zj{
zE*O2T`XGnKz%iagt$F=Nh9Cd8nFv9$OZb5!l8uIAOTK+yJN;RgJ^xisr`oBKQ23oo$U{rq`qE^zQY$hUl^(ym%;)ae-!UEAqPj`?
zxAFLUysyT?b*Sy^{1+llE=h+XSq`4ePndSw(x1-;1_rAdg~~q9W3m~Ouw)ml6*zQM
zIfN$b(E|R|ktWkhkhl_IhA)#-G37*!
z-F=RF_r_02lckZdc5BC`Z)aE!R*zP=92S`hp%FiyP=@0a_{tF5F6u3parB6mD64?<
zdX2&?@@X;gktf^!1E-~I-rfT6B{d~XZ6fP-3yghYeYYY(|Ga6LtM5XpRe;4APqT3s
z0(a$J^zn+b5DRNfnQVx)&QPbp%l4#HPF-~m&juznJs%ZfyB3+J%Q5Jky;k!>F3Pj5p3gm1}=n+2)f9W7aQv2u*FT=TrKI7a2hp
zWIJK|i!8~GojMiWWmG4wi8+KNqHXRrph(%KagFwVyUQ`bFvnkdvR$LL
zw;^((kCL3Txc1&wU%-HdV^cd&CRjiTo#>B{p&D1B@v9}3$z3%0p7-W`Y2hkOuaSC_(P1eyE)v
z_9pq1Q_oA^=iy00mneVD{l-Y9%6{k`jpe%;@sKh&;=pzsQ`4#Sa(U@;spA>2NKJ=o
zy3pS2*fufYQYh+hZM40HI|%|s>S_jRjNv3>2H(FGj_YMLQ
zT@?bss&YMf=2YkBri%valLBGNRG;I(yiB+K0avM>pi`jeDbMqTrwLg3zOL(3bXBso
z`nLHc9e?|!K>+Bwdap_JwBtS5Samnoo5CYZI$DHL;LOQG-r(GX6D<5T5Btw4d=C5o
z#BWDO+_-kTx;wV?O@K4OvjNE$4Y9n2GGE>f6Pq6ey{DkrFBo*{Dq~I3hY}d@UH7;A
zMV`R5yak#l%XSF&;H$HJ$C7q^CKcP}Zm=n&=QPV_U-B#y#E@_^`T|y#+{StP5Wj|<
z)8+OCaBdT~yRx=6ZIwN_<0jwiKrWp-*1_W^!ilm=fcib9wWLU~VHl;}7W`@3yH9%Y}4
zisiDL+Euj{zu_reU`T_2-hZE1=Rf_n=x3t>64}|{xac^J+wd~uu{E0^qy#;LkHHaj
zbl^>Un{G8DhCY}`4WABVV(kQ4Q-6)MuYbgt?Et{ND6i}OqvkPJ!AH&27dwx-P_PC@
z(Fm*7WT|`Wz%z!p>{Mvl{}3g)z(&o@9)@$5d?zVcdD@XN(+uD|{1lw+!H+vaHM&vM
z4WWM7-H6rZHVLVGcJkE4}`i|K}}bCcwQPm6;-0cr6;QgN2g8j3=}W9)3Xa7UYmwZcWGUQekNH3f$%O^s?1?
zUEG?Y&_6Q?fi#=}SrP0DK}{8@@d3+M0lLD=G@QH7Ewb?JyY<*C*=;#F10pGi#{C(Q
znzNs7U4)Y+O05I=&J9EP7ZGglDP?xsT);fyA3_6f^utOY$dqmF*Xq$R^!bNB1q;u7
zYga}c@m;B6%=H)Urri>VKc5jribzBbeY&_b_IW+vhF^DOV=tA%MeD?O#Z4oQHS(7XbKARL$Y=Z51Q
zB+~0v`fJ>=hKnp(Y-T0?awml#yCnU<5#L*Bzs*w8_eiRY9knMiOEi2!2)`YYLN4Qr
zQ>vd54Nd-#WNnl+c)uQ@;M}ZQr-I<3;J>}oED#S$ux%^C0QA1Cs{%K9{jVr+w&MyS
zwL_6KEozU@iu#2UtDUHoXJMpC*C7~OXu51DQ0b8laxm$bNAWBye~YAC?cBEuKkU0o
zY{N2<(;X4qS@)o$DS*li+!BBG!9CkvceEC%O{~tC)~P6RVVv-0krBb8E7O*e+AW)y
zm5TPq(`X@#r#D~{Dnc(zbvG5(cs&Q_I2e2SN7_uX0GcDhRYE_-tk7LS%NS*T5PqXt
z&R9=X`_62HDZ{nkZWmsAI?Zc3YA^e`#W(iiO5X9s6No~Po8aee4`
zQjB29cz<@G##4}QCed5D%9ZY;ygtIFSnWI|?|v77D}d#ip{)(|OU6){uIskm)8zyt
z`20xxh%)SK(|)CmTj~;Dj5Lt`t}m@xTtL_yYpPKoG&20>bcI8MELT`3on&_D5rk~1
zKbf($s!}z&3OZRNrIzj`|9G_VB?pgJH9Ai1c9w@H-;kzfE@ONSSu&2dKF-o6m3;hl
z2P=(=s$~ad!4tOr@4
zAr4Bf_HA*JPH}d@ZlC~F(WpQ6k0^VYvR~B+pvo<1`T6NZzAd&{Uefo$OzPfjacEch
zJA#&1m47@x6m|wc$%w<~VpWs@?2sW{uJrhedd!{}d?jN!ENH@Xzt6-tHVZdxC=j3Q
zqzeEI2zlt($}or^2d0KgjXZ8n)XU&~9SU63hj0s6po*8dk`ov+e6E3N?VSFWgq^0S1BxGfijKr)|;3WK_mwfDg{)~$Ft`(4t
zKkx=A`~e$U96eslzvg@OioIXS)F?0`y{eSo=6;PFwhspUnT=ad%h}khZz$no6A=)9
z?B?Ur#ilDb9{Rk`ekV#>ClslcRkn!~*Hc0!Z<(t!rA>r}R$RWM(n<48u0D?o&(&21
zrw@k3nHa0!3g)qc6&K4#lqZ)<+fq$UV=*g-M{19eMvcPRQ=rM{S00?#2DEZ45DVOf
zvT~>rBXzR4e_c7^*Mao>@)#wEc2Ayk@rqMzbzx!s=VJOS9phQo`$V+qAhL+X>zZUZ
zd9(n*IwUMCbSKAkrd;LYuWEhkx`;;-#r)->_)*M%%=LeSSbV6RqA*KM*jQLYMHsjq
z_?q;r?w7vl39vp+1=sk~!(jLJTtma9Oamx(Ee0UU8og(ZdtdxT?6iOq$bcnPP=Dk1
zpI-N;q~-Ru*4J)F#-RwBdqPfyxTXA+bvvJ#WarCm{kL6IjTs2pjRN_`B?{cX_%D0=
zfQxnsn=AM3ZRKx-5oW99-3Pm_Z~SHPS_axl5P9Mz4#M0-?A1Ol2|ZvS;*JcEEC(OF
zaE#8~zBY5&v)y)ZCuPxqdFQO=ii4%%LL$H#g>zt7>9yCwsnBv#P(-E6O;9&n^wT7~
zGB7V=sv6g`IT=pG-nqi#i1_!=MXNwNW8cODt74Xd7;g;`1vfu=aAs!%0B**
zADRN@HIk563vtKYFQKZdnGyF#+hdb2+YuT~0X9L#txh
z4BBN>$CZqBueHKg51gYb$Ogg__~;m9Myj^8BL%ewjW;xHSW-E;RJdCm(VY|DJn8&j-
z>(5JGuBusf(r(ug82INyP}u2V|~bS@R!)J9t5?N+`%;x)`tu;oigZ
zF8n#UM_(nvi1!iy$B+8;*_98C_Qwk>xu9OTWrnfse5bIRF{2zHl
zjdES8Gas&%oz@DpO4KF?unFVB$kP5s4oneeZ4O{;?gsAI2GYL4@>3}?ZQNI2!(1cR
z3&^`#^tOzb4nO|qNO+Feq60)bt8#F!q_9Ju!_WLOvTJ$LjffuObM^}$mcHpYyR~kW
zaRKnKrQ#)ABU1f}MTUG&^%qdax=ZpT*--7HAYZ%WnGgT9C^5Et<$h?ym0Xeg_cPLx
zW|xz;hR;P7L{G|Y5lp1UEltWGT$?wBtpXx2-r6Qwcp2-AEqkaXu@_G
zF}P5FRYMJ9I8-})+*|cJ5D8PNXkRJ)3Q3c;BvZm+f{ifbc#
zP3%H`a6<(^YlCdJ5DGHs1ZX_Jlm_`7YbMiKwx1uLJ6;74xbI!CEtF3JsRuH|t0Qs3
z7GSXKPk`g_E!Q1iDCpG;^}?30eAbi3zP__PMPB>J))KIY4i
zaiZB(a_>%VJdW^I_#RXK+ACBLC{*N=Rp*U?)?Vj@!lr3|#(n!{hFHqx^Vs{d+W3Xu
z{p7`TyLxzFy4bL13<}%%|8rSvJ`OXli+*Uyny12+FSyy5HrJ30jywU#uiSKwUT#iR
zSc<{8sM;qmZw1RV=oO9qd7QuZu=AV@8?3|Ukd}3-J)YO97xBl@TBf`(t}{emdzxT~
z&CnpBv3azeoZcDlQrR>~Ta3kmB*q=iH{JhAkB}K?w>l(}q51~I1cEQTe_hVh3^=Q*
z0z`I9w*tP?{EEr7QJSpRSs-8OHQ0+QilPF;cJODHabmZ-OP}LRu>laSfIxpaCBw_c
zr{~QiC)Ypf%XM#Y)Qac;dWaTy6!O96IeBOH{?bRo>
z@UZyUp09_jt5+${M4(>t@K1GGmcX2iF0exhZI}9=ikCg_v}4+x@EYfoz~buZ!v`Ea
zPwD2HNl`;-tHEeyGCi_EjP~J3$=RaX4YAUo@6I$xrPIhgv3dq>Lez1}g`sj@K
z;h~Mi{*ueH7AxqcU%}@kle{=h?HH0OcOLyVpSPg-{_yL;vpq{FOS;=7%Awq$EwnVU
zZ*H**-}6?>&R&PRCQm-)lZxELu5~ghsfy2^e(hI?Jeb$yx`=3Ax}*Uxna
z3_s{fJ|L?`u$^Z!L(Rmdc%~m@YLO8)b}LZ}kSeNw*OIqFoH3v>|5G0Gd|nqh>Fx9@
zK%9x0M&p%DMP9-)Jkk-YX8)N8E&nCsQ`({|p2U;SlJ9yIud@MNLOD>E_f`!PAO;ZecrOf94*lPM}IXH()N1?VCpTq0hdQjY3yT$wjO9Y@+-+cmR=M8(Zo
z$PB_D(Pk))CNoRyj_Pe|fVz7CRKMCWKbO^8d!6nGKEzTOPZ^rVs|1HaFGW+{{GP_J
zwdD!(GMzr9b~ha>F_FR{ZZW8*L`}
z7a_OmTPi?;0xyAcGYqLuZG3J6Oiqt|M?VnabAdyn8iJWGo`AB19KO553_2O@igD|O
zMiG4sC;bs=nEzJXQ)+J*<<3M7msOY$oTB?T+CSVQG4IDtvUoydZzNC5RuESSeLt
z(tc{HJz8H~98h_E#C|))XWi~IeYMnT&V0)l_m+9QK2us#tnBzZTTV`*YGa2AjpV=f
za$FHxAu
zKIfk(SIC=EvFS_Tqim3Og)<}uRTMBc?Ap&~^hRUa!&i&+pL_e?e-ZlrUi|EHBt3-?
zv`zET;s@ZiH#0^B9vxKh^@RYG%6~&u&{z<(oB@XpmCR`^`Gek3%X*e1;(9Ei`70cG
zvxi1v|7^%#RZRVbPQ|gczkcDn|p2e<4pzag?iJUHjQEcyK{ik*+O11nfrfN
zA<0C32Xc@BxsR*8HSQ19HZzn9b=DOG++MQPtd6GAmgjTizhS^gX0%sfTU
zbjUf?u~5pojERr!SS4`%ciQh5jk!Gl?bqLJiH{x>l8cgG*~9pr@52e|xSAm<^}
zd;OLkwI9U)J**^2;QLl|dwm
zlPU1NMFIem+nE3O^slE8P84#3yNmeGIWyo(HJjB1-tH~Um&zlauR~zzM&EYnh{2I%
zp2po+puyasEm}F9HHCCRU%lNiJ#u{?0gcJ1^k@|-7UTQRXy+S`Nq_WNbHz)coa&LGc*6W
zT)1AiJUKoy?oI4MpCfPVU{!M|gu!S%zdpJ=GkrZ$6tR&{|EJ((X7fAwl(7kQwBdgN
zhkBIt))Y{|H*qpl5wl?Aqrj98t0SfQby^(dOSCxBOz%o_hZTmnm0V*?_-R2%oJ+*q
z+VxaPHxcuBHb!cQ(nop~1c&jGj>$|78_eza!DObdLpXW#X4^mqqsKUjyuwP=y#o$1
z^&olc{GQvl_WM2iApx~~RI{}&()}wdlRnMb2Ip+na)(4aAP1<>*gWER8fU|lV2$GC
z`BoAM2UcmoBH!z3f^^fL35xc139su@*|PZ$!6~PS+7ywNHjRMv#}`Kj4kmrQm${b9
zu(uZjp!=Z_Wb0Sv(1=rhm7R+57j>Roaw#i-taoph!2bk9(;pycIW0a|=rW+A5D|Cq
z4qIPMMWw~R1ML)78iQL30<@z#jq)&|(@W(u!?W+aHYdgKS_OFr9m+3KnF8p8Y0MI1
zK6R30u}jj!zI;l=Xn<=0;>A?kI?^v?l0mZOl;G&D*zg>&YDcYdXTTg3Xaz*_k$caX
z6WIm~(xto4U!G!T;L#v|b2}7#ypCwl{Q_U6?Ivx}Cm|*VUb$PNe{(;Tb3b@!*nX9;
z1?6AJm0o>{N8?KOnH07^>uHeAc;zoO`l}uh3Fa+IU&VZpuzst
zn+tQV^k`_2J=rQ2)!`k6;jJ&164gI;#JQc;e;cRrd||M*tzA!n3Pq8;)6?A!wPXY`
z38s}`k&*iKA41N;fD#fcSQmqk%*U+#4g8=Fzxp#sCmCqiSm|IstK%a9E5hMX$fpes
zyB4nRR-Z*Vtp?9uCu0Xs)||$h!`DJ>Z-h(=&@js&{O93>Rt>VF>
zzDU|^z<#hpG37g_fj|ixp#T|cXrUB6#1@0}B%UcG-DndU!$d(@+3Oo}sURIJ$F59&
z44FA_Qu8sqV$puDYUP)Mn@sz^Ah|K1w4p_A?seF#yfpue$z~P(cC@yDz2O`85T72s
zJ-9#=^019w-Z1&`w#NB#otwM5O$a9~dU-zUwYbTm_^NSBiW$G
zZfqywpT0TY-o6^CGPE|?T#iKc&dD_wzDbMY0quExI!aifyPB?}k5>r}V*_y%Mda;K
z*rVfO@JO$w9s{)U64Zr@9es&eeHztmI?)cYpv+^JnYnxrJ01-E@l-ZgPOD?k{}k@_
zhg>yoF#p>{ndX34OGmeCaV}*lgzMBwj*+bEpJyz?z}W7}ST>0=OoVQw$}BY)8`Gob
zJ{xgLp?aD*n7k~?kQSYbMBWR#BTQiR^%apGkLQlB&9Ex$H@+G;i?hoks6r(0_|bNs
z9%=D7F&fM1*sh+N$d(AR=Y5e@dp{LLvHT;=cns%EfCSgqLyCqgUPX~}vQWa*{9=Gu
z$MpC{D~8riPcB!MSJrFGzYVf{*{|YPMYuM%-Qp-z0x&^rW4+_s{HC)P~M
zB|Q^KF!i>E#@$>q!KSpQ!^ta?FOW`c*MC5-7&M|{(v8>62n%#D?xQlzUF*$fx#)s6
zpO}#I1~WjrV0_~-UAXWrr*}WAU4Ax>CBJj7*moHFDIo8wOw*>?q^Q1p;{+Q_K01T^
zWfWOL@`pzi!K!xV@XDiZ(hQ7?oOO
zh?(p7H{U7$+r7x7d?%vCIf>+2(f3I5x~aA+Mxv6&9G0=A1qKcFA;sDlcRVC*k82g{
z{3H}58~79(RHg%dhy%w$spEo$v#0X`BErL}SWI#YIaB?=cYZ)>aWof1mc
zzR$Thu|f!0fvaLX9HC^PexctXR58)~g9Glp5FRx$LSGgTT~smqAgKc~CDBCDprIiS
z+9(49KODUHj;$;&EF>ILrbJ)zW{k72x}GjKU9C{GT&1X>Q#=3P&eOJYw}_$xUpR<+%YglD)B?FTzv5b^ZEp^Xjp#-eL9lMBslJQ)9(&K{@OpJ*8y}uA=EgjgVD9A9S#*lWLd2Z
zcou%#UJIsq3C~j&cdHew+t&;0KD?(viS#~>i5WK(^ElDf8N(iIbmD~(NV8aRjP&2##5@y^FO)w)>nTZ{Q|*}j~uFp0>CHdbwA
zyF^D6WQNy$mhz`p>4ILU1#)=#JwET$)9r^v9q(HNG+X$pePA(k6caJ8@SUvfx4L^)HEfKF=L3ndw~Q6sBZTr*_V0@NuFcIe
zro;W#;vJJ-1MIuxU5n%jGja`|CR6mZ+Fv_RsQu$STP&4Bj5ncNt3W34Jffdv>d@V#
zh8EFsY;x&f0Mg%%+tktOBimMLrO?$s!})!9Z*D1mTTJ}684z1)Qtv=+UYVClQkP&*
zz15<;mY6~j#nAqVQBZ;=a=o-38>P2AoMd7UHb($YUEbi^vN=Aw!_#-^H*>6pg#<)d
z{lTcnF#5}^Doif}i8iTk1a!V0i#XDOlBR#ikNaQy1)i{KBqZl=UZ@`qT&aTv-wp)d
zWSLAUO!jBU
zm*C$Ud0o+EF)ZGeE3gJ4!Mir?wmyfvv^Lne@1NK)t!&{*%~D=)^;(Ro`O`Pwq-T
zRKtLU%mFSc$l7|3WHanm8x10luMdeaT`Vl0qOd5Gi$aeHJvLX4cEpS0p|W|*WC{aF
z6}767Yyu-V^LBgmi-=IW!bi6v6kjStJt|9_U~#u7iLQh^-R`>b!in$cHEe$Pc>T5K
zc9gLp4=?05KE^4r+#K?O1Y-M3Qu{`znR1=+s4f1qOe?qevO5MM^PDmr?>H9-3S<}@
z|69M_4QOwCl@Pg^R)s-F@&WR_DM~|*`JMnBz7nW=!%0p~0A)0m0MTw%%fmLWy8wI+
z!b%9pJd)@!!TCBdyTsojHc0yV#m*-?&0$p|n$IoTC{|0$;`7n{(Zh_nPPeV7XrwQD
zGmL!^>v}6zBD(j0O$f5hphUN@`yd@LEO_QWyK{x5QHL70=8|4j7D_
zN4MQUBXWTOT`04z+;SJ``_3}8qpvn|vr3ymZ0S-Xb!ePEY3BTEGjUeGFpDPt?A?CG
z=A`E|(4udscZ*<3+eAn6pJj}}nwGCo
zAtj|?b8K_b2+Z7-f2Ob*tp81pwAAclo2%fy=r4B=-_0%1Ti#ew9#KhZeWR^;36lH`
zPIopZH~d}Xm*8|UC~Wy_V*jGS!%0>nF7x1zKO+wng;p<8(?-;H6c&Y1(3?-~*4rCz
z!&%;Tb`>9CPUEYH#HY*re)xJEcY-l(&8#<*6$JHTus~Z;|jnK(V@~Z~B-H%De&7iVV@-JnAEoWbJG0rInqneNrLZ8-)wxxgzxC*1sbp
zf}0eij#5BrO7OCI8OUPxR2wF+^3k+S^npo<~E~B+)5w>+=3AF!5#0MF9rKK$M1M7rK+ue4I^~eDwn%d+)wdoD#986xhY#5W)>HX0bhd}M!N&p(JUItmg|qhzYMaL
zQFrcD5urN7jEb4xojph7PuB}=2<51m$XPNrw-FqDNn5#2c}k2zqC@9YR#^189r30$
z)OGMRi;GT+rDx#IsHn-+1A6)z|5-zaUm6@5%j#7Aov>L)ifw`}MR%kYED`u;LZ?Cn
zg=N*toF}-{t0JFv%{tbyq?8iNG&{+h@69I~y$Su$W2&=dALyDtdDBzQcy!K1^sf#7
z08IcVv}`970AmV$=$PHljA5IDL*%P+qSxlYkAy2Qp*3gm2OC!{IN$rawWm%N@2SuN
zpLK)d(D3fMNKHqA=|eEY#CMTQlAg!wRZzxqv!!yiT8cvS6~1c?rx-+V99LW4jq74@
zuuF64sG5I(r*lE=f*|cU>H)c$&Nh(47FR5spi~sO09NC>k+>4N61Rz@+rjJf(<84s
zo4qriFz38)u^|6@{PDOA0ycCMhC`mbBdm#cEo-6bHrPwR>+QYpN?>>
zNjg`wnC>Glg5K_fae>Yr9_mOHhx`ZthJ$Vt+_%g=(O0F-2L{{uq`HS+0_K{uw+S@D
z8MWNPZML7^vRWMJw;L0-Qa{aO#7&?zeY;CY`WRv)v03C^l23%>y?d=Caviw~-M3mF
z7yCU)498VYSSp8GA%S&x*Pi@ZwOb|O?Kwpb2aPBIQs(Se4s1)IghniA-dm-Avd-H^
z1qF#xA+=aoUs#viV|Ks@{$IDy2gr1E>J=tEh4FybnE)XI&~!Yp40?KOCy=zbM(Xyy
z1XlmRF62@~Nmzw(BSpuZ_9GoW#Dzn&1sS@ba&-LW?RTG;*-HOs*0Bs)oLp^w^JiH-
z0-KCpF$rRqBWxxlcd0>{TR~6iEl?e;LNH(;>A;b?QUqVEsjm+eYm)wfq&7_|9zPqk
zO^b1O@uqYyY$q@i2e7xC)4wo8aTgpo`g<>Ufwfy}ZF4c%6)7((s_zdrvcf}BNt5Km
zB(a{%dUYv93nnJWv)60PPNfg)sghu2e3=N%Xeaw_Sh-s#H3?fGRn5hIwxe}1dn+Iu
z%%uxE>w>4fHR?!pu{I;HQgLS{DHZ?Fnd9o|Bx|3x$YS==+!U)FSf_00RMlvihh2a@Layf+oP=COD#k)Njf?UlQ&foM(k&T;23-H
zp&>(y(YKG66=>!hNvdkasrtq6^DQV|)
zpwqzY0z0NRFKyu|TZ~hNY#u6w#Y_dBlm!_IYYMf?ow=5R(7`8-$M^R&Vwmwve@GhN
zv0Ewm4xe{7`mN!umA!*oQOfhrQvIg_4Ej9>4$b%>43XHfS?IXH4z2MP=qj@?(sGfMJzc6%|au
zC+0E+2A^U6ZJn!>AI6bvG0M8PLRu_8?BUx{0IU`(XBwOPQ|&NeAXiCH2TgPwU5Hgl
ziL`vJbJh`gxR8f0)?(kf2ZOtYzCq#5X}B}7Xgo`8G}slX$)6ULMGFom(ajaf73Gty
zV((Z(SSRBaP>;BHPZhSwtCpiNMwz8IF#F-CL;m!Zq;*J@8p*MyQ)!x%{KS0)Gq{l(
z4e?FDq}VB|U@2Dw?nF03KA0OKZ+U%y&Hi+ekqGY=UOvUSNGt`Es-!0F@|-TMEIqrr
z-T1r=>41f7cq+L6>T%t*0t>wBS7sbt%oU*)<8%=qzOtt%L!=uTCN;ocQqP-I+cFv&
z$87)dAnsBjr`GfPEjmJ|^*Ttnu1RP$mS{?nXjO=DyOwh50Q$*Q#SzHcJ
zc`M)EX?ubhNZjqk=sMeAvuf^i)M--IW?h5hy|0w5d{K+}`*HCKkU{?$pZ{vGq}E}`0-3jpTs4k3
z*;Jt*_BiEYRimFh<7_)Pr5FEf&2i8zFJHU+BMbMMf0J(iPk%p3RE~RuOFG(?#LG=5
zuy$L_Swg6d-Tf7)<&Bzx|B+|sxkiULJHdbxNpbj@waDqQY+MQ&i5VV=`=#GhoE@mm
z3CLS)yHJ=-?l_o6Bvzgc^3}AeqU;^ni%zb!1${1nGn?tvY|y_bAvR)5OS^%>I)9cq
zDgGY5?X{CEbrV6zdMYR?;i}2cMIN#zNH;cFtMoLerU$q6om1m6B8=U`=jL9C@yQ~^
zNrUgBx|c_+9&wdM2(h@SUJOfBbMavJ9LByaHV;DBq|V?=xto)h+c?BxOBbGvvB0Vi
zKi5c<&As3e(!+5m8kI0JWO7ua8oWGr)D6rI9t-plwRg&ZUDv#V5<7VMTnJC3|
zRGU-UvQbAtSmqv!6Nts=#SpmNplGm9(tuadYIML}aTq|tqP3dWFK`R!{~qz;&VGK4CZaOzc^%xwDc->+%9{HKb^;j>{ruyeqK^D
zH@Uvoq5i@Um(1PtTI@s!G%puORV}{_)B&22TuB=k1l(gy)Mmw0PAz!-^mNMV%urVv
zD~Brf2vPkS6H3?o7)pTAn+N-|rOwsGt!NR!(UHb;i{mC1LiHC;(S7$$Y@L+UlAoaf
z@i&0D7Hz{I^MPQgBGZ=Ut#*i)Tk0zPRrSRK>Ga7VPq9PDcERnB2Q2l>dRyW%d!
zJQ7Jd=}Z4ip2;x{>5R0fVl@8E1e`CJ%d#xr&^2-K6Y^D_rB=AsxpwQKUN<-EHWv0l
zMJsnIp^9>fTP%R95xGp?PJ5+OhA7gKa)$1p68+A#wVI`?Y7;uzY<42=<*efR95d>R)YJ`o|H}v
z<0=mB^*mNvYx;3i8VeQ&TvO?@!51|g5Z4ug`{gvdnLvSOjkJe+jF;fIAaa*uc
z(qeVET7pr}7y2wimLR@Q{(oIy4e;}?9+$WKpDU!%%>Fdfa9<5h;E=+LQSp6EE^oed
zSTU}-27Y(t9BGQH$A?u9V02yMl%}Y>V*3N2Nc6}{7e>`c5AoiULOAqDXC4R0?-wxS
zy1HJPy4vG!DaI8R-6_vU(?$HKsYDwi15AH;BMWvzRB8V_Rm=>N)D3rh_rzJO@Qt#9
zf;$77gPhr7{=B4UEH`GhDz)_C{z+xz3PthWdXAex;b=RWg*{~c>vadx3{veUa#HAK
z^dLAC!iw;(4kr5;57^9=9X@Rxjd{OmT-#>@$?&ziiMPEru}EZ?i-IPBPk~}rLno!W
zXJ7H2Tv$_-OC3t<^V5Wj{B=M7lA8~X6J+!jpJm@AGeF=|FEAN^r6EB_6aryhmmmAYV+1|z6uEa7qEQpQ7>6}GN!5QHH*MhP
z20wF|`ZYaURbBB*@aAnFO34S%0C~uXg9E7><2tfyr-08GLlTavv9cGP(V?_smp)wh
z`rSmv<+0yYB7sdoqFe}MW07Tp_0O%sScYE=D9HAE?etLe1*vGm!lZ^gNjHS+jG*G@
zNxP*?*x-?PQsQN#f*n*F6`_574$q&8;s(|Gxj`=Sv3@lg1>X+OIR(5DV087p%$AbZ
zI3@;DD2rbO%O8s;L-6x<6p02Rh`AT2`RTB5qaRAFn{qn7CeDcA}-~JUJT6~81
zjn96JR51oZw9nz`Xldkl5A6%NAkW&Ff9iR@dN(&}a3-^l=S67$FB
zw{!Jr;nZTGae3Tx@eAyTJzDo^{|t#&%MdtXH^TorA*2n7$|)^_JfOw{iONa4q7wlB
z*EmQYf-+%2gp}LW8G_$Gx`_6w}_7kE2
zK-uSFw9_PG{O#!wWcN
z0>0GhjQ;d!j=M~;=3p=T+SAyFIA}(ESPT4@Re1FNX4L};35kY{JmQPUm%f=9Hmc0U
zMZUO=SFc|2agjHFfr6hDh2c(lU3;JU*?BMhVJ5pM*!ZEP%J@!G8rYxf!SJO>tU-%0
z_V|%M>e^b?an^TiRkCD(zAw9t58uJjVQ&mBqmVo#dd&C9*2_Ju)8Nw
zGu!Zrj@t}GB*bD=Uz2a_mMSHK5ThxNd(RC)EKE$XE?Z)y5|%^MaiiYpi0teJJ<|??
z1xENhV=M)QEY#Px4~@HPvuPlGNzJ(+ES&vi+i~$If>GBMdZkxayWXVEZCL>uS!U4C
zXhmwUBsMCg4K;_jH5PaHJe50WM@!CrN=n1;UU8VclUZUsmi2zPQ8Nsw$~B{);ti>P
zY75}_ewT`J%qv`6oJ0_Oddh6ET!NtM4N07AG*5#V%)ar*mmr}l^Q#^|@6Ys|3=&Ix
zq;gw3KyWhjbqPx=_icn0<3yyd(zk!F=945U;qtkJ(b@3TZZq6IuhX-m9^%o{#Q8I?
zAEKHVGZYj*rIhGLm5Q~bLK)Y110pWAI=^WquCj0I^Faxkiy9DT)_lqx#TLD_o^S#<
zj>3uh#NzGZqANArK-J{Nv#XsIIs*~;!?IL{5Tt6$KAn!l@eX}?ALRWE0(+wg7wKn%
z*RR>j^^dxvZdUFi>#gU+$iZ(*tJZsWh)1$}kbD(U#Y~31Q@y;xJKWRRETO#xZ>X+l
z($B6^vEFUoy3&)A#}^1ZR_|Y2gP9Vv7Qa&65qI!LXf;@`oj+@HJZEqxrsZtwc6|K4
z^h^XE+7f&g&y;%(p0Bf2weE>p3aQ@92LgHYTH|r_eOgw$>7ySZgex~I90e1=j>7Tb
zfVqU>ociQY0$kU(*$7>^G|kZ)uIqSD?T>*Su09J1HiR4CdGU#0fA;HM>U|%*(0EOa
zZ(8*>1>KeUcMV4uz*hMhTyK^2ow2P?v(PXk3KZ~MPuRs66TN`J06#aaUr%1`6WJRv
zRJ1egs)N&`3B{N+v^?VlE2hLgBB{^wCKHqdWDZtq#MS5ctcMoO`||=Q-lI@3AHsfA
z?}gPu8dMM?E(;NeIhoGJH*Sm-2hJ8T9*i%PE33c36P&fwOfpv=dRwxKaa4LJ_9;(%
za0JG>X{o>+Ofr4JuSZb>#r0+om3DBeW`ihlPU%M4N{6|fx}8-xIhut>V&eUU+|l}m
z2MPq$ZB;}vrKPiXn-zO9wkxi*Ri3pBvgL!K3{e?F(mNO*0w^PWG@>47j`LMo*@9%
zV;BJ$L?3^CthK%QsKxABHP7ig45U4-a&Ez~Ab9qJf=`eY5(da;Rz4Q};!6c$IFRD>
zXA@X6qOiRQEjoY*?mU0zk^x0mF53~$WvEgFM%m0vW>4nvh4YS(>Ad@TsJ1>I{I#`v
zIPF)NoxMoLZ9$=N(ZvdjNu!opx8TP|&Sg&KuU=gAueWt!8kX%}QDjIKMC%S;9RE-?
zt2JRreOJRD`&A{U(f&}fb)P8%wVXcL7r4l2oHoByEyt$5G^!^Li(f^xa{5%K8=cXg
zO(ytgac9$f`iO=xf>`6-&fJ5>(XG5u;8R!3AA*ciDOt5+SI;w@5-`F>Oo`tqE`gH+
zr%&|J-uabTPq5Sd6Nt@XMO`qxAR}F*SWbB-JCL8LwDN$fQ#VG8p-gtGy8=A-^MVj#z1dQ_l~Xy_%bjf-B4C0ui`qB~~yNI5~s0
zev6pG`~E7gerMr{E0&lv>Kl8OtA1)WbGc@ne@S&?tOrL_MV%k6&{{)Ia>`bXFa2<*S=agCiT`T?#k*tjUG)1J*cZanMFN{
zt_g46)k>Lh$Bx5HVaEl)lzfA**tsq)*HAD-KmflUlSzG6Zbck&+zWJ2=iFNmVfc-
zXM$cbaM&p+<(IyQ8%}1?_@t;;+=oGufyh81
zI8TvQ0a5OXf$0h`GsU57<`w=`TZy`AJJzps1i~%mNL}B&F>{xOp=|{u1nk()N!E-A
zxwG5DnJ@@k_Ek#_0_o8w{W-8G1PE`>^Y0&3iW!Khh_FotM;P*kDAje+1)&huS~lf3+0sS|*EY
zAls8f={ZI17xw9_kJk(f1BVW`tXbKVob0QFucQuvO_lAEnLe0d3zspKh&k^soZGuR
zN=2V6Lri(zFJ(w|=AnaCGF{EN?%-yhZl}P~$&sxw*EmBLHnRn8C&&**d~?^Ej-LdN
z=h%va584MiDAGh(E@I^NN3){K`Z-IYAt8VdtMR*A)Q
z>6=_a(zo*Hma}ck^k5N5o6@#4w0il^)>rQV3kOfLlBwL6HHz`UlkwmK@4FuPkx~NJ
z$C?lhNL`}Kxsros8dX2g($%4C^E>}Q_)yTrt9R;@dMf9>N{6;jvgX>SMG
zM*;{RmQQy~Od8{lA7>cy-}jbnY(oss=HU^p^O5F5W(mo;Ih-{5H+lEx;R%{^+bT(q
zBqI25jF(b4CH0@mC)ay_VhD3?J*U)9b(H6(+Ti7J>N0LU@5Q8%XlMhTA&H;snbDy9
z2jqU7satPlFqycbAeh~lr+j(*de;3YW@vhGQMn&ZwIigDW(V?HOc?gQe)oQrOW*Vw
zoTltFVT4?4>?+aV-L#f@)8R&8ksOnl3Q^SujQM#Q7GJ2U-7LLDq0qdJH6r6c=RaIH
zXn1>F(irPP8)G8REgT2zT&{nFH5hF6JXI8gT7RW`-$9laUL6uUt
z@+ACWs{McxvF)BUbqR%lUN5ipyej{>agAeLeBdCHCiaI{BmgVQ`=Dc+GWDv4twUW{
zsO%$1`KcdkV4Z-X)H-L<)+et>;>3j(W0QzaoMxn5g3Qira8>7x!|)Fb(NNiPGkcG3
zTg_Kh9(Y~`5+z+g18*+D0FC>&6&lY8l(_4@kluY8Mv%EaL(ZYEi?ZZMx%|%2xezYz
z<{RI2-RGT3b&POC((Qx=HlqNfVi;$lm>NQ2tf5kaB$}opYs-NOTuv#co{>L2h?bSjTg%
zzadS)%Y8pq{SvLWn#(GUHulY>kOmVY!rW-hlGrtS@~?G=-Kh
zRmFBk)3tCQaoX+%*^CtS$)MoY!IvgIl&<@5I_GLqHXP+=Tb&bxic_EGrnh7L5C
zT_hH{yzlAdGPtI=j=g*o;Ox78_+z6L)xr|`QmD-r8yfC}`vn>ht`V0YZPTkMf1Ona
z(q^Xdr(3A#nJdf69yK)!q%~}#Ym9IXXw9P8Mir!s%<_^-ZkcnPy7J_A?l%_hT2=nGgp>4P1X(Va!B&h1SO1l>sTb&*W3JU7Hl|oTccns-D`n
z5r2qIeWgSI2gn!5eaR5&t6=JQg?z?EEw$LUMYS{!b9jysDx{cfj-KXlyDb3XCtIw$
z45Cw=`Q&3rG}=tF^o#fM#V5f_w$qu^^A$kwserT~@cKmT=`oK#)t09x
zo;;qPN+$&#TWj`o?d01ibXz~jQEk3G-e}-TIfA%KUsCzJ1bmN2-
zPlVnt<|0_^Y(hs$qsaRD`<*xu_LAD-c@><#LJLJ&KB;G>B&!TMyy&~z-E>X%s~#G8
z)RlfBb~39zg^TsycN
z-6)seI}G0}KPI$|!kCS3u8ZXesy`dM*$-fz;V`6*hXux45Z<+sOxJtMI3urnlTseV
zO)4%3rn=JFZv^hue9~X8L-q_ct4~SMyuAA5es2eoL65eF3!uEty0?ae|%-i9N^8L|ThA1SAjp%HN$U4yl>UOfRO*SHtv
zYd131y|n#BN?pPzyl<*YZU9KFdr-KOr(1Nk
z@#2HF;-^*qE3=Vic1Ed#gUd){u3waa8@UrBn~HoPD~EcPccgRez;_WuNw?+?uUsLq
z7Vrc+HwcB6$ECK9pN@uErt~XMNprf+@uX;JQfDc&>H5GH$G#7xoc9fE?6{t#T6)l%tYOQIEZS&47
zWfb>37OfC#d;N@U3~`yvuFK6wBEgbW8*C?JXKs3w
zxG9_}(;Xkg&CN-FF?ak;ue)E9Ow-PKetg%}qc~<%PrEKakP^aXmFY1jigtrZ?t}tj
zZa_RX4R9`sAK2XsYz{bn=TU*E8J9*6e6nSICUzi-p0ZsvW5@K6gO3s`f?!@>PizBIb~ou=pZ6XSaxm
zXG;4;|FhYTtagjlxVgjt`9vkI+(g!x~zba6%xuTg4winkv`|tQsu}}HurFz7z0gWmT@{HN7}PK
zRLS7c1MAz9ATOdTQ>BI%qJ%;l{Ol8UvEEE@Da|WrDg5TROo!0UvLNKM*+$oacNRVR
zXvgy|PuVpdTRc;`8K<*UgwC#nm#?60F}SohhiPE~$|?=GWpr9TAvO$(k>>RF=A_;y
zJtp)m9|)gI>u>>-kV(D>bqWj)rE~5a^=oJa#v1K&AUSbOhCJU#xCYYerd$W#X7s#9
zr^vYjTUrmRoD8rN&-wP~IwKp1)E_h;QX*iYV=_f5GaBYug6|1BgD(>wn%iA_`bw&!
z#1J+wUBsB$uDB(ot3wGKFfkMt_MHuV`Jt^-OAEdz7Z#KBV9YQg7avNQGAV5y@?_nY
zwBk?#5vMeQeIMO?>JA6oLN1&7-mwVIak$F92?-Bt;N9
zrH;pW>R=(I!f)06$q1)VISnaneC;Rrm?aQ-E~x~KM=^(+Q1rSDG7qj+$i_nzw67qw
zl1$xZIUIkYp;Bx%fE-i>b~*|>&F4_i963)xd|bBLH2J?
z&dOL*Ow#nU8F<9Qa`l2~_)|z(=Fhl=d|aP*1fGt+GUM`ZE8k42C#n;oIE|0yIJ4!d
zIt=}INoJ{_-E34wZt8xiPvvP6>h{+CaCC6k1%T?}3mM5AWW9Hd@j1-_&c{AJVLM+n
z=7C%`8uW4TnM+)T3SnTCBovGqp1jN}a7G5GHeyNese@Lk#0IqWF8b9BW9_!fcXa_6
zMXz{9;57wq&-fly@xhOIT5}V7HvS&_p7}iX16G0Z%A$`T;bCdI`$X^&g6CXU7Gb>R
zep92CbWyNdK`3?AMuSQTn3U|uBc${znmTy4!L^m_%afMV{OOn79}7Km<}SoIr7N_O
z?%uOE*j1k&Xd~bxrM;r1mn~Kbt$|Zokwqn@GzP^w-h
z?KRF4KsqxGB0-(}e7#LUsf_O_XNF|PqfusIPd+-h<_k@4_HeuKq;nco?Sq5Jh4q8k
zC1zyjW!QP~4!v1S>|wE_~iI4v+I}kP3Xr;wKAq@lK5a3x|n{%z>MZ`id?)#j#i?`wAOz
zGW`$~J+sqIeww2_@wZLdL5zDF6rer^@{mzyPGoA9u@Zq^?Ll{)XjSbMr1v5s4%~-h
zRv^3N^~sh4yv_!AGNVi$X@tiHZ<>(ONJ1?0csr+=pH?2HsyO^}G9vT^(ZsK-8`cnf
zgh+D+d{?Bh4%{LUx^f8}ypu=h4$l4LQ#Uh7<%@LErlO(>rnGVJb-y$kqQ0PlbIeLe
zozmS-1fCk2zf0PduHHNb7w=O@+9iFgJY230YYE6iaeQ?I5>WaQ>Xp5C
zv1(SqmpHZox?$yv$!xtq6;-DcoUJ`5J&yO7#@NqlsQTUt%ebWwBBD*-FG^uv&;ky{R2$-jOi(;fTQAG4B)M#b3*9Cn|S!QS}Lb%
zeL)#9`nnMkamz{hnupBl2K}7wpxfyxM3QYI$SvhWN=i>uTy$bM!#qq=Tx2K#H(?1`
z68J%M77f$pHR1T`;4)Pc?{zVUZG@o3sM6C0J@FUrL$;an&M1MXnpCqnT&+QeuB4$%
z8f&tFgA=;D*0!s2r?$bpaYEYl?*XNbsSg9MFs#D}d8+IoICbtndvuF%Jt2}kh*FR4
zhi0u7Am*g%c_|!7ZO?SXbSZ~Sjos&(E+m5TMlMg_fJ5^pV9->%cXwFzFvAzZVlmgO
zsToW^RTU?y!bj8Xap78^B3;#>&{7}9De-cGAg`V*EohFqZL!G^5uL4$8XML)A|e}z
zNdIiV%)A%Bl`>I-ZaeLlx_7jEv$M=q%Ev3ZNj;46p3CqM#Wc1KfN4u?`Yb5JgYxhZ
z3U-(QdZ&YIPaGxy+KDrUniGlIE5vqr6oA(%kRTNLR-55BcW_ao0}!`ta5sc&2mZp
zE`q^V0=jQF2E|yFmnvF8%lCwR%Ac*l(cQ`yYI0WvU96S-E3FrD&DX#B*1cXE`gpyf
zGM1yD2gHc*)V@BA*RlN;1E+_=GZW0y(QyUg7?EgYNYf+*sZMQgNFUO8+*_1)Vs!g@
zPM9~XlM6=xWU-aKW+MP0wmAXKb%l%MNob*d^+S_S1E(=A>
zQR6zkR_DZhb=pe&O&;sF&))Iq8%kdPw|nk3jH8=`g`6?
zI&*UZFL&#<{YtDck#2Z&YC}1ghU3{dObJU~C6#iWdSA^<6E~|xHokc@j?bBqce}~W
z>`ttnR#ocYnFt^qD$3l>fYUN=e>{1%#!GE#Un`Q%JZW^Ber$jDbq~B}PB*YR}xjBWXf8oGOTo&C>}huOQYo
z7WYe&?N7Wx8j1Tg2I62I8@;alzhYXv$udA~WB9Xqd+m@}0q;3Vkoa6p?<
zc&v<_bR{Po;D-CQ?W&noZXwa`6OoETNMF
+
+
+
+
+
+
+
+
+
+
+
+
+## Themes
+
+Switch between light and dark themes to suit your preference.
+
+## Default Agent Configuration
+
+Choose the default agent and variant for new task attempts. This profile is pre-selected when creating new task attempts and follow-ups.
+
+1. **Select an agent** (e.g., Claude Code, Gemini CLI, Codex)
+2. **Choose a variant** if available (e.g., Default, Plan, Router)
+
+
+
+
+## Creating Your Project
+Click the **Create Project** button to choose from two options:
+- **From existing git repository**: Browse your file system and select from a list of git repositories sorted by recent activity
+- **Create blank project**: Generate a new git repository from scratch
+Each project represents a git repository. After creation, you can configure it with setup scripts, dev server scripts, and other settings.
+
+
+
+
+
+After creating a project, add tasks by clicking the **plus (+) icon** in the top right of your project kanban page, or by using the keyboard shortcut **`c`**. Creating a task adds it to your kanban board without automatically starting a coding agent.
+
+## Using Templates
+
+
+
+
+
+When adding a task, you can select from your saved templates:
+
+1. Click the **Use a template** dropdown
+2. Choose from available global or project templates
+3. The template automatically populates the task title and description
+
+
+
+
+To activate a coding agent on your task, create a task attempt:
+
+
+
+
+
+
+To create a subtask from an existing task attempt:
+
+
+
+
+When viewing a parent task, you can see its subtasks in the **Task Relationships** panel. This collapsible section shows:
+
+- **Child Tasks** with a count (e.g., "CHILD TASKS (1)")
+- Individual subtask titles with links to view them
+- Easy navigation between parent and child tasks
+
+This helps you track progress across all related work items and understand the task hierarchy at a glance.
+
+## Viewing Subtask Details
+
+
+
+
+
+When viewing a subtask, the **Task Relationships** panel displays:
+
+- **Parent Task** section showing the parent task title
+- Direct link to navigate to the parent task
+- Clear visual indication that this is a child task
+- Context about the parent-child relationship
+
+The subtask also shows its own **Create Subtask** button, allowing you to create nested subtasks if needed.
+
+## How Subtasks Work
+
+Subtasks in Vibe Kanban follow these key principles:
+
+### Git Branching Workflow
+
+Subtasks create their own feature branches that can work independently while maintaining connection to the parent task:
+
+```mermaid
+gitGraph
+ commit id: "main"
+ branch feature/parent-task
+ checkout feature/parent-task
+ commit id: "Parent Task Start"
+ commit id: "Initial work"
+
+ branch feature/subtask-1
+ checkout feature/subtask-1
+ commit id: "Subtask 1: Backend API"
+ commit id: "API implementation"
+ commit id: "API tests"
+
+ checkout feature/parent-task
+ branch feature/subtask-2
+ checkout feature/subtask-2
+ commit id: "Subtask 2: Frontend UI"
+ commit id: "Component creation"
+ commit id: "UI styling"
+
+ checkout feature/parent-task
+ branch feature/subtask-3
+ checkout feature/subtask-3
+ commit id: "Subtask 3: Integration"
+ commit id: "Connect API to UI"
+
+ checkout feature/parent-task
+ merge feature/subtask-1
+ merge feature/subtask-2
+ merge feature/subtask-3
+ commit id: "Parent Task Complete"
+
+ checkout main
+ merge feature/parent-task
+```
+
+### Parent-Child Relationships
+
+- Subtasks are linked to specific **task attempts**, not just tasks
+- Each subtask knows which attempt created it
+- Multiple subtasks can be created from the same parent attempt
+
+### Branch Inheritance
+
+- Subtasks automatically inherit the base branch from their parent attempt
+- This ensures subtasks work within the same development context
+- You can modify the branch when creating the subtask if needed
+
+### Independent Task Lifecycle
+
+- Subtasks appear as regular tasks on your kanban board
+- Each subtask has its own lifecycle (To do → In Progress → In Review → Done)
+- Subtasks can have their own task attempts and coding agents
diff --git a/docs/core-features/task-details-full-screen.mdx b/docs/core-features/task-details-full-screen.mdx
new file mode 100644
index 00000000..582e9a8b
--- /dev/null
+++ b/docs/core-features/task-details-full-screen.mdx
@@ -0,0 +1,135 @@
+---
+title: "Task Details Full Screen Mode"
+sidebarTitle: "Full Screen Mode"
+description: "Complete guide to using the task details full screen mode for development workflows, including dev server, git operations, logs, diffs, and process monitoring"
+---
+
+## Accessing Full Screen Mode
+
+Click the **Maximise** button (⛶) in the task details header to expand the view to occupy the full right side of your screen. Some task actions (like "View full diff") automatically switch to full screen mode for better visibility.
+
+
+
+
+
+## Interface Layout
+
+Full screen mode uses a two-column layout:
+
+### Left Sidebar
+- **Task Information**: Title, description, and metadata
+- **Development Toolbar**: Primary development actions
+- **TODOs**: Task checklist and progress tracking
+- **Relationships**: Subtasks and parent task links
+
+### Right Panel
+- **Tab Navigation**: Switch between Logs, Diffs, and Processes
+- **Content Area**: Active tab content with real-time updates
+- **Follow-up Section**: Additional context and actions
+
+## Core Features
+
+### Development Server
+
+Start and manage your project's development environment directly from the task interface.
+
+**Controls:**
+- **Dev** (▶️): Start the development server using your project's configured dev script
+- **Stop Dev** (⏹️): Terminate the running development server
+- **View Logs** (📄): Jump to process logs to monitor server output
+
+The development server runs in a git worktree environment and streams all output to the Processes tab. Click the logs button next to the dev server control to jump directly to the process logs for real-time monitoring.
+
+### Git Operations
+
+#### Rebase
+Keep your task branch up-to-date with the latest changes from the base branch.
+
+- **Automatic Detection**: The rebase button appears when your branch is behind the base branch
+- **Conflict Handling**: Any merge conflicts are displayed in the Diffs tab
+
+#### Merge
+Integrate your completed work back into the base branch.
+
+- **Availability**: Disabled when an open pull request exists
+- **Success Indication**: A "Merged!" notification confirms successful integration
+
+#### Push & Pull Request Management
+- **Create PR**: Opens pull request creation dialog for new branches
+- **Push to PR**: Updates existing pull request with latest changes
+- **Auto-detection**: Automatically detects existing PRs and adjusts button behavior
+
+### Task Management
+
+#### History & Attempts
+View and manage all task attempts from the full screen interface.
+
+- **History**: View all previous attempts for this task, review execution status and outcomes, and switch between different attempts to compare results
+- **New Attempt**: Create additional attempts when previous approaches didn't work as expected or when testing different implementation strategies
+
+
+
+
+#### Diffs Tab
+The Diffs tab provides a visual representation of all code changes made during task execution. It shows a git diff between your branch and the base branch, with syntax highlighting and language-aware code formatting. You can see a summary of added, modified, and deleted files with precise line-by-line change tracking and context.
+
+
+
+
+
+Learn more in [Reviewing Code Changes](/core-features/reviewing-code-changes).
+
+#### Processes Tab
+The Processes tab displays a timeline view of all running and completed processes. You can track the status of running, completed, failed, and stopped processes with their complete execution timeline. Click any process to view its specific output logs, and use the interactive controls to stop running processes directly from the interface.
+
+
+
+
+
+## Navigation & Controls
+
+### Keyboard Shortcuts
+- **Escape**: Exit full screen mode and return to sidebar view
+- **Tab Navigation**: Use browser tab controls to switch between Logs, Diffs, and Processes
+
+
+
+## Exiting Full Screen Mode
+
+- Click the **Minimize** button in the header
+- Press **Escape** key
+- Click the **×** button to close the task panel entirely
+- Navigate to a different task or project
+
+The interface gracefully transitions back to the compact sidebar view while preserving your work context.
+
+## Related Documentation
+
+- [Creating Task Attempts](/core-features/creating-task-attempts) - Learn about task attempt lifecycle
+- [Reviewing Code Changes](/core-features/reviewing-code-changes) - Deep dive into diff analysis
+- [Creating Tasks](/core-features/creating-tasks) - Task creation and management
+- [Agent Configurations](/configuration-customisation/agent-configurations) - Customise AI agent behaviour
diff --git a/docs/development.mdx b/docs/development.mdx
deleted file mode 100644
index ac633bad..00000000
--- a/docs/development.mdx
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: 'Development'
-description: 'Preview changes locally to update your docs'
----
-
-
-
-
-## Code formatting
-
-We suggest using extensions on your IDE to recognize and format MDX. If you're a VSCode user, consider the [MDX VSCode extension](https://marketplace.visualstudio.com/items?itemName=unifiedjs.vscode-mdx) for syntax highlighting, and [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) for code formatting.
-
-## Troubleshooting
-
-
-
-## Image
-
-### Using Markdown
-
-The [markdown syntax](https://www.markdownguide.org/basic-syntax/#images) lets you add images using the following code
-
-```md
-
-```
-
-Note that the image file size must be less than 5MB. Otherwise, we recommend hosting on a service like [Cloudinary](https://cloudinary.com/) or [S3](https://aws.amazon.com/s3/). You can then use that URL and embed.
-
-### Using embeds
-
-To get more customizability with images, you can also use [embeds](/writing-content/embed) to add images
-
-```html
-
-```
-
-## Embeds and HTML elements
-
-
-
-