Summary
I’d like to propose a small UX improvement for the Obsidian plugin:
- Add a context menu action like
Send to Claudian when text is selected in the editor
- Add a context menu action like
Add to Claudian chat when right-clicking a file in the file explorer
Both actions would only append content into the Claudian input box and would not auto-send.
Motivation
This makes it easier to add editor selections or files into the chat context without manual copy/paste, similar to “Add to Chat” interactions in other editor tools.
Current status
I have already implemented a local prototype and tested the basic workflow in Obsidian.
The current behavior in my local implementation is:
-
For editor selections:
- Show the menu item only when there is a non-empty selection
- Open the Claudian panel automatically if needed
- Append the selected content into the input box using the existing XML-style context format
- Do not auto-send
-
For files:
- Show the menu item only for text-like files
- Append the file path into the input box using the existing context format
- Do not auto-send
Notes
I tried to keep the implementation aligned with the current context/tag flow and avoid changing existing interactions such as commands, shortcuts, or inline edit behavior.
If this direction looks good, I can open a PR and refine the implementation based on feedback.
Summary
I’d like to propose a small UX improvement for the Obsidian plugin:
Send to Claudianwhen text is selected in the editorAdd to Claudian chatwhen right-clicking a file in the file explorerBoth actions would only append content into the Claudian input box and would not auto-send.
Motivation
This makes it easier to add editor selections or files into the chat context without manual copy/paste, similar to “Add to Chat” interactions in other editor tools.
Current status
I have already implemented a local prototype and tested the basic workflow in Obsidian.
The current behavior in my local implementation is:
For editor selections:
For files:
Notes
I tried to keep the implementation aligned with the current context/tag flow and avoid changing existing interactions such as commands, shortcuts, or inline edit behavior.
If this direction looks good, I can open a PR and refine the implementation based on feedback.