feat: local changes

[ADITYA-tp01]

User description

Webhook fix, stop dashboard, agent model update

---

CodeAnt-AI Description

Fix local webhook delivery, stop the dashboard cleanly, and update the agent model

What Changed

• Chaos actions now send webhook notifications to the local dashboard service reliably
• The stop script also shuts down the dashboard process instead of leaving it running
• The MissionControl agent now uses the Llama 3.3 70B Instruct model

Impact

✅ Reliable local alert handling
✅ Cleaner dashboard shutdowns
✅ Updated agent responses

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	a6d12f7	Aug 30, 2026 · 14:37	14:39

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[qodo-code-review]

PR Summary by Qodo

Fix local webhook routing and refresh agent operations

🐞 Bug fix ✨ Enhancement ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Routes automatic incident triggers to the dashboard webhook on its fixed local port.
• Stops dashboard Node processes alongside Docker services during one-click shutdown.
• Migrates the missioncontrol agent manifest to Llama 3.3 70B.

Diagram

graph TD
  Stop["Stop script"] -->|"terminates"| Dash["Dashboard process"] -->|"hosts"| Action["Action API"] -->|"posts incident"| Webhook["Webhook API"] -->|"creates session"| Forge["TrueForge"] -->|"loads model"| Agent[("Agent record")]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Configurable webhook endpoint

• ➕ Supports non-local deployments and alternate dashboard ports
• ➕ Avoids embedding environment topology in application code
• ➖ Requires an additional environment variable and documented default

2. Process-scoped dashboard shutdown

• ➕ Avoids terminating unrelated Node applications
• ➕ Can reuse the repository's existing port and command-line filtering strategy
• ➖ Adds more PowerShell process-discovery logic

Recommendation: Keep localhost:3001 as the local default, but allow an environment override for the webhook URL. Prefer PID-, port-, or command-line-scoped dashboard termination over stopping every Node process, especially since scripts/stop-all.ps1 already demonstrates targeted shutdown.

Files changed (3) +6 / -1

Enhancement (1) +4 / -0

stop.ps1Stop the dashboard during one-click shutdown +4/-0

Stop the dashboard during one-click shutdown

• Extends the root shutdown script to force-stop Node processes after Docker Compose services are stopped. Adds explicit console output for the dashboard shutdown step.

stop.ps1

Bug fix (1) +1 / -1

route.tsRoute agent triggers to the local dashboard webhook +1/-1

Route agent triggers to the local dashboard webhook

• Changes automatic chaos-incident triggers from the incoming request origin to the dashboard webhook at 127.0.0.1:3001. This ensures server-side triggers reach the locally hosted webhook endpoint.

apps/dashboard/app/api/infra/action/route.ts

Other (1) +1 / -0

update.sqlSwitch the missioncontrol agent model +1/-0

Switch the missioncontrol agent model

• Adds a targeted SQLite JSON update that sets the missioncontrol agent manifest model to meta/llama-3.3-70b-instruct while preserving the manifest's BLOB storage type.

update.sql

[github-actions]

Failed to generate code suggestions for PR

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Kills unrelated Node processes 🐞 Bug ☼ Reliability

Description

The new shutdown command force-terminates every Windows process named node, not just
MissionControl's dashboard. Running stop.ps1 can therefore abruptly kill unrelated development
servers, editors, and other Node applications, causing interrupted work or data loss.

Code

stop.ps1[6]

+Stop-Process -Name "node" -Force -ErrorAction SilentlyContinue

Relevance

●●● Strong

Recent PR #5 accepted the same risk and required targeted process identification instead of killing
all Node processes.

PR-#5

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

MissionControl launches the dashboard through npm run dev in its dashboard directory, but Node's
process name does not identify that specific application. The existing comprehensive stop script
explicitly avoids this hazard by finding the port owner and verifying MissionControl command-line
patterns before killing it; accepted PR #5 documents the same unrelated-process termination risk.

start.ps1[48-57]
apps/dashboard/package.json[5-9]
scripts/stop-all.ps1[8-35]
PR-#5

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`Stop-Process -Name "node" -Force` kills every Windows Node process rather than only the MissionControl dashboard.

## Issue Context
The dashboard runs on port 3001, and the repository already has targeted process-identification logic in `scripts/stop-all.ps1` that verifies the owning process command line before terminating it.

## Fix Focus Areas
- stop.ps1[5-6]
- scripts/stop-all.ps1[8-35]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context sources

Review mode: ⚖️ Balanced: This changes runtime webhook routing, a process-stop script, and a database update, creating multiple behavioral and operational risks that warrant a careful single-pass review.

Tip of the day

💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

1. Kills unrelated node processes 🐞 Bug ☼ Reliability

The new shutdown command force-terminates every Windows process named node, not just
MissionControl's dashboard. Running stop.ps1 can therefore abruptly kill unrelated development
servers, editors, and other Node applications, causing interrupted work or data loss.

Agent Prompt

## Issue description
`Stop-Process -Name "node" -Force` kills every Windows Node process rather than only the MissionControl dashboard.

## Issue Context
The dashboard runs on port 3001, and the repository already has targeted process-identification logic in `scripts/stop-all.ps1` that verifies the owning process command line before terminating it.

## Fix Focus Areas
- stop.ps1[5-6]
- scripts/stop-all.ps1[8-35]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[codeant-ai]

Suggestion: Stop-Process -Name "node" forcibly terminates every Node process, including unrelated development servers and applications running on the machine. [logic error]

Assessment: 🟠 Major · 🔁 Occurrence: Sometimes

Prompt for AI Agent 🤖

This is a comment left during a code review.

**Path:** stop.ps1
**Line:** 6:6
**Comment:**
	*Logic Error: `Stop-Process -Name "node"` forcibly terminates every Node process, including unrelated development servers and applications running on the machine.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

👍 | 👎