Start here
Build your first NetConverter workflow
Choose a connection, run a supported task, and understand the evidence before making a network change.
Choose how you work
| Your task | Start here | What you need |
|---|---|---|
| Work directly with files in a terminal | Install the CLI | An enabled account and a supported job type. |
| Let an assistant submit a local file | Local MCP bridge | The CLI, an assistant that runs local MCP servers, and MCP access. |
| Ask about existing jobs from a web assistant | Hosted connection | Your NetConverter sign-in and administrator-enabled MCP access. |
| Collect and prepare on your network | NetConverter Local preview | The separate on-site workspace; check its preview availability. |
A first result you can inspect
Follow the first-validation guide: sign in, check your capabilities, submit the synthetic example and inspect the verdict and findings. Start with the report when asking an assistant for an explanation.
Read the evidence in context
A completed job is not a change approval. Check the warnings, the features covered and any missing evidence. Deterministic checks govern status; an AI explanation does not clear a blocking finding. Engineers own target testing and deployment.
Know what is available
Support depends on the account, job type, platform and release. Read compatibility and verification before treating a documented command as a tested end-to-end workflow. The current terminal guides describe CLI 0.5.0; older pilot keys keep a narrower scope.
Source and release context: CLI overview · Verification evidence