Some folks prefer TUI and some folks like Chat. @agentastic supports both. You can seamless switch between terminal agents and their chat interface in agentastic.dev by pressing ⌘+I (interface) or toggle it in the sidebear. You can also set the chat or terminal as the default for each agent.
Our terminal (which is a fork of libghostty) is also special that we preview images and files if you hover over them. This applies to local terminals, as well as VPS or Cloud VMs so you can see the image previews without needing to sync those files to local machine. Very handy for pasting local screenshots to the agent's terminal.
So conductor cloud is sunsetting, agentastic.dev on the other hand on the rise. You can bring all your configs/agents/worktrees to dev, and also all the cloud features are free (no subs required).
I am very excited to share that Conductor is joining Meta!
We have some big, crazy plans for the next interface. If you liked Conductor, you’re gonna love what’s coming.
We’re super excited to work with @natfriedman and @alexandr_wang at MSL to build it. They’ve been on an absolute tear, and I’m convinced MSL has the highest talent density of all the labs.
A huge thank you to our earliest believers @aaron_epstein, @ilyasu, and @nabeel. And to everyone here who tried Conductor, sent us feedback, and prompt requests - you made this so much fun. Thank you ❤️🚂
Choo choo!
This is an SF meetup you don't want to miss.
Real demos, tips, and workflows for agentic engineering. Expect engineers from @OpenAI, @cognition, @temporalio, @agentastic, and Qodo.
No shilling. They're sharing how they build with Codex, Claude Code, and other coding agents.
Wed, Sept 30 at @okta offices 📍 RSVP now:
luma.com/ai-agentic-coding
I'm the second presenter here, jump to 30m mark to check out agentastic.dev, where we talk and demo AI factories, long-horizon manager agents, and fab: our new agent analytic platform for understanding how agents operate in your factory. This also gives a glimpse of the direction where Dev is headed.
AI-native workshop [006] nitter.cf/i/broadcasts/1qJVmyagm…
Introducing the browser-use skill in Agentastic[.]dev.
Dev now gives agents full browser control through dev browser, so they can open pages, inspect the app, click around, fill forms, wait for UI changes, and verify behavior from the terminal. This is a huge step toward true autonomous web dev.
We added a new feature called Agent Home. We really like it! It lets you submit the same task to multiple agents simultaneously, we take care of creating work-trees and running the agent in the background. Watching 10s of agents spin-up on-demands is a sight to be see.
Claude can now use multi-agent orchestration in separate processes/tabs. tmux (any terminal) or iterm2 terminal support this by default. AgentasticDev uses a native terminal (libghostty), so tmux is supported out of the box. But the question is can ghostty support native tab splitting like iterm2. The source article said ghostty was not supported, I don’t believe it. So I set to implement this feature in Dev.
Claude can now create tabs for its sub-agents, and you can click/interact or re-arrange each tab. We believe native tabs are much better UX than tmux, and definitely much more customizable.
We released @agentastic Dev v0.5. This version brings some of the most requested features as well as usability improvements.
Containers: Containers provide full isolation, so you don't need to worry about agent deleting your production tables. This was the most-requested feature since our beta launch last week. Docker containers are now supported (req. docker), so you can use them in addition to the work-trees for full isolation. The code is synced between local worktree and container, so you can view view, edit or test agent's changes immediately.









