Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customize chat template #106

Open
helins opened this issue Feb 15, 2024 · 0 comments
Open

Customize chat template #106

helins opened this issue Feb 15, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@helins
Copy link

helins commented Feb 15, 2024

A simple but potentially killer feature would be to allow customizing the chat template. For instance, that would allow interfacing more directly with markdown-based note taking app such as Obsidian and Logseq. Users could prepare the header of the chat file with things like tags. I think having chats in an app like Obsidian would be terrific.

It seems like it would require only simple changes:

  • Replace chat_template with a function. The default one would keep the current behavior.
  • is_chat seems overly cautious. Why must the file contain - file: ...? Or even a title? Being in the chat dir is the most important factor. For instance, it would suffice that the plugin splits on the first --- in any MD file in the chat dir, assuming what is before is a header to discard and what is after is the chat history to use. Or perhaps I am not considering something :)
@Robitx Robitx added the enhancement New feature or request label Aug 4, 2024
Robitx added a commit that referenced this issue Aug 17, 2024
- file and topic headers not mandatory
- current conditions: .md, chat dir, header section break
Robitx added a commit that referenced this issue Sep 19, 2024
- file and topic headers not mandatory
- current conditions: .md, chat dir, header section break
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants