Repository navigation
v0.5.4 — MCP tuning, plugin networking, directory cleanup
What's new
MCP resource-scoped org hints
Define per-group guidance in Settings → MCP Tuning. Deckwatch appends your hint to tool descriptions only when that resource group is in scope — namespace guidance fires for namespace tools, deployment guidance for deployment tools, etc. No more global instructions polluting unrelated interactions.
Also adds global instructions injected via the MCP initialize response for cross-cutting guidance.
Plugin: inherit_env_keys
Credentials mounted as Kubernetes Secret env vars on the deckwatch pod can now be passed to plugins without storing them in settings. Deckwatch reads the named env vars from the process environment at invocation time and injects them into the plugin's extism config — overriding any same-named static config entry so rotated credentials always win.
{ "inherit_env_keys": ["AWS_ACCESS_KEY_ID", "AWS_SECRET_ACCESS_KEY", "AWS_SESSION_TOKEN"] }MCP prompt improvements
pre-deployment-check: explicitly states no CI pipeline is needed — deckwatch GitOps IS the build pipeline. All 10 checklist items reframed accordingly.deployment-readiness-check: replaced:latesttag check with GitOps build status and OOMKilled detection.
Repository cleanup
- Removed stale
Making an AI app.mdfrom root - Moved 21 handler test files from
src/root intosrc/handlers/alongside their modules (structural cleanup, no behaviour change) - Updated all
#[path]annotations
Documentation
SETTINGS.md:inherit_env_keysandmcp_tuningfully documented with examplesMCP.md: new MCP Tuning sectionPLUGINS.md: full plugin config schema, roadmap updated
Companion repos
- deckwatch-plugin-sdk v0.4.0 —
PluginMetadata,plugin_outputs,outputs - deckwatch-plugin-aws v0.1.0 — unified IAM + RDS + S3 + AWS Backup