Launching today
Clark
An AI coworker with its own cloud computer
673 followers
An AI coworker with its own cloud computer
673 followers
Clark is an AI coworker with its own cloud computer - browser, terminal, files, and code. Hand it a real task, close the tab, and come back to finished work: wide, sourced research; websites; spreadsheets; decks; audits; or tested code. It can fan work out to parallel specialists, run on a schedule, and return artifacts with the evidence behind them. Use Clark on web or mobile, work in real repositories with Clark Code, or embed the agent through an OpenAI-compatible API.
Free Options
Launch Team / Built With
Clark
@stanislav_kirdey To be honest , I am actually waiting for something that can own an entire workflow instead of just helping with one prompt at a time. The cloud computer+ parallel specialists approach is a really interesting direction. Excited to give it a try.
Clark
@james_anderson77 thanks!
share your feedback here or on the app 💜
@stanislav_kirdey Seriously the ability to walk away from a task and come back to finished work is exactly the kind of experience I've been hoping AI would evolve toward . Excited to try this out.
@stanislav_kirdey What’s one real task you’d hand Clark right now and why; and what would you need to see in the returned files or logs to feel confident you could rely on it again?
Clark
@swati_paliwal i handle it a lot of prototype app building, very wide research, git repo analysis, anything where agent with browser can be great like filling out forms etc, and it manages my calendar too!
The 'own cloud computer' framing is what separates this from a chat wrapper for me — but it lives or dies on state. Between tasks, is each job a fresh ephemeral VM wiped clean every time, or a durable workspace that keeps files and context so a scheduled monitor run actually builds on the last one? And with Clark Code in a real repo, does it work on a clone in its own env and hand back a PR/diff I can inspect, or does it need direct write access to the repo?
Clark
@noctis06 clark code it will work in the repo and do the changes just like codex or claude
Clark
@hamza_afzal_butt yes it can!
Congrats on the launch. I like that it's async, you send a task and leave instead of babysitting the agent the whole way. My one nervous question before handing an agent a real repo: when Clark Code patches something while I'm gone, is it scoped to a branch or PR I get to review, or can it land straight on main? Trying to picture the blast radius before I point it at anything that matters.
Clark
@vollos clark code could work on main, but optimized for worktrees
would love your feedback on what would work best by default
@stanislav_kirdey For me the default has to be the safe one: worktrees or a branch, never straight to main. A default is what everyone who skips the docs ends up running, and async is exactly when nobody's watching. If the one time it goes sideways it's already on main, there was no gate to catch it. I'd make branch-or-PR the default and let people opt into main once they trust it on their own repo.
todai
Clark
@umar_saleem clark code
www.clarkchat.com/clark-code should be able to navigate them with ease!
"Its own cloud computer" is a meaningfully different architecture than most AI-coworker tools that just call APIs — giving it a persistent environment changes what it can actually do end-to-end. Curious how you're handling security/sandboxing for that computer, especially once it's doing real multi-step tasks unsupervised. That's usually the part that keeps teams from trusting autonomous agents with anything consequential.
the sandboxing/state questions above cover the trust side well. curious about the fan-out mechanic specifically - when Clark splits a task across parallel specialists, do they each get an isolated environment that gets merged into the final artifact, or do they share the same cloud computer/workspace while running concurrently? asking because shared-state parallelism is where I'd expect the weird bugs to show up first