Hey Harsh, cool stuff! Can you elaborate on what's the difference than me just passing in my repo's context to cursor? Is it aggregating all of my team's KBs such as Slack, Notion, etc?
that's exactly the goal - aggregating context from slack, notion, and other services. but for now, it works a bit differently than just passing your repo context to cursor.
right now, multiple team members can access the shared memory that your AI agents are generating. so when your colleague has a conversation with claude code about some architecture decision, you can pick up right where they left off when you switch to cursor or windsurf.
the context persists across different AI tools through MCP servers, rather than everyone starting fresh each time. think of it as a shared brain for your team's AI development tools.
Comments
Hey Harsh, cool stuff! Can you elaborate on what's the difference than me just passing in my repo's context to cursor? Is it aggregating all of my team's KBs such as Slack, Notion, etc?
that's exactly the goal - aggregating context from slack, notion, and other services. but for now, it works a bit differently than just passing your repo context to cursor. right now, multiple team members can access the shared memory that your AI agents are generating. so when your colleague has a conversation with claude code about some architecture decision, you can pick up right where they left off when you switch to cursor or windsurf. the context persists across different AI tools through MCP servers, rather than everyone starting fresh each time. think of it as a shared brain for your team's AI development tools.
ahh okay! happy to chat more in this and and help you w feedback if you'd want