Viewing profile — a24venka

Really appreciate the detailed feedback. 1) Agreed on the show-tell-show framing: Chat is a natural starting point for people frustrated with linear interfaces, but you're right th…

Thanks for the feedback! On the chat interface point, we actually think chat is still a great way to get into the product, but we leverage the canvas behind the scenes to let the a…

This is really great to hear, thank you! Have fun with the prototype, let us know how it goes.

Spot on. The persistence layer is a huge part of what makes the canvas work. For failures, we handle it at multiple levels: first, standard retries and fallbacks to alternate model…

Great question. The core of Spine is coordinating multiple specialized agents across multiple models, using the canvas to store and pass context selectively so each agent works wit…

This is great to hear, thank you! Would love to hear your thoughts once you see your final report and explore some of those other opportunities.

Great framing. You're right that context fragility is a big part of it. The canvas helps because each block maintains its own context explicitly, and connected blocks pass context …

Agreed. The term has been overloaded lately. We also refer to it as a visual workspace which perhaps captures it a bit better.

Agreed. We will make sure this comes through in our website.

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 mo…

Thanks! Great question. We see canvases as living workspaces, you can revisit, iterate on, and build on them over time. But the deliverables (docs, slides, code) are first-class ou…

This is good feedback and definitely something we are improving.

The daily refresh isn't a cap on usage, it's additional credits you get each day (resets to 1,500 nightly regardless of use). You can use your full 30k balance in a single run if n…

Definite miss on our part, we're working on making the product experience more visible upfront on our landing page.

Good call and noted. We're working on making the product experience more visible upfront.

This is a fair point, we are exploring progressive disclosure on the canvas to better utilize the space and make the key artifacts more readily visible. We do have other panels (th…

Credits are consumed by the blocks that get generated, not by the agents themselves. Some blocks are cheaper than others. A simple prompt or image block is a single model call, whi…

Fair point, we should be more upfront about the sign-up step. Given that tasks are long-running and token-intensive, we do need an auth barrier to protect against abuse, but we can…

We've only partially explored this so far, but it's a great suggestion. The canvas architecture naturally supports this kind of loop since agents can already read and build on each…

That is definitely a valid way of using Spine as well. You can just work in the chat and consume the deliverables similar to how you would in other tools. The canvas helps when you…

Thanks for the feedback! Definitely agree that we could do more with the marketing site. We're working on a gallery page to showcase some demos.

Hey HN! We're Ashwin and Akshay from Spine AI ( https://www.getspine.ai ). Spine Swarm is a multi-agent system that works on an infinite visual canvas to complete complex non-codin…

Hey HN — Akshay & Ashwin here, co-founders of Spine AI (YC S23). We've been rethinking how AI agents work together. Instead of a single model in a chat loop or agents reading/writi…

There is a heavy emphasis on testing the code as the way to provide guarantees that it works. While this is a helpful tool, I often find that the best engineers are ones who take a…