Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

How can I continue an unfinished message? #142

Closed
Mashiro-Yukino opened this issue Apr 2, 2023 · 7 comments
Closed

How can I continue an unfinished message? #142

Mashiro-Yukino opened this issue Apr 2, 2023 · 7 comments

Comments

@Mashiro-Yukino
Copy link

I find it is hard to continue the unfinished message after breaking if I used my notes, anyway to continue the unfinished message?

@Mashiro-Yukino Mashiro-Yukino changed the title continue continue the unfinished message Apr 2, 2023
@Mara-Li
Copy link
Contributor

Mara-Li commented Apr 2, 2023

I have the same problem, many replies are unfinished :
image

@brianpetro
Copy link
Owner

@Mashiro-Yukino @Lisandra-dev thanks for bringing this to my attention.

When using your notes as context, often we use up all available space for text as context. So, after this completion from the model, the context sourced from the notes is dropped to make room for additional messages. This is why continuing doesn't work after messages that used your notes as context.

There is one relevant improvement coming soon: the ability to change the size of the output. However, it's important to note, since the text size limit is a combination of both the input text and the output text, any increase in output will reduce the amount of context sourced from your notes.

To get around this using prompt engineering, you can try summarizing context from your notes, then making a subsequent query that will use the summary instead of your raw notes as context.

This problem will also be improved as the text-size limits of the underlying AI models continue to increase. GPT-4 does currently offer double the text-size (tokens) limit as GPT-3.5, and it was already announced that GPT-4 will offer eight times the limit in an upcoming release.

Let me know if you have any questions, thoughts or other ideas about how we might address this and make Smart Connections a better assistant.

Brian 🌴

@Mara-Li
Copy link
Contributor

Mara-Li commented Apr 3, 2023

It will be cool to have a text/symbole allow to cut the notes send in the prompt, in this case.

For example %% stop %% or %%---%%

Also I think the plugin can remove the frontmatter from note entry

Mara-Li added a commit to Mara-Li/obsidian-smart-connections that referenced this issue Apr 3, 2023
Mara-Li added a commit to Mara-Li/obsidian-smart-connections that referenced this issue Apr 3, 2023
@brianpetro
Copy link
Owner

@Lisandra-dev interesting. Let me give that some thought and get back to you.

Thanks for the PR,
Brian 🌴

@Mara-Li
Copy link
Contributor

Mara-Li commented Apr 3, 2023

Also I discover that using th word continue allow GPT to continue the unfinished messages!

@Mashiro-Yukino
Copy link
Author

Yes, I tried to use "continue". But subsequent responses won't be based on your notes any more

@brianpetro
Copy link
Owner

Yes, I tried to use "continue". But subsequent responses won't be based on your notes any more

@Mashiro-Yukino yes, this is true.

This is the relevant explanation:

When using your notes as context, often we use up all available space for text as context. So, after this completion from the model, the context sourced from the notes is dropped to make room for additional messages. This is why continuing doesn't work after messages that used your notes as context.

#142 (comment) explains more about the issue, possible workarounds, and upcoming changes that will improve it.

@brianpetro brianpetro changed the title continue the unfinished message How can I continue an unfinished message? Apr 5, 2023
Repository owner locked and limited conversation to collaborators Apr 5, 2023
@brianpetro brianpetro converted this issue into discussion #151 Apr 5, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants