a24venka

6 ms·

1.
by a24venka 6mo ago
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 that the a-ha is the orchestration and outputs. We'l
2.
by a24venka 6mo ago
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 agents do better work and give users the ability to audit and
3.
by a24venka 6mo ago
This is really great to hear, thank you! Have fun with the prototype, let us know how it goes.
4.
by a24venka 6mo ago
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 models/providers. If that fails, the agents look for alterna
5.
by a24venka 6mo ago
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 with exactly what it needs. On the eval side, we ran Spine Swar
6.
by a24venka 6mo ago
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.
7.
by a24venka 6mo ago
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 between blocks without polluting the agents' conte
8.
by a24venka 6mo ago
Agreed. The term has been overloaded lately. We also refer to it as a visual workspace which perhaps captures it a bit better.
9.
by a24venka 6mo ago
Agreed. We will make sure this comes through in our website.
10.
by a24venka 6mo ago
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) G
11.
by a24venka 6mo ago
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 outputs you can export and use independently. So it works both
12.
by a24venka 6mo ago
This is good feedback and definitely something we are improving.
13.
by a24venka 6mo ago
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 needed. The daily refresh just tops you back up ove
14.
by a24venka 6mo ago
Definite miss on our part, we're working on making the product experience more visible upfront on our landing page.
15.
by a24venka 6mo ago
Good call and noted. We're working on making the product experience more visible upfront.
16.
by a24venka 6mo ago
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 (the chat, task and deliverable) that have alternate views of w
17.
by a24venka 6mo ago
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, while browser use or deliverable blocks like documents and spre
18.
by a24venka 6mo ago
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 definitely do a better job signaling that before you hit th
19.
by a24venka 6mo ago
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 other's outputs — so the plumbing is there,
20.
by a24venka 6mo ago
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 want to trace back why an output wasn't what you expec
21.
by a24venka 6mo ago
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.
22.
Launch HN: Spine Swarm (YC S23) – AI agents that collaborate on a visual canvas(getspine.ai)
109 points by a24venka 6mo ago|69 comments
23.
Why file systems are the wrong workspace for AI agents(blog.getspine.ai)
6 points by a24venka 6mo ago|1 comments
24.
by a24venka 6mo ago
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/writing to a file system, we built a visual canvas
25.
by a24venka 9mo ago
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 more first principles approach to the code and can reason a
26.
Spine AI (YC S23) is hiring a senior back end engineer(ycombinator.com)
1 points by a24venka 2y ago
27.
Spine AI (YC S23) Is Hiring(ycombinator.com)
1 points by a24venka 3y ago
28.
Spine AI (YC S23) Is Hiring a Lead ML Scientist(ycombinator.com)
1 points by a24venka 3y ago