SlyCode

You were working before you sat down.

A workspace manager for AI coding agents.

Give each task its own workspace: terminal, context, and persistent session. Pick up any task exactly where you left off. SlyCode layers onto the tools and setup you already use. It does not take them over.

SlyCode kanban board with cards across backlog, design, implementation, testing, and done stagesCard detail view showing the Alert Rules Engine description, requirements, and problem trackerDesign document rendered inline within a card, showing the Alert Rules Engine specificationTerminal tab showing a live AI coding session with skill buttons for Design Doc, Feature Spec, Implement, and moreTerminal tab with session resume prompt, skill buttons, and provider selection for Claude Code, Codex CLI, and Gemini CLI

Built for developers running Claude Code, Codex, or Gemini.

Built on itself

SlyCode was built using SlyCode.

From day two, every feature, every card, every design doc went through the same workflow you'll use.

193 card workspaces (so far)

Each with its own context, terminal session, and recoverable history.

Built in SlyCode itself

The product has been developed through its own workflow, not staged around it.

Desk to phone and back

Tasks stay intact across contexts, so work can continue without rebuilding momentum.

Why SlyCode

CLI AI tools are powerful. Keeping up with them is the hard part.

You are juggling multiple tasks, multiple sessions, and multiple projects, each with its own context and momentum. The AI does not lose the thread. You do.

That is the real drag: not generating code, but constantly rebuilding context, reloading intent, and getting your bearings again. There is a name for that feeling now: AI coding fatigue.

SlyCode exists because the biggest problem in AI development is not the model. It is everything around the model.

What if the card was the workspace?

Instead of separating planning from doing, SlyCode keeps the task, its context, and its live working session in one place.

A SlyCode card showing a task with tags, checklist progress, and bug indicator

Every task lives on a card: title, description, checklist, and status in one place.

What needs to happen

Title, description, checklist, acceptance criteria.

Why it matters

Problem context, design documents, feature documents.

Where you do it

A live terminal session that already knows the task.

Click a card, and you are working. Not setting up. Not searching for the last session. Working.

Build wherever you are

Your best thinking doesn't happen at a desk.

Turn a rough idea into a structured task while you are away from your desk, then pick it back up with real progress already attached.

8:15 AM

The park

School run done. Your phone buzzes with the morning summary, and you keep walking.

8:20 AM

A new card

An idea lands. You speak it out loud, and it becomes a card in the workflow.

8:25 AM

Design

You pull up the task, talk through the shape of the solution, and the AI turns that conversation into a design you can actually build from.

8:40 AM

Moving forward

The task is no longer just an idea. The card has context, direction, and enough structure for the work to keep moving.

9:00 AM

Back at the desk

You sit down, open SlyCode, and pick the task back up with real progress already attached to it.

SlyCode Telegram bot: project selection and session commandsSlyCode Telegram bot: card actions with onboard, context, and show cardSlyCode Telegram bot: voice messages and card status

Remember, you were working before you sat down.

Features

Built for the workflow, not just the prompt.

Move work through a structured flow, with the AI able to update cards as the task progresses. Turn a rough idea into a clear task, generate design and feature documents before building, implement against a plan, and test before you ship.

01

Capture the work

Start with a rough task and turn it into something actionable.

02

Onboard the task

Add scope, intent, and the context needed to move forward.

03

Design and specify

Generate design and feature documents before building, so the work starts from a clearer plan.

04

Implement with structure

Build against the task's plan and context, while the workflow stays attached to the work.

05

Test and review

Close the loop with structured checks before the card moves on.

Powered by built-in skills and actions, but designed to feel like one workflow.

Pricing

Free for solo developers.

The complete solo developer experience ships at no cost. Teams support is on the way.

Current

Free

The full system. No gates.

  • BYO CLI tool (Claude, Codex, Gemini)
  • Kanban board with full workflow
  • Multiple projects
  • Automations and context priming
  • Mobile messaging
Get Started
Coming Soon

Teams

Solo today. Your team when you're ready.

Shared workflows, team visibility, and a setup built for organization use.

  • Everything in Free
  • Shared workspaces
  • Role-based access
  • Workflow integrations
  • Team-wide visibility

Get Started

Get up and running in under five minutes.

Everything you need to start working ships in a single scaffold.

npx @slycode/create-slycode slycode

Requires Node.js 20+

1

Scaffold

npx @slycode/create-slycode slycode

The setup wizard walks you through five quick questions: ports, integrations, services.

You can name the folder anything you like.

2

Launch

cd slycode && slycode start

Starts the SlyCode services.

On Windows, use npx slycode start. All slycode CLI commands require the npx prefix on Windows.

3

Open

localhost:7591

Open SlyCode in your browser. The SlyCode tutorial will be in the dashboard and will help you get started.

4

Build

Once you are familiar, create a new project or add an existing one and SlyCode will help you manage it.

What you bring

  • SlyCode works alongside your existing setup.
  • Bring the AI CLI tools you already use.
  • A code editor is still useful for manual edits, review, and project-wide navigation.
  • For mobile use, connect Telegram so you can create cards, shape tasks, and keep work moving away from your desk.

Running on a server?

SlyCode runs comfortably on 4 GB of memory. If you are running multiple sessions, create a 12 GB swap file to handle the extra load.

Help improve SlyCode

SlyCode is still evolving, and real-world feedback across tools, providers, and workflows is valuable. If you hit an issue or find a rough edge, report it here.