Replies: 2 comments
-
Yeah, the workaround works: require('mcphub').setup {
auto_approve = function(params)
if vim.g.codecompanion_auto_tool_mode then
return true -- Auto approve when CodeCompanion auto-tool mode is on.
end
if not params.is_auto_approved_in_server then
vim.api.nvim_exec_autocmds('User', { pattern = 'MCPHubConfirmationNeeded' })
end
return params.is_auto_approved_in_server -- Respect servers.json configuration.
end,
} |
Beta Was this translation helpful? Give feedback.
0 replies
-
@powerman Thanks for the suggestion! 🎉 This has been implemented in commit 2218737. MCPHub now fires You can now set up sound notifications like: vim.api.nvim_create_autocmd("User", {
pattern = "MCPHubApprovalWindowOpened",
callback = function()
vim.fn.system("paplay /path/to/notification.wav &")
end,
}) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It's useful to have sound notifications when LLM waits for an input or sent a final answer. Second part is already possible with events sent by CodeComplete, but MCPHub confirmation window is currently shown without firing any user events which can be used to setup sound notifier. I suppose it's possible to work around this by using auto-approve callback, but didn't tried this yet, and, anyway, it'll be nice to have this feature without misusing auto-approve feature.
Beta Was this translation helpful? Give feedback.
All reactions