Richard/ClawdDotNet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Automatisierungsvorschlaege nur mit n8n-Anbindung (#726)

Browse Source 
An instance without n8n has no use for workflow proposals. New instance
setting automation.enabled ("this instance works with n8n"), off by default:
- off: automation_find/automation_propose refuse, no candidates are put to
  agents, and the escalation tool does not mention proposals at all;
- the switch sits in the settings card for external MCP servers; the
  approvals view says proposals are off instead of standing empty.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Richard
2026-10-01 20:29:19 +02:00
co-authored by Claude Opus 5.5
parent 184a507e3d
commit a17ac2957f
12 changed files with 124 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/ClawdDotNet.App/AppHost.cs
+4 -1
View File
@@ -750,7 +750,10 @@ public sealed class AppHost : IAsyncDisposable
// #726: agents propose workflows; recurring tasks that do the same each time are put to them.
var automations = new Core.Automation.AutomationProposals(storage, audit, taskRepository, board,
loggerFactory.CreateLogger("ClawdDotNet.Core.Automation"));
loggerFactory.CreateLogger("ClawdDotNet.Core.Automation"), () => instance.Automation);
// The escalation tool only mentions proposals to agents of an instance that works with n8n.
if (tools.Get(Core.Cases.CaseDesk.ToolName) is Tools.Taskboard.EscalationTool escalation)
escalation.AutomationEnabled = () => instance.Automation.Enabled;
engine.Automations = automations;
host.Automations = automations;
automations.Start();