Migrate from Conductor
Import your local Conductor repositories and workspaces into Agentastic, review lifecycle scripts, and continue working on your existing branches.
Bring your local Conductor work into Agentastic with Import from Other Apps…. Agentastic opens existing repositories and worktrees in place, so your branches, files, and uncommitted changes stay in their current folders.
What comes across#
| In Conductor | In Agentastic |
|---|---|
| Local repository | Repository in the sidebar, using the existing checkout |
| Local workspace | Existing Git worktree, opened at its current path |
| Workspace name and pin | Imported name and pin, preserving existing local choices |
| Explicit archive state | Reviewed archive state; uncertain entries appear under Needs review |
| Setup, archive, and run scripts | Supported commands offered for review and translation into native configuration and run tasks |
| Running agents and conversations | Start or resume separately; import does not launch an agent |
This guide covers local Conductor workspaces. Remote and sandbox-hosted Conductor workspaces are skipped by the importer. Missing checkouts are not downloaded or recreated.
1. Install Agentastic#
Follow Installation, then open Agentastic on the Mac where you use Conductor. Keep your existing repository and workspace folders available. You do not need to clone your repositories again.
Before switching, let running agents finish or stop them in Conductor so two agents do not edit the same checkout at once.
2. Import your Conductor workspaces#
- Choose File > Import from Other Apps…. You can also open import from the welcome screen or Settings > Workspaces.
- Review the repositories and workspaces listed under Conductor. Check their paths and select the ones you want to bring over.
- Check archive decisions. A workspace with uncertain lifecycle information appears under Needs review; select it to keep it managed locally.
- Choose whether to enable Follow new workspaces for Conductor. This rechecks source metadata when local repositories refresh, so you can keep using both apps during the transition. Manual changes in Agentastic take priority.
- Choose Bring it over to apply your selections.
Import reads Conductor's local database at ~/Library/Application Support/com.conductor.app/conductor.db. It recognizes supported legacy and current local workspace layouts, including explicit custom workspace paths.
The import does not move files, run setup or archive commands, or stop terminals. Existing names and archive choices you already made in Agentastic are preserved. See Import from Other Apps for the full review and following behavior.
Imported workspaces still use their original folders. Keep those folders while you use them in Agentastic, and avoid deleting or archiving the same checkout from Conductor.
3. Review your scripts#
The import review can offer supported commands from conductor.json or .conductor/settings.toml. Script configuration is unchecked by default: inspect the commands and warnings before selecting it.
Approved setup and archive commands become native configuration; supported run commands become run tasks. Import does not execute them or overwrite existing native configuration. Unsupported fields are reported as warnings, so check any named actions or custom settings before relying on them.
For example, review a setup command that installs dependencies, a run command that starts your dev server, and an archive command that stops local services. Confirm that paths and external tools still make sense in the imported checkout and in a newly created worktree.
Agentastic provides Conductor-compatible environment aliases and a persistent block of ten ports per worktree. Port allocation does not reserve sockets, and source-specific named port declarations are not migrated. Check your server's port settings when running several worktrees.
For new worktrees, see Setup & Teardown Scripts. .worktreeinclude patterns can also bring Git-ignored files into new local worktrees.
4. Continue with your agent#
Open an imported workspace and start your preferred agent. See Supported Providers and Your First Agent for setup.
Conductor chat history and running processes are not transferred by this import. If your agent CLI saved a conversation locally, use its resume workflow from the imported checkout. Otherwise, start a fresh conversation with a short summary of the task and the current changes.
Authentication, trust grants, and permission bypasses are not migrated. Set up any required provider authentication before starting work.
5. Review and ship#
Use Source Control to inspect changes and commit your work, and the Diff Viewer to review edits. For another task, create a Git worktree and run an agent on its own branch.
When you finish switching, turn off Follow new workspaces under Settings > Workspaces > Import if you no longer want Conductor metadata reconciled. Previously imported values remain. Keep any Conductor workspace directories that Agentastic still uses.
If something is missing#
Check that the repository and workspace still exist on this Mac. In the main repository, run:
git worktree listCompare those paths with the import review. Remote workspaces and missing folders will not be brought over. If a local repository is not detected, open its existing checkout in Agentastic and check its worktrees there.
To revert the latest import, choose Undo Import in the review window. Undo survives app restarts and preserves later edits; repositories opened during import remain open. See Import from Other Apps for details.