Public Roadmap

This roadmap is directional. It describes the product areas we intend to extend after the current hosted board, VS Code integration, capture, resume, API, and MCP foundation.

Current Foundation

Today AgentKanban already provides:

• hosted boards, lanes, tasks, comments, todos, and attachments
• organisation and team collaboration
• VS Code remote mode for selecting the active task
• automatic GitHub Copilot turn capture bound to that task
• resume flows that inject task context into a new chat
• External API and MCP access to boards, tasks, memory, comments, todos, and assets

This is the base we are building on.

Next: More Agent Harness Integrations

The next expansion area is broader IDE and agent-harness coverage.

Planned areas:

• Claude Code integration
• Codex integration
• a more uniform capture and resume model across supported harnesses
• clearer source labelling and timeline presentation when work spans multiple harnesses

The goal is not just to add more logos. It is to let teams keep the same task and context workflow even when the underlying agent harness changes.

Next: Deeper Context Management

The current product already captures and resumes task context. The next layer is to give users more control over how context is shaped and reused.

Planned areas:

• context branching from an existing task state
• split or forked workstreams for alternative implementation paths
• compressed resume modes for lighter continuation packs
• indexed search across saved task context and prior sessions
• curation controls so saved context can be pinned, excluded, or trimmed before future resumes
• stronger cross-task context linking for related work

These capabilities are aimed at reducing context bloat while keeping resumed sessions accurate and task-specific.

Later: Better Context Operations For Teams

Longer term, we want the context layer to be more operationally useful for teams running many concurrent tasks.

Planned areas:

• better tools for reviewing prior agent activity on a task
• stronger context-sharing and handoff flows between teammates
• richer controls around retention, history shape, and reusable task memory
• clearer visibility into how task context is assembled during resume

Product Principle

The roadmap follows one core principle:

AgentKanban should help teams organise work and manage agent context in the same system.

The board remains the unit of project organisation. The context layer remains attached to the task. New roadmap work should strengthen that connection rather than introduce a separate context tool that drifts away from the project workflow.