ICC 0.1.3 — Windows / PSU 2026.3.3

Connect your AI service to PowerShell Universal with MCP. Ask questions in plain English and use the PowerShell tools you choose to expose. An MCP-capable client connects the AI service to PSU; PSU runs the selected PowerShell on the server and returns the result for the service's reply.

Incident Command Center (ICC) is a working example of that connection. Its ICC_Demo_Incident tool lets you inspect a fictional Acme incident, save an acknowledgment, repeat it safely and prepare a handoff. The dashboard shows the same saved state. Signals are synthetic, and acknowledgment does not repair a service.

You can use a commercial AI service or an application connected to an LLM your organization provides. Either route needs an MCP-capable client that supports PSU's remote HTTP endpoint and app-token authentication, plus a model that can use tools. Familiar documented options include GitHub Copilot in VS Code, Codex and Claude Code. Only Codex has been tested with ICC. Other clients and organization-provided model setups need validation in your environment.

ICC 0.1.3 is a regular release for Windows with PSU and Devolutions.PowerShellUniversal 2026.3.3. It remains a single-server learning example; a regular release does not establish production readiness or compatibility with other environments.

This version binds native Acknowledge, Verify and Handoff buttons to the rehearsal displayed in their tab. Superseded tabs are rejected before acting on another rehearsal. It includes the 0.1.2 timeline-concurrency, missing-acknowledgment recovery and truthful initial-Verify corrections. See change history.

Validation recorded October 15, 2026 UTC on Windows Server 2019, PSU/module 2026.3.3, PowerShell 7.6.6 and Codex CLI 0.162.0-alpha.17.2:

• 338 offline checks, including 71 simulated installer scenarios, plus 47 server recovery/concurrency checks passed.
• Actual native use, safe repetition, saved-state verification, handoff and all three stale-tab rejections passed.
• One signed-in Codex conversation made six native HTTP MCP calls. Returned results, stored Completed PSU jobs and model facts/handoff agreed.
• On a separately refreshed PSU instance, both unchanged packaged installers passed with standard ICC names and an empty code/data path after residual folders were preserved. Native use and one installed-tool Inspect matched the same saved state and Completed job output. No new model session was run in that clean-install phase.

Linux, other PSU releases or clients, custom service identities and multiple nodes remain untested. PowerShell 7.5.4 is the package minimum. The acknowledgment is durable; the service signals are fixed demo data.

Install and use ICC · MCP setup · Updating and recovery · Native workflow screenshot

The AI introduction, repository description and main-branch guides were updated on October 15, 2026 after release. The v0.1.3 tag, downloadable package and dated validation scope are unchanged; the package retains its original reviewed documentation.

Download IncidentCommandCenter-0.1.3.zip below. It has one outer package directory containing the installers beside the module directory, docs and tests. RELEASE-MANIFEST.json identifies the exact source commit and every payload hash; SHA256SUMS.txt covers the payload, ZIP and manifest. Existing installations should follow the updating/recovery guide instead of rerunning the fresh installers. Earlier tags, releases and assets are retained. MIT licensed.

ICC 0.1.2 — Windows / PSU 2026.3.3 community preview

Incident Command Center (ICC) demonstrates PowerShell Universal's Model Context Protocol (MCP) feature through an incident rehearsal at fictional Acme Inc. An external assistant discovers and calls ICC_Demo_Incident; PSU executes the PowerShell and saves the acknowledgment. The native dashboard shows the same state. Signals are synthetic, and acknowledgment does not repair a service.

ICC 0.1.2 is a community preview for Windows with PSU and Devolutions.PowerShellUniversal 2026.3.3. It corrects three issues found in the independent 0.1.1 review:

• Coordinate timeline readers and action writers, and return each action's coherent saved-state snapshot.
• Refuse to recreate a missing acknowledgment when retained actions show one existed; explain backup recovery and partial-save failures.
• Show accurate Verify/Open-read messages before an acknowledgment exists.

Validation of 0.1.2 is offline only, on Windows with PowerShell 7.6.6: core 28 checks, MCP backend 8, installers 216 across 71 scenarios, workflow 17, and state/recovery 47 across seven cases. The live native app, signed-in MCP/model workflow, installation and visual acceptance have not been rerun for 0.1.2. Prior live results and the retained screenshot describe 0.1.1. Other platforms, clients, custom identities and multiple nodes remain untested.

Install and use ICC · MCP setup · Updating and recovery · Change history

Download IncidentCommandCenter-0.1.2.zip below. It has one outer package folder containing the installers, docs, tests and module folder. RELEASE-MANIFEST.json identifies the published source commit and every payload hash; SHA256SUMS.txt covers the payload, ZIP and manifest. Existing installations should follow the recovery/update guide rather than rerun the fresh installer. The 0.1.1 tag, release and assets remain available. MIT licensed.

ICC 0.1.1 — Windows / PSU 2026.3.3 community preview

I’ve built Incident Command Center (ICC) to demonstrate PowerShell Universal’s Model Context Protocol (MCP) feature with a small, working example.

Why does this exist?

ICC shows how a PowerShell workflow can become a tool that an external assistant discovers and calls through PSU’s MCP endpoint. PSU executes the PowerShell and stores the result; the assistant provides the conversation.

The ICC_Demo_Incident tool exposes Inspect, Acknowledge and Handoff. An assistant can read the current rehearsal, save receipt of its warning, verify the stored response and prepare a handoff from those facts. The dashboard makes the same saved state visible, so you can compare tool calls with direct app actions.

At fictional Acme Inc., a checkout latency warning gives the demonstration a simple scenario. The signals are synthetic; the acknowledgment is saved on the server. The native app also works independently of an MCP client.

ICC 0.1.1 is a single-server community preview for Windows with PSU and Devolutions.PowerShellUniversal 2026.3.3. Validation used PowerShell 7.6.6 and Codex CLI. Other platforms and clients remain untested. Acknowledgment records receipt of the warning; it performs no service repair.

Source, installation, MCP setup, recovery guidance and offline tests

MIT licensed. Use the dashboard to learn the rehearsal, then follow the MCP setup guide and try the same workflow through your assistant. Feedback and ideas for adapting the pattern are welcome.

Workflow screenshot

One saved acknowledgment, verified from disk, with a safe repeat and completed handoff.

Download IncidentCommandCenter-0.1.1.zip. The accompanying RELEASE-MANIFEST.json identifies the reviewed source and package; SHA256SUMS.txt supplies the matching checksums.