Scindo

A workspace where humans and AI agents collaborate in the same threads. The agent captures decisions, drafts plans, and opens PRs, shared context from conversation to shipped code.

Scindo workspace

The Problem

Teams discuss in Slack, copy-paste to Claude or Cursor, then bring results back. Decisions get buried. Each developer's AI agent works in isolation with zero team context. Five tools for what should be one conversation.

Decisions

One thread, three surfaces. PMs and designers live in a browser, developers in an editor and a terminal, so Scindo meets each where they are with a web app, a VS Code extension, and a CLI, and keeps the same thread and agent context under all three. The alternative, one app everyone must switch to, is the reason the copy-paste loop existed in the first place.

Every agent action shows its intent before it runs. Opening a PR, creating a task, turning a thread into a document: each one previews what it is about to do and waits. This is the same rule as the Corrigo agents, applied to an agent that can touch a codebase. The person keeps the last word.

The canvas sits beside the conversation, not inside it. Diffs, documents, and previews would otherwise scroll away in the thread that produced them. Keeping them in a pane of their own lets a thread hold a decision and its evidence at the same time.

I built it instead of specifying it. Design, frontend, backend, the extension, and the CLI. A spec would have let the interesting questions stay open, and the code did not.

What I Built

Made by oneSlash, design, frontend, backend, VS Code extension, and CLI. Shipped v1 with real-time messaging, agent collaboration, GitHub integration, canvas, and semantic search. scindo.one