Spine is the world's first truly agentic platform designed to manage and orchestrate the next generation of AI.
Read the original article
Comments
By nanookclaw 2026-03-1322:26 To your question about how others approach multi-step AI work beyond coding: I run an autonomous agent on OpenClaw that handles multi-day projects through structured state files and round-robin work loops. No visual canvas, but the same core pattern you discovered — externalizing context to persistent storage instead of holding it in memory.
The agent writes intermediate results to JSON state files and markdown logs between sessions. Each new session reads state from disk, picks up where the last one left off, and writes results back. Context never degrades because it is never held in a context window across boundaries — it is always reconstructed from structured files.
What breaks first: concurrent writes. When multiple cron-triggered sessions modify the same state file, you get race conditions. Your canvas model likely handles this more gracefully since blocks have defined ownership. For flat files the solution has been build locks and TTLs, which works but feels like reinventing what a proper DAG execution engine gives you for free.
The other thing that resonated: agents running longer when they delegate to blocks. Same pattern — my agent runs 58-minute work sessions and stays productive because it offloads all state to disk. The agent itself is stateless between sessions. The workspace IS the memory.
By orky56 2026-03-1322:23 Congrats on the launch. Few pieces of feedback that are similar in nature to what has already been shared but unique in terms of solutions.
1) The chat interface as shared in the video is a prime starting point to capture intent but anchors viewers to what Spine is all about. Try a show-tell-show approach where you can demonstrate (ideally above the fold) a compelling output, credits used and agents leverages, and THEN the simple prompt used to get it all started. Let's be real: the chat interface is not the a-ha moment. It's what you get out of it, the orchestration that happens behind the scenes, and finally the familiar chat interface that kicks it all off.
2) Who is the target persona for this? The benchmark accolade is great for the technical audience but they may not care about doing everything in the browser. The non-technical audience may like the browser but prefers examples of other companies and use cases are make the technical more accessible. The board concept helps the abstraction layer of understanding what is produced by the agents but the missing piece is memorializing the decision-making where human in the loop needs something to grasp & share.
I think this is really neat. You should probably take it as a compliment that the biggest criticisms so far are about the website landing page. ;)
I like canvases in general, and I especially like them for mentally organizing and referring to this sort of broad work. (Honestly, I think zoomable canvases would make a better window manager in general, but I digress)
One small piece of friction: My default mouse-based ways of dragging the canvas around (that work in most canvases like Figma) aren't working. I saw that you had a tutorial, and I have learned to hold space now, but I prefer the "hold middle mouse button to drag my canvas view around".
I've got a couple of research tasks running now, and my current open questions as a very new user are: 1) How easy will it be to store the outputs into a Github repository. 2) How easy will it be to refer back to this later? 3) Can I build upon it manually or automatically? 4) Can I (securely) share it with someone else for them to see and build upon it? 5) Can I do something "locally" with it? Not necessarily the model, but my preferred interface for LLMs at this point is Claude Code. Could I have a Claude Code instance running in one of these boxes somehow? 6) What if I want to do private stuff with it and don't like the traffic going through Spine's servers? Could I pay them for the interface, but bring my own keys? (Related: Can I self host somehow?) 7) When this is done, each artifact it found (screenshot, webpage, etc), is going to be helpful. The data-hoarder in me wants to make sure I can search these later. Heck, if I could do that, this would become my preferred "web browser". (But again, I digress.)
Really appreciate the detailed feedback and questions! And yes, we'll take the website criticism as a compliment :)
Good callout on the canvas navigation, we'll look into middle mouse button support.
To answer your questions: 1) GitHub integration is on our roadmap. Right now you can export outputs manually but we want to make this seamless. 2) All your canvases are saved and you can search them by name in your dashboard. We're also working on a dedicated section for deliverables across canvases. 3) Yes to both! You can manually add or edit blocks, or kick off new agent runs that build on existing work. 4) You can currently only share public links of your canvas to others (but you can make it private at any point). We are testing out a teams feature which allows you to share canvases with members on your team securely. Beyond that, we are working on adding roles and email-based sharing controls which is in our roadmap. 5) Claude Code in a block is a really interesting idea. We don't support that today but we're thinking about computer use and coding workflows. 6)BYOK (bring your own keys) is something we've heard interest in and are considering. Self-hosting isn't available right now, though we do support private deployments for enterprise customers if that's ever relevant. 7) Love the 'preferred web browser' framing. Right now you can search canvases but searchable artifacts across canvases is definitely where we want to head.
Thanks for giving it a real spin, this kind of feedback is incredibly valuable.
By swyx 2026-03-1316:56 > And yes, we'll take the website criticism as a compliment :)
ugh. guys. come on. stop celebrating at the 1 yard line. people are telling you they didnt even look at the product becacuse your landing page was so bad. you wasted your launch HN linking directly to it, ofc thats the first thing people are going to give feedback on. fix it right now you still have time.
