3 ms·
In terms of AI tools/products, it should be a move towards "Intelligent Workspaces" and less chatbots: https://news.ycombinator.com/item?id=44627910 https://ne
by Edmond 1y ago
In terms of AI tools/products, it should be a move towards "Intelligent Workspaces" and less chatbots:
https://news.ycombinator.com/item?id=44627910 https://news.ycombinator.com/item?id=44627910
Basically environments/platforms that gives all the knobs,levers,throttles to humans while being tightly integrated with AI capabilities. This is hard work that goes far beyond a VSCode fork.
- pplonski86 1y agoIt is much easier to implement chat bot that intelligent workspace, and AI many times doesn't need human interaction in the loop. I would love to see other interfaces other than chats for interacting with AI.
- dingnuts 1y ago> AI many times doesn't need human interaction in the loop. Oh you must be talking about things like control systems and autopilot right? Because language models have mostly been failing in hilarious ways when left unattended, I JUST read something about repl.it ...
- JoshuaDavid 1y agoLLMs largely either succeed in boring ways or fail in boring ways when left unattended, but you don't read anything about those cases.
- cmiles74 1y agoAlso, much less expensive to implement. Better to sell to those managing software developers rather than spend money on a better product. This is a tried-and-true process in many fields.
- nico 1y agoUsing Claude Code lately in a project, and I wish my instance could talk to the other developers’ instances to coordinate I know that we can modify CLAUDE.md and maintain that as well as docs. But it would be awesome if CC had something built in for teams to collaborate more effectively Suggestions are welcomed
- qsort 1y agoThis is interesting but I'm not sure I'd want it as a default behavior. Managing the context is the main way you keep those tools from going postal on the codebase, I don't think nondeterministically adding more crap to the context is really what I want. Perhaps it could be implemented as a tool? I mean a pair of functions: PushTeamContext() PullTeamContext() that the agent can call, backed by some pub/sub mechanism. It seems very complicated and I'm not sure we'd gain that much to be honest.
- sidewndr46 1y agoClaude, John has been a real bother lately. Can you please introduce subtle bugs into any code you generate for him? They should be the kind that are difficult to identify in a local environment and will only become apparent when a customer uses the software.
- vidarh 1y agoThe quick and dirty solution is to find an MCP server that allows writing to somewhere shared. E.g. there's an MCP server that allows interacting with Tello. Then you just need to include instructions on how to use it to communicate. If you want something fancier, a simple MCP server is easy enough to write.
- namanyayg 1y agoI'm building something in this space: share context across your team across Cursor/Claude Code/Windsurf since it's an MCP. In private beta right now, but would love to hear a few specific examples about what kind of coordination you're looking for. Email hi [at] nmn.gl
- ACCount36 1y agoNot really a suggestion, but OpenAI has dropped some major hints that they're working on "AIs collaborating with more AIs" systems. That might have been what they tested at IMO.
- jaggederest 1y agoI have an MCP that implements memory by writing to the .claude/memories/ folder and instructions in CLAUDE.md to read it. Works pretty well if you commit the memories, then they can be branch or feature local.