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 that the a-ha is the orchestration and outputs. We'll keep this in mind as we build out our gallery and demos going forward.

2) Right now our primary users are knowledge workers and researchers who need to do complex, multi-step work. The benchmarks help establish credibility, but we're building out more use case demos and a gallery to make it tangible for a broader audience. On the human-in-the-loop point, the agents do pause and come back to the user, and there is scope for iterations as well, but we haven't highlighted this well enough. We'll do a better job of showing that going forward.

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 visualize what's happening. Good note on the demo topic though, we have some broader, non-AI demos coming soon on our website and newsletter.

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 models/providers. If that fails, the agents look for alternate approaches to accomplish the same task (e.g. falling back to web search instead of browser use).

For completeness, you can also manually re-run or edit individual blocks if they fail (though the agents may or may not consider this depending on where they are in their flow).

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 between blocks without polluting the agents' context windows.

On conflict resolution, the synthesizer block can see all upstream outputs, so it has full visibility into any divergence. It does surface contradictions to the user, though this is something we're constantly improving.

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 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.

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 ways depending on the workflow.

Kavla looks cool, canvas-based SQL is a great use case for this kind of thinking!

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 needed. The daily refresh just tops you back up over time so you're not waiting for a monthly reset.

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.