Design Agent

Scindo

Team chat your AI agents can read. A message app keeps the conversation. Scindo keeps what the team agreed, and hands it to every person and every agent that asks, Claude included, so no one starts from a blank prompt.

Company
oneSlash
Product
Scindo
Role
Maker
Period
2024 – Present
Key metric
35 workspaces created
A Scindo thread where a PM, a designer, and a developer settle a billing page, with the agent saving the decisions and drafting the plan beside it
The thread, the saved decisions, and the plan drafted from it

The Problem

AI agents can write code, but they do not know what the team decided.

Teams discuss in Slack, copy-paste to Claude or Cursor, then bring results back. The decision lives in a thread, the plan lives in someone's head, and the PR surprises the team. Every agent session starts from zero.

Message Apps

Slack and Teams are good at the conversation.

They were not built for the agreement that comes out of it, or for agents that need to read it.

Decision

Read-only first, plan switcher in v2.1

Billing page v2 · 11/07/2026 · Sarah

Decisions

Decisions are saved with their source

In a message app a decision is one reply in a long thread. In Scindo you save it from the chat in one click, with who made it and the thread it came from, so you can still find it next month.

Invoice list

Agreed

Usage meter

Agreed

Empty states

Open
2 of 3 signed off

Plans

The plan is written down and shared

The agent drafts the plan from the thread, the team approves it, and the developer and the agent both read it. When the discussion changes, the plan changes with it.

Sarah Whitfield, Jinhwan Kim, George Lindqvist

ask the same agent

Scindo agent

Channels · tasks · documents · pull requests

One agent

One agent reads for the whole team

Everyone running a private AI session means the same questions asked again and answers nobody else sees. Scindo's agent reads the same channels, tasks, documents, and pull requests for the whole team, scoped to what each person can see. Direct messages are never included.

The page ships read-only first, with the plan switcher in v2.1.

Decision
Task
Thread

Answers

Answers cite their sources

Ask in plain words, from Scindo or from Claude or any MCP client, and the answer cites the decision, task, or thread behind it, so you can check it.

#214 Billing page v2

CI passed

Agreed

Read-only first

Retries with backoff

Built

Invoice list, usage meter

WebhookHandler with retries

Pull requests

The plan sits next to the diff

The reviewer, and the agent, see what was agreed beside what was built, so "That's not what we agreed on" gets said in review.

Decisions

01

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.

02

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 decides whether it goes ahead.

03

Approval refers to what is on the page.

The agent drafts the plan from the thread, each design decision records who raised it and who dissented, and editing the plan revokes earlier sign-offs. So nobody approves a version they have not seen.

04

I built it as well as designed it.

Design, frontend, backend, the extension, and the CLI. Writing the code answered questions a spec would have left open.

Ask Scindo

Any MCP client can ask Scindo what the team decided, and so can the Ask Scindo page inside the app.

The answer is built from the saved decisions, plans, threads, and tasks, scoped to what the person asking can see, with the sources linked under it.

Ask Scindo answering what the team decided about onboarding, with the two saved documents cited
Ask Scindo, an answer from the knowledge base with its sources
An agent answering a question about onboarding through the Scindo MCP server, with the decision, task, and thread cited
The same question from Claude over MCP, from the Scindo marketing page

Plans

The agent drafts the plan from the thread.

Each design decision records the options considered, the rationale, who raised it, and who dissented, and the plan shows how many people have signed off. Editing the plan revokes earlier sign-offs, so approval always refers to what is on the page.

The Scindo plan panel with requirements, a design decisions table, and a sign-off count
The plan drafted from the thread, with sign-off

Connect Any Agent

The same knowledge is open to the tools people already use.

Claude connects as a custom connector with sign-in and no API key. Claude Code, Gemini CLI, and Codex connect with a key that sees only what its owner can see, and can be revoked at any time.

Scindo setup, create an API key and connect Claude, Claude Code, Gemini CLI, Codex, or Claude Desktop
Setup, one endpoint for every MCP client

Three Surfaces

Web app for PMs and designers, VS Code extension for developers, CLI for terminal workflows.

All share the same threads and agent context.

The Scindo extension in VS Code, a chat panel in the sidebar beside the extension's details page
VS Code extension, chat panel in the editor
The Scindo CLI in a terminal, running login, workspaces, and read, with the agent answering a question about the latest request
CLI, terminal-native chat

What I Built

Made by oneSlash, design, frontend, backend, VS Code extension, and CLI.

Made by oneSlash, design, frontend, backend, VS Code extension, and CLI. Shipped v1 with real-time messaging, agent collaboration, and GitHub integration. Since then I rebuilt the positioning and the marketing page around one idea, agents that read what the team agreed, and added an MCP server so Claude connects as a custom connector with sign-in and no API key.

Closing

Scindo's own agent runs on Claude Haiku.

scindo.one

Scindo on Product Hunt

More Design Agent