Conduit is a "workspace manager" for parallelizing coding tasks with agents, across both local and cloud compute. It allows you to design bespoke development workflows, which are organized as arbitrarily-flexible tabs of terminals, editors, and browsers.
Why is this interesting? Because CLIs and coding agents are getting increasingly powerful, and so the aforementioned primitives may eventually be all that you need? 🤔 Or maybe not! It's just an exploration, and meant to be fun.
- Grab the latest release (currently macOS-only)
- Learn more by reading the feature reference and/or checking out the screenshots below 👇
- Follow along with our updates by subscribing to the Conduit releases
- File an issue with any feedback, questions, ideas, etc. 🚀
Create information-dense tabs, each with a flexible grid of terminal, editor, and browser panes (that can be resized, organized, collapsed, and cloned)
And once your tabs feel exactly like you want, you can then lock them, to prevent accidentally changes.
Create isolated agent sandboxes, by simply spliting new terminals, or duplicating tabs, with automatic worktree management.
Spin up cloud terminals and intermingle them with local terminals, so you can parallelize your tasks even further.
Define and configure all of the coding agents you use, so you can quickly recall them via a slash command from any terminal.
Organize your tabs by creating or removing panes, drag & dropping panes, splitting panes into new tabs, moving panes between tabs, etc. All with a fun and visual editing surface.
You can also configure the radial "quick actions", so its simple to create the exact panes and layouts you want.
Zoom in and out of panes in a tab (w/cmd+option+f), so you can seamlessly transition between focusing and observing (with a really fun minimap!)
Hover over any tab and see a live preview of its status. This is kind of like "peek definition" for tabs, and makes it easy to parallelize work, while keeping an eye on background tasks.
When you have multiple tabs, you can open a live "birds-eye view" of them all, which makes it easy to observe multiple tasks at once.
Add editor panes to any tab, which provide a file explorer + text editor, complete with real-time git status, diffs, and the ability to stage, commit, push and pull changes.
And because markdown is so central to most devs/projects, the editor pane includes an integrated markdown preview as well:
When you click a URL in your terminal, it will open a new browser pane, which allows you to navigate, test, debug, and favorite web pages, without needing to context switch.
Perform one-off actions without needing to disrupt your tab layouts, or switching to another tool.
Using the conduit CLI, you (and your coding agents!) can design, interact, and automate every part of your dev environment (including terminals and browsers!).
Create multiple terminal panes, that can be synchronized, so that as you type, you can orchestrate/steer them all at once.
Save and restore sets of tabs, so you can jump in and out of projects with ease.
Configure the keybindings that are used for common actions, so you can maximize your flow state exactly as you want it.
Run global commands at any time (cmd+shift+p), including spinning up quick terminal instances (w/an MRU list).
Conduit was born out of the following key assumptions:
-
Developers will continue to make use of multiple different coding agents, because no single agent will (ever?) serve all their needs. Therefore, it's critcal to have toolchains that allow a "learn once, use any agent" experience.
-
Coding agents will continue to evolve at a rapid pace, and putting too many abstractions on top of them will creation friction in the availability of innovation. Therefore, developers want to be as "close to the metal" as possible with their agents.
-
Coding agents will continue to get more powerful over time, and therefore, a CLI interface, along with supporting tools, will be sufficient for most users. Therefore, toolchains should embrace terminals as being central vs. secondary.
-
Developers love hackable environments, but with smart defaults. That way they can get started quickly, but without compromising on their flow. Therefore, agentic surfaces must embrace compsability and personalization at its core.