Silk

•⁠  ⁠intros
•⁠  ⁠⁠sameen pitch
•⁠  ⁠⁠how do you use AI? daily wf
•⁠  ⁠⁠what do you want from AI?
•⁠  ⁠⁠this is what weaver does
•⁠  ⁠⁠quick product vision. no one else has this vision
•⁠  ⁠⁠what we’ve been working on. burning bugs, rebrand, plugins, cool features lined up
•⁠  ⁠⁠ritesh ad-libs

- core ai platform
- tom: represent all workflows that people and humans do
- gav: what tom just said. too many years in the industry
- how to replace the PDLC, what does that look like?

onboard/ingest?
vms?
rbac?

I was hoping we could spend a few minutes introducing
hey I'm sakib, this is ritesh, ritesh do you wanna introduce yourselves
my background is in large scale systems at fb, I was a PE working on traffic infrastructure
that's when I was in San Francisco - moved onto MongoDB at some point and worked on building and scaling an enterprise kube platform that supported the entire atlas product
we both use a lot of agents all the time. we both have an issue with multiplayer AI
we know it's a bit of a crowded space, but we're both a little frustrated that none of the products out there have the complete user experience that we were looking for
Ritesh and I met through some projects we were working on
since then we've been dev'ing weaver (formerly pix) for about 6 months
we've been spinning wheels on the rebrand recently
then we realized YC actually put out a request for startups to solve multiplayer AI!
so that's how we got into this.
I've personally seen such a massive amount of variance in how my peers make use of AI
y'know, some people still don't use AI at all, most people use AI to varying effect.
and very few people make effective use of AI. very few have established the rigorous setup needed to 10x themselves.
we don't think it has to be like that. we're pretty focused on the details
we want to build the BEST ai workflows possible and make those available to everyone, community and enterprise

tom: local claude, design something, dump artifact into platform, platform gets the job done
what I picture is mirro or stitch where I can work with a bunch of people on my team to collaboratively build the artifact that can then be fed into the development platform
gav: 200 jobs to be done by the business - "I want a calendar that can make things better"
we want a platform to shape the intake of intent into the PDLC
so imagine a hub that leads you, your fellow engineer, and your fellow PM into a shared view of 4-5 agents side by side. these agents can talk bidirectionally to each other. everyone can collaborate with RBAC, the PM can maybe propose changes to prompts to different agents, an engineer is the driver for one or more of the sessions, the sessions carefully manage context. shared artifacts
tom: the piece missing from this is the artifact management. I wanna be able to use my local claude. it's very text based.
tom: if we've knocked out 20 odd tickets. new joiners can pull on the context of the conversation so far
dont care what everyone is using but i wanna make sure
tom: when you're working it comes down to, I've got my local thing, that's also this remote deployed thing too, but with local coding harnesses. I need my own local thing, I like my agent hearing it in math notation, no one else does
gav: I've spent my career translating excel to tech.
sameen mentioned
gav: models will get cheaper and cheaper. I've got


recently we put up new branding and a new landing page - you can see that at https://silkstack.ai/
here's what we have lined up: we'd love to get your thoughts
(share major items on the product roadmap items -> talk about high-level specifics)
- multiplayer
- p2p
- PM and engineer work on the same IDE together (agentic XP)