Browse all 9 articles in this open-source series. Understand Orca’s desktop, worktree and remote-runtime roles before increasing the number of concurrent coding tasks.
Featured starting point
Understand Orca’s desktop, worktree and remote-runtime roles before increasing the number of concurrent coding tasks.
Suggested learning path
01 → 09
Understand Orca’s desktop, worktree and remote-runtime roles before increasing the number of concurrent coding tasks.
Check task identity, terminal location and a small diff before experimenting with parallel agents or remote access.
Use the pinned Linux guide to plan a private runtime without mistaking an advertised address for network isolation.
Map local coding work, headless runtime access and the documented mobile relay without assuming all traffic uses one path.
Follow Node and Electron checks, selective rebuilding and fresh-process verification in ensure-native-runtime.mjs.
Compare a fixed task set while recording integration conflicts, model usage and review effort.
Keep repository separation distinct from process permissions and review remote access before connecting devices.
Match the interface to task coordination and operating needs instead of choosing from agent counts.
Create a learning tool that records host, worktree and acceptance evidence without automating merges or deleting unfinished work.
