[Feature]: Cross-Workspace Pipelines

[jamesruscoe]

Platform

macOS

Operating system version

tahoe 26.3

System architecture

Intel (x86)

PolyScope Version

0.11.0

Bug description

Feature Request: Cross-Workspace Pipelines

The Problem

When building features that span multiple repos (e.g. Laravel API + Vue frontend), Polyscope workspaces are completely isolated. Agents can't trigger each other, share context, or communicate. The user has to manually coordinate everything.

Proposed Features

1. Pipeline Mode — Chain workspaces together so one finishing triggers the next, passing artifacts between them
2. File-Watch Triggers — A workspace wakes up automatically when a shared context file changes if told it will need to make FE changes
3. Cross-Workspace Messaging — Agents can ask each other questions directly instead of through the user
4. Managed Shared Context — Polyscope handles a shared directory across repos that agents can read/write to without sandbox restrictions

How It Works Today (Manual Workaround)

You can get a basic version of this working, but you are the glue at every step.

One-Time Setup

1. Create a shared directory: ~/.polyscope/shared-context
2. Add this to your global ~/.claude/CLAUDE.md so all agents know about it:

## Cross-Repo Shared Context
Shared context path: /Users/<you>/.polyscope/shared-context/
When building cross-repo features, check this directory for API contracts before starting work.

Workflow

1. Open a BE workspace. Prompt it:

"Build something services controllers etc general CRUD - when finished spit out all contacts that have been made such as routes and the things that are required by the BE to function that the front end needs to send"

2. Copy the contract. The agent outputs it in the chat. You manually save it to:

~/.polyscope/shared-context/context.md

(The agent can't write there itself — it's sandboxed to its repo clone.)

3. Open a FE workspace. Prompt it:

"Read /Users/<you>/.polyscope/shared-context/context.md first, then build the service layer, types, store, and views to match."

That's it. Three steps, two manual handoffs. It works but you're the pipeline.

What Pipelines Would Replace

Instead of three manual steps, you'd define one pipeline and hit go. Polyscope sequences the workspaces, passes the contract file automatically, and you review two PRs at the end.

Steps to reproduce

No response

Relevant log output