{"slug": "conductor-0-63-0-cursor-support-dispatcher", "title": "Conductor 0.63.0: Cursor support & Dispatcher", "summary": "Conductor 0.63.0 adds support for Cursor Composer 2.5 and introduces the Dispatcher for workspace creation. The update includes improvements to terminal scrollback, auto-run scripts, and preview URLs, along with multiple bug fixes.", "body_md": "Cursor 🤝 Conductor\nConductor now supports Cursor Composer 2.5! It's fast, precise, and cost-efficient. We're excited to see how it improves your workflow.\nTo get started, select Composer 2.5 in the model picker. You'll have to grab a Cursor API key and add it in Settings → Providers.\nIntroducing _Dispatcher_\nWe've added a new way to kick off a workspace: the **Dispatcher**. When you create a new workspace, Conductor opens the Dispatcher so you can submit a prompt.\nToggle on create more to keep dispatching requests. Open Dispatcher with ⌘N.\nImprovements\nAdded a terminal scrollback limit setting in Advanced settings, shown as an approximate MB limit. The default scrollback limit is 10 MB, and persisted terminal snapshots retain the configured scrollback.\nAdded a setting to start run scripts automatically after new local workspaces finish setup. The setting can be configured globally or per repository through scripts.auto_run_after_setup.\nAdded a General preference to apply downloaded updates automatically when local agents are idle, using the existing Restart when idle update flow.\nAdded support for multiple named Preview URLs, with a split-button Open menu and reordering controls in settings.\nImproved responsiveness when Conductor has many archived workspaces by reducing broad workspace subscriptions in common app chrome.\nFixes\nFixed an issue where interactive agent questions could fail or get stuck instead of showing a response prompt.\nFixed the dashed plan-mode border shifting the layout and cutting through the middle of the new-workspace composer.\nFixed setup and run script configuration buttons that opened the wrong repository settings tab, and updated in-app help text from legacy conductor.json references to .conductor/settings.toml.\nFixed an issue where old managed settings at ~/.conductor/settings.json could be interpreted as user settings.\nFixed agents sometimes not having access to Conductor environment variables, such as CONDUCTOR_WORKSPACE_PATH.\nFixed an issue where repository setup, run, and archive scripts saved in older versions could stop applying after settings migration.\nFixed markdown links, file paths, images, code blocks, and Mermaid diagrams so they behave the same in Tufte and Default markdown styles.\nFixed blank web search previews in Codex sessions.\nFixed browser preview authentication for localhost dev servers by serving previews through localhost instead of 127.0.0.1, so cookie-based auth flows work in Conductor's preview browser.\nFixed an issue where opening Settings could request access to protected repo folders.\nFixed an issue where Claude auth checks could repeatedly trigger Claude Code hooks while Conductor was open.\nFixed an issue that stopped Bedrock authentication with CLAUDE_CODE_USE_BEDROCK=1 from automatically registering.", "url": "https://wpnews.pro/news/conductor-0-63-0-cursor-support-dispatcher", "canonical_source": "https://www.conductor.build/changelog/0.63.0-cursor-support-dispatcher", "published_at": "2026-06-08 00:00:00+00:00", "updated_at": "2026-06-16 01:53:33.328044+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools", "ai-agents"], "entities": ["Conductor", "Cursor", "Claude", "Bedrock"], "alternates": {"html": "https://wpnews.pro/news/conductor-0-63-0-cursor-support-dispatcher", "markdown": "https://wpnews.pro/news/conductor-0-63-0-cursor-support-dispatcher.md", "text": "https://wpnews.pro/news/conductor-0-63-0-cursor-support-dispatcher.txt", "jsonld": "https://wpnews.pro/news/conductor-0-63-0-cursor-support-dispatcher.jsonld"}}