Skip to content

Commit 63e7009

Browse files
committed
refactor!: default_prompts removed
1 parent eab01fa commit 63e7009

File tree

2 files changed

+3
-14
lines changed

2 files changed

+3
-14
lines changed

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -147,8 +147,8 @@ _Slash commands_, accessed via `/`, run commands to insert additional context in
147147

148148
_Tools_, accessed via `@`, allow the LLM to function as an agent and carry out actions:
149149

150-
- `@buffer_editor` - The LLM will edit code in a Neovim buffer by searching and replacing blocks
151150
- `@code_runner` - The LLM will run code for you in a Docker container
151+
- `@editor` - The LLM will edit code in a Neovim buffer
152152
- `@rag` - The LLM will browse and search the internet for real-time information to supplement its response
153153

154154
> [!TIP]
@@ -1167,7 +1167,7 @@ By default, an inline assistant prompt will trigger the diff feature, showing di
11671167

11681168
As outlined by Andrew Ng in [Agentic Design Patterns Part 3, Tool Use](https://www.deeplearning.ai/the-batch/agentic-design-patterns-part-3-tool-use), LLMs can act as agents by leveraging external tools. Andrew notes some common examples such as web searching or code execution that have obvious benefits when using LLMs.
11691169

1170-
In the plugin, agents are simply context that's given to an LLM via a `system` prompt. This gives it knowledge and a defined schema which it can include in its response for the plugin to parse, execute and feedback on. Agents can be added as a participant in a chat buffer by using the `@` key.
1170+
In the plugin, agents are simply context that's given to an LLM via a `system` prompt. This gives it knowledge and a defined schema which it can include in its response for the plugin to parse, execute and feedback on. Agents can be added as a participant to the chat buffer by using the `@` key.
11711171

11721172
More information on how agents work and how you can create your own can be found in the [AGENTS](doc/AGENTS.md) guide.
11731173

@@ -1202,6 +1202,7 @@ The plugin sets the following highlight groups during setup:
12021202

12031203
The plugin fires many events during its lifecycle:
12041204

1205+
- `CodeCompanionToolAdded` - Fired when a tool has been added to a chat buffer
12051206
- `CodeCompanionChatClosed` - Fired after a chat has been closed
12061207
- `CodeCompanionChatAdapter` - Fired after the adapter has been set in the chat
12071208
- `CodeCompanionAgentStarted` - Fired when an agent has started using a tool

lua/codecompanion/init.lua

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -239,18 +239,6 @@ end
239239
---@param opts nil|table
240240
---@return nil
241241
M.setup = function(opts)
242-
if opts and opts.default_prompts then
243-
dep.write(
244-
"The ",
245-
{ "`default_prompts`", "WarningMsg" },
246-
" have been renamed to ",
247-
{ "`pre_defined_prompts`", "WarningMsg" },
248-
"\nThey will be removed in the coming weeks."
249-
)
250-
opts.pre_defined_prompts = opts.default_prompts
251-
opts.opts.use_default_pre_defined_prompts = opts.opts.use_default_prompts
252-
end
253-
254242
M.config = vim.tbl_deep_extend("force", M.config, opts or {})
255243

256244
if opts and opts.adapters then

0 commit comments

Comments
 (0)