Environment ambiguity
Python, packages, virtualization, local paths, ports, server processes, and GNS3 versions can fail independently.
FLAGSHIP PRODUCT / 001
A technical operator for GNS3 labs.
GNS3 Agent is being built to diagnose environments, inspect real GNS3 state, execute bounded workflows, capture evidence, and explain what happened.
STATUS Active development
CURRENT PHASEDiagnostics + real REST connectivity
PRIMARY ENVIRONMENTWindows · GNS3 2.x
OPERATING PRINCIPLERead first. Act with boundaries.
01 / Problem
Network labs fail in the gaps
between tools, instructions, and evidence.
Execution overhead
Students and engineers repeatedly translate lab documents into device, topology, validation, and troubleshooting steps.
Evidence fragmentation
Commands, screenshots, state checks, and written reports are produced separately, often without a reliable audit trail.
02 / Current capabilities
What the agent can inspect today.
The current phase emphasizes truthful diagnostics and read-only visibility before expanding execution authority.
Environment doctor
Python runtime, required packages, Windows paths, GNS3 installation, processes, and virtualization checks.
REST connectivity
Typed direct connection to the GNS3 REST API with structured success and error results.
Server inspection
Server information, projects, templates, configuration, and diagnostic summaries.
Report artifacts
JSON and Markdown reports for diagnostics and read-only inspection output.
Topology execution
Bounded creation and configuration workflows with checkpoints and rollback awareness.
Evidence automation
Scope-aware screenshots, command evidence, validation output, and submission-ready reporting.
03 / Operating model
A visible execution loop.
Understand
Parse the environment, request, lab instructions, constraints, and required evidence.
Plan
Produce a device and command plan with validation checkpoints before modifying state.
Execute
Call approved tools and GNS3 endpoints through bounded, observable operations.
Verify
Check device state, connectivity, expected outputs, and failure conditions.
Recover
Stop, explain, retry safely, or return control when confidence or policy is insufficient.
Document
Package commands, results, screenshots, and explanations into traceable artifacts.
04 / Architecture
Local-first by default. Extensible by design.
Interface layer
CLI today; desktop and guided workflow interfaces later.
Orchestration layer
Task planning, typed results, policy checks, checkpoints, and execution state.
GNS3 adapter
Direct typed REST client for server, project, template, node, and link operations.
System diagnostics
Windows process, path, port, package, install, and virtualization inspection.
Evidence layer
Structured logs, JSON/Markdown artifacts, screenshots, and report generation.
Model layer
Optional reasoning assistance with local or cloud models based on task sensitivity.
05 / Initial audience
Built first for the people closest to the pain.
Students
Understand lab failures, execute repeatable workflows, and create better evidence without hiding the learning process.
Educators
Standardize lab setup, inspect environments, and reduce time spent debugging unrelated workstation problems.
Technical teams
Automate controlled GNS3 test environments, reusable topology tasks, and infrastructure validation.
EARLY ACCESS
Join the early conversation ↗Help shape the first useful release.
Share your GNS3 environment, recurring lab pain, or automation use case.