Your project stays intact, your agents stay separated, your attention stays on the work.
- Thought
- 4s
- Read
- AppManager.tsx
- Searched
- expose patterns
Drafted implementation steps in feature-prd.md. A few quick questions before I start building:
How should Mission Control be triggered?
- 1Gesture (swipe up with 3 fingers)
- 2Keyboard shortcut (e.g., F3 or Cmd+F3)
- 3Both keyboard and button
Mission Control Interface
A grid view of all open windows as scaled previews, allowing quick selection to bring any window to front.
Trigger
Menu item in MenuBar.tsx (View > Mission Control), hotkey F3, or double-tap desktop.
View Behavior
Overlay existing windows into a grid of live previews with spring-based layout animations and shared element transitions.
- Add multiplayer mode to useAppStore.ts
- Create a new MissionControlView.tsx component
- Update AppManager.tsx to apply expose modes.
- Add a task, ⌘K to generate…
Claude Code, Codex, OpenCode, you choose your agent, we just made it feel at home.
On it. I'll build the dashboard using your theme config, wire up the research data, and add interactive charts with public access controls.
Done! Here's a walkthrough.
Tight integration when you want it. Any terminal agent when you need it. Never a tradeoff on isolation.
i wanna be able to go to cursor.com/changelog#1.0 to see 1.0 changelog
checks out
@cursor can yo…
I added direct li…
constraints acro…
@cursor can you review this PR?
The composerOpenModeToggleKeybinding is a function that needs to be called to get its value. This makes the condition always truthy.
Open a workspace, spin up a new worktree, check on an agent, never click a button.
"use client"
import React, { useState } from "react"
import Navigation from "./Navigation"
import Dashboard from "./Dashboard"
import { fetchTelemetry } from "@/lib/telemetry"
export default function Dashboard() {
const [ready, setReady] = useState(false)
// spin up worktree, attach agent, return view
}Join the waitlist.
We'll let you know when it's done baking.