One workspace to plan, execute, and ship — where your team and your AI agents always share the same context.
Projects
7 projects in Personal
Mobile Checkout
API v2 Migration
User Onboarding v2
Referral Program
Search Experience
Analytics Dashboard
Auth & SSO
Canvas, documents, AI, and live collaboration — see how it all fits together.
From the first idea to the last sprint — everything stays in the same project. No re-entry in a separate tracker, no specs drifting into a forgotten wiki.
Start with a clear brief — outcome, health, pinned docs, and team. Everyone knows the goal before the canvas opens.
Map dependencies, order, and structure visually. See the shape of the work — not just a list of items.
Execute in sprints or kanban. Board shows active work by status; Backlog queues what comes next.
Specs and decision logs attach directly to canvas cards. Context is one click away from the work, not lost in a separate wiki.
Stokik is the source of truth for the project. CLI agents can run inside your codebase while using the Stokik project as their live brief, then push task updates, implementation notes, labeled dependencies, and progress events back to the canvas.
MCP access uses revocable, user-scoped tokens. Agents can only access projects and actions the connected user can access.
Agent run
Claude Code in your repo via MCP
Create a scoped MCP token, then connect Claude Code, Codex, or another MCP client running in your development environment.
The agent can read tasks, documents, canvas positions, labeled edges, and permissions before touching the codebase.
As the agent edits files in your repo, it can update task status, add implementation notes, connect dependencies, and record run progress.
Example output: code changes in your repo, 4 task updates, 2 implementation notes, 3 labeled edges, and 5 progress events recorded in Stokik.
Everything that usually lives in separate tools — canvas, tasks, docs, agents, and access control — in one workspace. No context sprawl.
Stop hunting through lists to understand relationships. Drag cards onto a canvas, draw dependencies, and see your entire product structure at a glance — not buried five levels deep.
Stop losing specs in a wiki no one opens. Docs attach directly to canvas cards — so when someone clicks a feature, the context is already there.
Track assignees, due dates, points, and status without losing the project context. Team members upvote tasks to surface urgent work — sort by votes to see priority at a glance.
Run sprints or kanban boards without opening a second tool. Board shows active work by status; Backlog queues what's next. Completing a sprint moves unfinished tasks forward automatically.
Organisations and project roles work together. Set a workspace default, then override access per project when a team needs something different.
Group projects into named Spaces — "Q2 2026", "Team DevOps" — with their own permission levels. Flat and fast, no nested hierarchy to get lost in.
See who's online in real time. Canvas changes — nodes, edges, positions — sync instantly across all viewers. No refresh needed.
Stokik is the shared context for your team and your agents. Connect Claude or Codex via MCP — they read the same tasks, docs, and canvas your team uses, execute in your codebase, and write progress back.
Not a doc tool. Not a task manager. A connected planning system.
A canvas makes relationships visible. Draw dependencies, group related work spatially, and see how everything connects — without switching to a separate diagramming tool.
Discovery
In ProgressArchitecture
TodoResearch
ScopeImplementation
BacklogCheck API rate limits before scoping
Write specs, decision logs, and research directly inside the project. Each document attaches to a canvas card so context never gets lost in a separate wiki.
Create an organisation workspace and invite your team. Granular permissions let you set exactly what each person can see, comment on, edit, or manage.
The hardest part of planning is the blank canvas — deciding which nodes exist, how they relate, and where to begin. Use Stoker inside Stokik for a structured starting point, or connect Claude and Codex through MCP so CLI agents can execute from your codebase while staying anchored to the same project context.
Stoker
AI Assistant
Plan a user onboarding flow with email verification and profile setup
Will add 5 nodes and 5 edges to the canvas
Tasks give you a clean execution surface for assignees, due dates, points, tags, and status. They stay connected to projects and the larger plan, so work does not drift into a separate tracker.
Tasks
Cross-project work list
Approve onboarding scope
User onboarding · Alex
Today
In progress
Prepare API v2 review
Platform · Sam
Fri
Todo
Link docs to launch tasks
Growth · Taylor
Next week
Scope
The two-hour sprint planning ceremony exists because the backlog isn't ready. Fix the backlog and the meeting shrinks to twenty minutes — or disappears entirely.
June 14, 2026
A skill file embedded in your repo teaches every Claude Code or Codex session how to use Stokik correctly — which project to use, how to create tasks, when to ask questions.
June 6, 2026
Use Stokik's MCP integration to let Claude, Codex, and other agents execute from a project plan, work inside a codebase, and record progress back to Stokik.
May 25, 2026
Free to start. Takes 2 minutes. No credit card required.
