Inline Assistant v2

[olimorris]

Progress

• System prompt has been revamped - much more structured and logical
• LLMs now return XML:

<response>
  <code>print('Hello World')</code>
  <language>python</language>
  <placement>add</placement>
</response>

This makes it much easier to parse code and errors if they occur:

<response>
  <error>Unable to process the prompt as it appears to be random characters without any clear instruction or meaning.</error>
</response>

• If the LLM returns XML in a markdown code block then we use Tree-sitter to attempt to parse it (something which was common for small parameter LLMs and Gemini 2.0). This will make the Inline Assistant much more resilient, however, this means that streaming is no longer possible
• Improved test coverage
• Adapter tests now test for inline output
• Can now pass in the adapter as the first argument to the prompt
• Prompts can now make use of variables
• Added two new variables: #chat and #buffer

[cloudflare-workers-and-pages]

Deploying codecompanion with    Cloudflare Pages

Latest commit:	68a33c1
Status:	✅  Deploy successful!
Preview URL:	https://c2c19bb0.codecompanion.pages.dev
Branch Preview URL:	https://feat-inline-assistant.codecompanion.pages.dev

View logs

[taketwo]

In one of my custom inline prompts I'm using placement = 'before|false' to place the response in the beginning of the buffer and auto-accept the diff (suggested here). Seems like the auto-acceptance does not work anymore. Is this accidental or was the feature purposefully removed?

[nshen]

After the v2 update, my :CodeCompanion commands have almost stopped working. I've tried Copilot, DeepSeek, and Alibaba's qwen-omni-turbo-latest models.

[olimorris]

@nshen if this is the case, then please raise a support ticket so I can reproduce the issue.

[olimorris]

In one of my custom inline prompts I'm using placement = 'before|false' to place the response in the beginning of the buffer and auto-accept the diff (suggested here). Seems like the auto-acceptance does not work anymore. Is this accidental or was the feature purposefully removed?

The placement|boolean approach was discarded in the plugin many months ago. Apologies if my docs have been slow to reflect that. Also, auto-acceptance has never been a feature so I'm not sure where that came from? Do you mean auto placement? Because that's still very much supported for prompt library items.

[taketwo]

To be clear: I've never seen placement|boolean being documented anywhere. This syntax was suggested by a kind soul in the above-referenced comment.

The placement|boolean approach was discarded in the plugin many months ago.

Yet it worked well until this last release.

Also, auto-acceptance has never been a feature so I'm not sure where that came from?

It was suggested here: #92 (comment).