Skip to content

[docs] Update landing readme.md - #1437

Merged
Anis Mohammed Khaja Mohideen (kanismohammed) merged 8 commits into
mainfrom
jsidewhite/docs_3_rewrite
Oct 7, 2026
Merged

Anis Mohammed Khaja Mohideen (kanismohammed) merged 8 commits into
mainfrom
jsidewhite/docs_3_rewrite

Conversation

@jsidewhite

@jsidewhite Jeff Whiteside (jsidewhite) commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

[docs] Update landing readme.md

Microsoft Reviewers: Open in CodeFlow

Copilot AI balanced review requested due to automatic review settings October 7, 2026 04:42
@jsidewhite
Jeff Whiteside (jsidewhite) requested a review from a team as a code owner October 7, 2026 04:42
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Streaming correctness, platform requirements, and broken documentation anchors need correction.

Review effort: Balanced
Findings: 2 Medium severity · 5 Low severity

Open (7)
What changed in this PR

Refreshes the consumer landing page and reorganizes contributor guidance.

Changes:

  • Reworks the landing README around SDK consumption and platform support.
  • Adds a local-development guide.
  • Updates the Node streaming sample to demonstrate event callbacks.
File Description
README.md Reorganizes consumer documentation and examples.
docs/​development/​README.md Links new development resources.
docs/​development/​build-and-test/​local-development.md Adds local build and validation commands.
samples/​run-with-io-stdio-streaming/​README.md Documents Node stream callbacks.
samples/​run-with-io-stdio-streaming/​node/​src/​main.ts Uses event-driven output forwarding.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread README.md Outdated
);
}
return new Promise<void>((resolve, reject) => {
stream.on('data', (chunk) => destination.write(chunk));
Comment thread README.md
the resulting container.

For which filesystem, network, and UI-restriction policy aspects the Windows `processcontainer` backend can enforce on each Windows 11 release (23H2 / 24H2 / 25H2 / 25H2+), see [Windows OS-version policy support](./docs/backends/process-container/os-version-support.md).
### What container types are supported?
Comment thread README.md Outdated
Comment on lines +57 to +58
| Windows 11 x64 / ARM64 | `processcontainer` | `windows_sandbox`, `wslc`, `microvm`, `hyperlight`, `isolation_session` | `processcontainer`: 26100 (24H2)<br>`isolation_session`: 26340.9212 ([Insider Preview](https://learn.microsoft.com/en-us/windows-insider/release-notes/experimental/preview-build-26340-9212)) |
| Linux x64 / ARM64 | `bubblewrap` | `lxc`, `microvm`, `hyperlight` | - |
Comment thread README.md
|---|---|---|---|
| Windows 11 x64 / ARM64 | `processcontainer` | `windows_sandbox`, `wslc`, `microvm`, `hyperlight`, `isolation_session` | `processcontainer`: 26100 (24H2)<br>`isolation_session`: 26340.9212 ([Insider Preview](https://learn.microsoft.com/en-us/windows-insider/release-notes/experimental/preview-build-26340-9212)) |
| Linux x64 / ARM64 | `bubblewrap` | `lxc`, `microvm`, `hyperlight` | - |
| macOS ARM64 / x64 | `seatbelt` | - | - |
Comment thread README.md
developer reference.

### Request-aware ProcessContainer probe
### Audit mode
Comment thread docs/development/build-and-test/local-development.md Outdated
Comment thread README.md Outdated

MXC is a **sandboxed code execution system** for running untrusted code (model output, plugins, tools) on Windows, Linux, and macOS. It provides multiple containment backends — from OS-native process sandboxes to full VMs — behind a unified JSON configuration schema and TypeScript SDK.
MXC is a **sandboxed code execution system** for running untrusted code
(agentic actions, plugins, and tools) on Windows, Linux, and macOS. It provides

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agentic actions

leave it as model output

Comment on lines +1 to +33
# Local development

> **Audience:** MXC developers

Use the repository build scripts for complete platform builds. The commands
below target individual components or validation steps during development.
Run Rust commands from `src/`.

## Component builds

```text
# Windows x64
cargo build --release --target x86_64-pc-windows-msvc

# Windows ARM64
cargo build --release --target aarch64-pc-windows-msvc

# Linux executor for the LXC and Bubblewrap backends
cargo build --release -p lxc

# macOS executor
cargo build --release -p mxc_darwin --target aarch64-apple-darwin
```

Build the Node SDK from `sdk/node/`:

```text
npm install
npm run build
```

## Format and lint

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: for this file, we probably should just tell the developers to run the build.bat on windows, build.sh on linux and build-mac.sh on macOS. The .bat should build the crates, nuget package and npm package.

Comment thread README.md Outdated
Comment on lines +36 to +37
SDK --> Engine["MXC engine<br/>(in process)"]
Engine --> Backend["Selected backend<br/>(in process)"]

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: probably can just go from SDK -> Backend tbh

Comment thread README.md Outdated
### Requirements
| Runtime platform | Default backend | Other backends | Minimum host OS |
|---|---|---|---|
| Windows 11 x64 / ARM64 | `processcontainer` | `windows_sandbox`, `wslc`, `microvm`, `hyperlight`, `isolation_session` | `processcontainer`: 26100 (24H2)<br>`isolation_session`: 26340.9212 ([Insider Preview](https://learn.microsoft.com/en-us/windows-insider/release-notes/experimental/preview-build-26340-9212)) |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

26340.9212

PRovide the link to the Windows OS Support

Copilot AI balanced review requested due to automatic review settings October 7, 2026 05:23

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Comment on lines +26 to +30
return new Promise<void>((resolve, reject) => {
stream.on('data', (chunk) => destination.write(chunk));
stream.once('end', resolve);
stream.once('error', reject);
});
Comment thread README.md
Telemetry is **off by default**. To keep it off, do not set
`"telemetry": { "enabled": true }` for the run.
#### Windows

Comment thread README.md
Comment on lines +22 to +23
return Promise.reject(
new Error('The selected backend did not provide an expected output stream.'),
Copilot AI balanced review requested due to automatic review settings October 7, 2026 05:50

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Several build instructions are inaccurate, and the Node examples mishandle process ownership or stream backpressure.

Review effort: Balanced
Findings: 1 High severity · 2 Medium severity · 6 Low severity

Open (9)
Resolved since last review (3)
Previously missed (3)

In code that hasn't changed since last review

Low severity Mark Linux microvm and hyperlight as experimental

README.md:55

The footnote only applies to starred entries, but the Linux microvm and hyperlight backends are experimental too (the previous README and their backend guides require experimental authorization). Leaving them unstarred makes the support table present them as non-experimental on Linux.

Low severity Complete MxcProcess lifecycle in landing example

README.md:96

The landing example returns an owning MxcProcess but never calls wait() or dispose(). wait() is also what drains untaken output, so copying this pattern for a noisier command can block on full stdio pipes. For this minimal example, use run() (or show the complete stream/wait/dispose lifecycle).

Low severity Correct Windows Node.js version prerequisite

README.md:161

This prerequisite is too broad on Windows: native stdio rejects Node 24 before 24.21.0 and all Node 25 releases; support resumes at 26.8.0. Retain the platform-specific requirement documented in sdk/node/README.md:15-17.

Comment thread README.md

Official/shipped Microsoft builds set a TraceLogging provider group GUID at build time and route `MXC.Execution`, `MXC.Error`, and `MXC.VerboseDenials` events to Microsoft through the UTC pipeline when telemetry is enabled — that same build-time setting also selects the correct Measures keyword and Product-and-Service-Usage privacy tag for the events, so telemetry routing and event classification always agree. **Local and open-source builds send nothing to Microsoft by default** — the public source ships without a provider group GUID, so events are emitted to the local ETW subsystem only, use a provider-local keyword with no UTC meaning, and carry no privacy classification tag, and are not routed to any Microsoft collection pipeline. Internal builds that set the `MXC_TELEMETRY_PROVIDER_GROUP_GUID` environment variable at build time enable the Microsoft-routed path.
```bash
./build.sh --all # Release build
@kanismohammed
Anis Mohammed Khaja Mohideen (kanismohammed) merged commit c645d02 into main Oct 7, 2026
31 checks passed
@kanismohammed
Anis Mohammed Khaja Mohideen (kanismohammed) deleted the jsidewhite/docs_3_rewrite branch October 7, 2026 05:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants