Custom assistant prompt (i.e. agent prefix/suffix)

[frankroeder]

Another useful feature is being able to customise assitant prompt (i.e. agent prefix/suffix) in the responses for custom commands (for example my 'proofreader' command could have a different emoji like 👓 instead of 🦜).

Originally posted by @eterps in #23 (comment)

[frankroeder]

@eterps could you share your "proofreader" with me?

[eterps]

Sure:

      hooks = {
        --PrtProofReader
        ProofReader = function(prt, params)
          local chat_system_prompt = [[
I want you to act as a proofreader. I will provide you with texts and
I would like you to review them for any spelling, grammar, or
punctuation errors. Once you have finished reviewing the text,
provide me with any necessary corrections or suggestions to improve the
text. Highlight the corrected fragments (if any) using markdown backticks.

When you have done that subsequently provide me with a slightly better
version of the text, but keep close to the original text.

Finally provide me with an ideal version of the text.

Whenever I provide you with text, you reply in this format directly:

## Corrected text:

{corrected text, or say "NO_CORRECTIONS_NEEDED" instead if there are no corrections made}

## Slightly better text

{slightly better text}

## Ideal text

{ideal text}
]]
          local agent = prt.get_chat_agent()
          agent.model.system = chat_system_prompt
          prt.cmd.ChatNew(params, agent.model, '')
        end,
      }

[frankroeder]

I am not sure if this worked at all. In the current version I changed the arguments for ChatNew, thus the new_chat function. Previously, agent.model and system_prompt were used solely for visualization purposes at the beginning of the chat file. Could you confirm that your chat_system_promptgoes through and let me know which commit you’re currently using, or at the very least, the commit where this function worked correctly?

[eterps]

I am not sure if this worked at all.

It definitely works, the markdown response of this prompt is quite elaborate. I use it with Anthropic's Claude 3.5 model.
I'm on 8fa80bb. I don't have the time to do any checks myself for now, maybe later this week.
Thanks for looking into it.

[frankroeder]

There is no hurry, it works for anthropic, but not for other providers. agent.model.system = chat_system_prompt really changes the reference for that API call. On the other hand, agent.system_prompt = chat_system_prompt does not work for other providers.

[eterps]

I found some additional information while trying to understand what's happening.
In my code fragment above I have this function call:

prt.cmd.ChatNew(params, agent.model, '')

However, that doesn't make sense because the prt.cmd.ChatNew function only accepts a single argument, not 3.
In the other words, the passing of agent.model and '' is ignored.
Which is true because if I change that call to prt.cmd.ChatNew(params) the proofreader continues to work fine (when used with Anthropic).

That means that agent.model.system = chat_system_prompt overrides the system prompt globally. Which causes this bug: #28

However, I also see you're working on: #29

[frankroeder]

Sure:

      hooks = {
        --PrtProofReader
        ProofReader = function(prt, params)
          local chat_system_prompt = [[
I want you to act as a proofreader. I will provide you with texts and
I would like you to review them for any spelling, grammar, or
punctuation errors. Once you have finished reviewing the text,
provide me with any necessary corrections or suggestions to improve the
text. Highlight the corrected fragments (if any) using markdown backticks.

When you have done that subsequently provide me with a slightly better
version of the text, but keep close to the original text.

Finally provide me with an ideal version of the text.

Whenever I provide you with text, you reply in this format directly:

## Corrected text:

{corrected text, or say "NO_CORRECTIONS_NEEDED" instead if there are no corrections made}

## Slightly better text

{slightly better text}

## Ideal text

{ideal text}
]]
          local agent = prt.get_chat_agent()
          agent.model.system = chat_system_prompt
          prt.cmd.ChatNew(params, agent.model, '')
        end,
      }

Dear @eterps, I have added a lightweight chat template support. In the latest release, you can now provide custom prompt text that is part of the first message.

       ProofReader = function(prt, params)
      local chat_prompt = [[
		I want you to act as a proofreader. I will provide you with texts and
		I would like you to review them for any spelling, grammar, or
		punctuation errors. Once you have finished reviewing the text,
		provide me with any necessary corrections or suggestions to improve the
		text. Highlight the corrected fragments (if any) using markdown backticks.

		When you have done that subsequently provide me with a slightly better
		version of the text, but keep close to the original text.

		Finally provide me with an ideal version of the text.

		Whenever I provide you with text, you reply in this format directly:

		## Corrected text:

		{corrected text, or say "NO_CORRECTIONS_NEEDED" instead if there are no corrections made}

		## Slightly better text

		{slightly better text}

		## Ideal text

		{ideal text}
		]]
      prt.cmd.ChatNew(params, chat_prompt)
    end

[eterps]

Ah, thanks! It makes sense that way. I'll give it a try 👍

[eterps]

@frankroeder it works great, however I can imagine it might be confusing UX to some users.
This is what I see when I invoke ProofReader:

On line 5 in this screenshot is the chat_user_prefix and at line 29 is the nvim cursor where I can type (or paste) my text.

Making it part of the first message is a powerful feature, but it feels quite different than having it as a system prompt for that particular chat.

But like I said, it works for me, so thank you 👍

[eterps]

Now that I think of it, I can probably improve my prompt as well so that it reads less like a system prompt and has a clear separator for the text I'm pasting in.

[frankroeder]

@eterps, I also considered this and decided to go with the message because the system prompt is not visible to the user. However, it is quite simple to make it the system prompt. The question is whether it should be appended to the existing general system prompt or replace it entirely.

[eterps]

I believe replacing the prompt entirely would be preferable, as automatic merging could potentially be frustrating for users. If needed, users can always incorporate the general system prompt, which they would likely customize to suit their specific requirements for the hook in question.

[frankroeder]

@eterps, you are right. I will change this very soon.

[frankroeder]

@eterps Despite everything being cramped into a single row, this is how it looks when provided as a system prompt, using the former structure of gp.nvim.

[eterps]

@frankroeder looks quite clear to me. Another possibility would be to use vim folds around the system prompt so the user can expand it on demand.

[frankroeder]

Oh, that is just my setup. You can simply call :set wrap and you will be fine. vim.fold wouldn't change too much as it is a single line.

[GerardGarcia]

similarly, it would be nice to be able configure the agent_prefix similarly to the chat_user_prefix option, not everyone have terminals that support bitmap emojis and in these cases nothing renders or you only see a square instead of the parrot.

[frankroeder]

@GerardGarcia Sure, I added the agent prefix with commit 2b29eb3 on the main branch. It will be part of the next release today.