Composer Agents #475
TomLucidor
started this conversation in
Ideas & Feature Requests
Replies: 2 comments 3 replies
-
|
Current PR #427 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Haha! I’m really glad to see similar perspectives and ideas—I’m also very interested in this.😘 In fact, I’m currently developing my own optimized version of Smart Composer, called Next Composer. So far, I’ve completed the following work:
What I’m working on now, and planning for the future, includes:
If you’re also interested, feel free to check out Next Composer. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Obsidian composer can be closer to Cursor Composer (and other IDE agents) by simply being able to plan and use tools
There are ways to get LLMs to use tools (also MCPs are good ways of packaging tools)
The ideal would be to pack Obsidian note edits into tool calling, and allow the adoption of code-related MCPs into non-code domains. This would include "deep research", web crawling, coding tools, lateral thinking, dependency tracing, project orchestration, task management etc.
The flow would be simple:
The concept of "sub-agents" and "background agents" are probably a bit more complex, or just use a tab-based system to make sure multiple agents can be run in parallel, and communicate with shared note-taking.
Related discussions:
Beta Was this translation helpful? Give feedback.
All reactions