Sinaris

简体中文

Compatibility notice: Sinaris is currently verified with Cursor Agent. Copilot and other AI coding agents are planned for future integrations.

A shared task board for AI coding agents — coordinate Cursor, Copilot, and other agents around confirmed goals, requirements, decisions, and execution plans.

Use Guide or Proposal to make direction explicit, Design to turn direction into executable work, and Apply to move implementation forward. Sinaris keeps decisions and progress durable so the next agent session does not have to start from scratch.

---

What Problem Does It Solve?

When using AI agents to build software, the hard parts are usually not local code generation. The hard parts are:

1. Lost context — after a chat is interrupted, the next agent does not know what was already decided.
2. Broken handoffs — when one task finishes, the next step often still depends on a human repeating instructions.
3. Invisible progress — with multiple chats or agents involved, it becomes difficult to know what is done, blocked, or next.

Sinaris provides a stable control plane for AI coding.

It extracts project-critical context from chat history into reviewable, traceable, resumable project resources. The shared task board shows project state, while timely context injection keeps every agent aligned with the same confirmed facts.

Sinaris is not just about getting an AI to write the next code snippet. It is about helping AI agents deliver real projects continuously and under control.

---

Product Idea

In one sentence: Sinaris turns AI coding from one-off chat into a trackable, resumable, collaborative execution workflow.

• Confirmed goals, requirements, decisions, and plans become durable project assets.
• The Hub keeps requirements, plans, agents, and progress visible in one place.
• Cursor, Copilot, and other agents can continue work against the same plan after interruptions.

For the deeper product architecture, see docs/product-architecture.md.

---

Preview

Explore the public documentation site: Sinaris Docs.

Open the prototypes directly: desktop Hub or mobile Hub.

Sinaris gives AI coding work a cockpit. The Hub shows the project plan, ready work, blocked journeys, agent sessions, and delivery status in one place, so the team can tell what should happen next without reading through old chats.

Area	Why it matters
Plans	Turn Guide, Proposal, and Design into durable project memory.
Board	Show what can be claimed now, what is blocked, and who owns the work.
Activity	Make agent events, decision requests, and resume messages traceable.
Evaluator	Track high-value journeys and release confidence beyond task completion.

Explore the visual product tour for a guided overview.

Demo: From Guide To Hub Control Plane

A beginner can start with /sx-guide. Guide uses an ICOD loop to ask one focused question at a time, then writes the confirmed project basis: goal, users, value, success criteria, scope boundary, capability inventory, and milestone roadmap.

Those confirmed facts become the control data for the rest of Sinaris. Design asks the next architectural question with a recommended option.

The Hub is the visible control plane driven by that data: plans, phases, tasks, agent sessions, activity, and evaluator confidence are shown together so a beginner can see what should happen next.

---

Installation

Sinaris is distributed as a .NET global tool. You do not need .NET knowledge or a C# project; the .NET SDK only provides the dotnet command used to install and update Sinaris.

Install the .NET 10 SDK first:

# macOS with Homebrew
brew install --cask dotnet-sdk

# Verify the SDK is available
dotnet --version

# Windows with winget
winget install Microsoft.DotNet.SDK.10

# Restart the terminal, then verify the SDK is available
dotnet --version

# Linux or non-admin install
curl -sSL https://dot.net/v1/dotnet-install.sh -o dotnet-install.sh
bash dotnet-install.sh --channel 10.0
export PATH="$HOME/.dotnet:$HOME/.dotnet/tools:$PATH"

# Verify the SDK is available
dotnet --version

Then install Sinaris for the first time:

dotnet tool install --global Sinaris.Cli

If Sinaris is already installed, update it instead:

dotnet tool update --global Sinaris.Cli

Verify the CLI is ready:

sinaris --version

Complete Quick Start

# 1. Go to your project root
cd /path/to/your-project

# 2. Initialize Sinaris assets and workspace state
sinaris init

# 3. On the first run, choose one target platform when prompted:
#    1 = Copilot, 2 = Cursor

# 4. Open the Hub to inspect plans, tasks, agents, and activity
sinaris hub

Then open Cursor and choose the short Sinaris command that matches the project state:

• New project: start with /sx-guide to confirm project goals and the milestone roadmap.
• New requirement in an existing project: start with /sx-proposal to clarify intent, impact, and decisions.
• Direction is already confirmed: use /sx-design to turn goals or requirements into executable plans.
• Ready to implement: use /sx-apply to let agents execute planned tasks.

Open the Hub when you need to inspect progress:

sinaris hub

When context is interrupted, resume an existing agent session:

sinaris agent resume --session <session-id>

---

Core Features

• Two explicit entry points: Guide for new projects; Proposal for new requirements in existing projects.
• Design before execution: Design turns direction into plans; Apply moves implementation forward.
• Visible progress: the Hub shows requirements, plans, tasks, agents, and progress without digging through chat history.
• Resumable execution: continue an existing agent session without restating the project background.
• Multi-agent handoff: Cursor, Copilot, and other agents can collaborate around the same plan.
• Safer initialization: init avoids silent asset overwrites and asks before irreversible operations.

---

User-Facing Commands

Goal	Command
Initialize a project	sinaris init
Open the Hub	sinaris hub
Resume an existing agent session	sinaris agent resume --session <id>

Guide, Proposal, Design, and Apply are usually used from your IDE. For the complete CLI protocol, see docs/cli-protocol.md.

---

Typical Workflows

Guide and Proposal are different entry points. Neither is universally preferred. Choose based on project state: use Guide for a new project; use Proposal for a concrete new requirement, change, or idea in an existing project.

Scenario 1: Guide -> Design -> Apply

1. Run sinaris init to enable Sinaris in the current project.
2. In Cursor, enter /sx-guide to confirm project goals and milestones.
3. Enter /sx-design to split the current phase into executable work.
4. Enter /sx-apply to let the agent implement against the plan.
5. After interruption, use sinaris agent resume --session <id> to return to the same conversation.

Scenario 2: Proposal -> Design -> Apply

Use this when the project already has a goal and roadmap, and a new requirement, change, or idea arrives.

1. Run sinaris init to confirm the current project is Sinaris-enabled.
2. In Cursor, enter /sx-proposal to discuss one requirement's goal, impact, and recommended direction.
3. After the user confirms the Final Proposal Summary, Sinaris adds the requirement to the project plan.
4. When the requirement is ready for solution design, enter /sx-design to split it into executable work.
5. Enter /sx-apply to implement the planned tasks.
6. Open sinaris hub to inspect requirements, plans, and progress.
7. After interruption, use sinaris agent resume --session <id> to return to the same conversation.

---

Learn More

• For design rationale, see Product Architecture.
• For automation and full command details, see CLI Protocol.
• For version history, see CHANGELOG.

---

License

MIT