For you, your agent, your coworker and their agent. It holds the team's critical know-how, research, decisions and data. But it's not a dead storage. It's a workspace that makes the context workable for humans as well as agents.
Free
Launch Team
AWS Startup AdvisorPersonalized AWS guidance that meets you where you’re already building
Promoted
How do you stop the canvas from becoming another messy place over time? Is there an agent workflow for cleaning up old context and decisions?
@ben_stephenson2 this is always a challenge. The brain is made to self-evolve and clean up. Project are made to be messy. We plan to have more agents soon so you can setup linting agent that goes over workspace and find things that are duplicate, old, and maybe not relevant!
@ben_stephenson2 yep we are working on a system that is going to help with this. We call it "gardener". It will run every morning and tell you what can should be merged / deleted / is out of date.
@ben_stephenson2 we are trying to find balance as AI is still not in the state of handling the context on its own, and we believe it is very important to keep human in the loop. we are working on "gardener" workflows which should make agent resurface relevant stuff and support this flow in more productive way
@ben_stephenson2 We are thinking about it this problem a lot and we are currently working on something we call a "gardener agent", that automates and simplifies this process.
I built something like this internally for our team - literally called it our Brain. The idea was they can use that context in Claude though and build skills against it, etc.
Is that possible, or can you only execute tasks within Kanwas? I love the idea of a Brain we can all visualise & collaboratively maintain/iterate in here but then use in claude.
@tom_rudnai1 Yes definitely. You can use Kanwas as the single source of truth for context that the whole team expands and edits and use it with other AI tools.
@tom_rudnai1 good to see you here Tom!!! Actually we built it so you can run any agent through CLI :)
@tom_rudnai1 exactly! updates work in both directions. you can bring anything in kanwas and iterate on all your signals, and also local/coding agent can pull the latest context and work with it
@tom_rudnai1 Yep, that’s the beauty of Kanwas being backed by simple file formats like Markdown. You can easily import and export everything.
love that it’s fully editable. my biggest fear with "ai brains" is when they hallucinate a decision we never actually made. being able to step in and refine the context keeps the agents from going off the rails. @johancutych
I am glad this is not another closed workspace where everything disappears into a proprietary database. Markdown/YAML plus Git history makes the product much easier to trust.
@mahin_makkhy This kind of interoperability was very important to us. We didn't want to vendor lock users to some proprietary format but rather let them work on markdown files.
Nice side-benefit of this is that you can use our CLI tool to export and import files easily
@mahin_makkhy .md files are way to go!!
@mahin_makkhy True! Markdowns are the way to go, and from our learnings agent works the best when it lives on top of it.
@mahin_makkhy I'm glad it resonates with you. We belive the era of heavy close, proprietary tools is comming to an end. Open source and open standards / formats are now important more than ever and we've been building Kanwas with this in mind since the first day.
@zuse yep collapsed outputs are hell, I've always liked canvas interface for any creative and iterative work. messy middle is the new moat!! thanks for shouts Tom!
@zuse Thank you! Team brainstorming session with Kanwas over Google Meet is one of our most favourite use cases. We all have the shared context, there is a visual reference to reason about, and we can ask the agent to check any facts or do some additional research as we go.
@zuse Yep we love to use for these creative sessions. There really is no good tool to do this in.
@zuse Thank you, Tomas! Canvas is a big part of the product, and our approach is to provide a more neutral space for brainstorming and creative thinking.
Nice, is it synced with any tools in particular?
@dan_tatar There are over 1000 native connections, and a native CLI tool that exposes the raw file system. I would say that the connection possibilities are only limited by imagination.
@dan_tatar we have all connections out there, plus cli as the input!
@dan_tatar Yep we are using composio.dev for all connections. There are more ten 1k+ and they work much better then MCPs
@dan_tatar we have 1k+ connections and it actually work wonders!
What does a Kanwas workspace look like after a project has been running for a month?
@igor_kuznietsov I would call it well oiled machine :) Folders that have nice compact human readable context that AI can use to make great decisions in. You will feel significantly more productive here then you would be in Claude chats and other linear tools.
@igor_kuznietsov That's a good question. In the ideas scenario, where you invest a bit of time into actively managing the context, it grows and compounds. You will have a lot of general context about the company, the market, etc. and also you will capture the specific work on specific problems like crafting marketing copy, PRDs or strategic documents, which both helps you get better reasoning and outputs from your AI agents.
@igor_kuznietsov Hey Igor, Kanwas is updating its memory accordingly and keeping the log decision. Also on the side we are preparing the gardener flow which will support you with old, left artifacts, by resurfacing them and cleaning by date and relevance.
@igor_kuznietsov Long time no see man! Actually it looks tight and clean cause the brain self evolves and project are easily cleaned up by agents!