Three fabrication modes
The application currently supports three production paths inside one system:
- 3D Print
- CNC
- Laser
G-code generation • 3D Print • CNC • Laser
Build safer G-code workflows for fabrication.
GcoWorks is a fabrication-focused desktop application with an Electron desktop shell, a Web/Vite interface, and a Python backend for generating G-code across 3D print, CNC, and laser workflows. The project is designed to produce not only the final G-code file, but also logs, metrics, summaries, and validation feedback that help users understand what the machine will do before production starts.
GcoWorks explores fabrication workflow validation — combining toolpath generation, machine-safety checks, diagnostics, metrics, logs, and preview logic inside one connected desktop workflow.
Current state: functional prototype / active desktop development / fabrication workflow validation in progress. The strongest areas today are technical G-code safety, 3D print wall/skin/infill output, metrics and summary reporting, preserved CNC and laser modes, and significantly improved performance. The main open weakness remains the 3D print support motor, especially Cura-style ground-up trunk / anchor behavior for difficult overhangs.
Electron desktop appWeb / Vite UIPython G-code backend3 manufacturing modesLogs + metrics + summary
Status: Functional prototype / active desktop development / fabrication workflow validation in progress • 3D print, CNC, and laser workflows are implemented • main open gap: support engine reach / trunk behavior
Prototype walkthrough
GcoWorks workflow demo.
This video presents the current GcoWorks workflow, showing how fabrication modes, model preparation, G-code logic, validation feedback, logs, metrics, and preview behavior work together inside one machine-oriented workflow.
What GcoWorks does
GcoWorks is built for people who need structured toolpaths and traceable fabrication output. It explores fabrication workflow validation by combining mode-based G-code generation, machine-safety checks, diagnostics, metrics, logs, and visual preview in one connected workflow so the user can move from model input to machine output with more control.
Structured output and reporting
Each run is designed to produce more than a toolpath. The current output set includes:
- G-code file
.summary.json.metrics.json.log
Machine safety checks
Safety validation is one of the project’s strongest current areas. The workflow includes control logic for negative Z risk, bounds checking, z-drop risk, G0 extrusion control, and start / end G-code safety sequencing.
Analysis and metrics
The current analysis layer tracks feature usage and manufacturing estimates such as WALL, SKIN, FILL, SUPPORT, SUPPORT-INTERFACE, and SKIRT, together with filament length / weight, estimated time, layer count, motion count, and travel / extrusion path distance.
Visual preview workflow
The project includes a G-code layer viewer and visual preview pipeline so users can inspect layer behavior instead of relying only on raw text output.
Terminal-friendly packaging
The system is designed with terminal-runnable package structures so the workflow can be tested, executed, and validated outside a purely visual environment.
Mode overview
The current implementation is not a concept-only landing page. It reflects the present development state of the application and the mode-specific capabilities already described in the project.
3D Print workspace
Mesh / STL-based slicing workflow with wall generation, top / bottom skin, sparse infill, skirt / brim infrastructure, PLA preset handling, temperature control fields, retraction logic, and support diagnostics. Full geometry-driven adaptive layer behavior remains a development target.
Generated G-code output
Readable output stage for the generated file and related analysis, designed to support verification, debugging, and structured reporting before production.
CNC workflow
CNC G-code generation with pocket / contour logic, heightmap / probe infrastructure, smoke tests, and validation logic that remains isolated from the recent support-engine work.
Strong areas today
The strongest current parts of the project, based on the implementation summary, are the following:
- Technical G-code safety is strong.
- 3D print wall / skin / infill generation is working.
- Start / end safety sequencing is clean.
- Metrics and summary reporting are strong.
- Performance is meaningfully improved.
- CNC and laser modes are preserved in the project.
One measured performance improvement already noted in the project is a reduction on a large model from roughly 3 minutes to around 50 seconds.
Current open weakness
The biggest current gap remains the 3D print support motor. This is the area that still most clearly limits parity with Cura-style support behavior.
Implemented support-side work
- Support on / off generation
- Support interface generation
- Buildplate-only logic
- Ground-start rule added
- Support mask / scanline-based newer motor
- Support diagnostics
Still incomplete
- Support reach is still weak.
- Cura-like trunk / anchor growth from buildplate upward is still missing.
BUILDPLATE_ONLY_CANNOT_REACH_OVERHANGwarning continues.- Support-on-model is currently disabled.
This means the current page should present the app honestly as a working and advancing fabrication tool, while clearly stating that the support engine is the main remaining technical weakness in 3D print mode.
Detailed capability map
Below is a structured summary of the current capabilities described for the application. This wording is intentionally aligned with the present state rather than marketing claims beyond the implementation.
3D print capabilities
- STL / mesh-based slicing
- Adaptive layer settings infrastructure
- Wall / inner wall / outer wall generation
- Top / bottom / skin generation
- Sparse infill generation
- Skirt / brim infrastructure
- PLA material preset
- Nozzle / bed / fan temperature handling
- Retraction / unretraction
- Filament, time, layer, and path calculations
CNC + laser capabilities
- CNC pocket / contour logic
- Heightmap / probe infrastructure
- CNC smoke tests
- Laser G-code generation
- Fill / engraving-like laser paths
- Laser sample job system
- M3 / M5 style laser control flow
- Laser smoke tests
Validation + profiling
- Risk warnings and validation reports
- Travel / extrusion path measurement
- Motion count and layer count
- Production fast mode
- Shadow / debug analysis disabled in normal production
- Performance profiler: slice, support emitter, G-code emit, hardening, validation timings
Development path
The most realistic next milestone is not a broad rewrite, but continued hardening around the current architecture while improving the support engine without breaking already working CNC, laser, wall, skin, infill, and validation logic.
1
Stabilize current core
Keep the strong parts stable: safety logic, output reporting, CNC / laser modes, and current 3D print wall / skin / infill behavior.
2
Improve support reach
Focus on the support motor where the main gap remains: buildplate-only support reach and Cura-style trunk / anchor growth toward overhang regions.
3
Expand production confidence
Continue using logs, metrics, summaries, smoke tests, and validation output to make generated toolpaths easier to trust and easier to diagnose.
Measured sample output
These numbers are taken from local sample output generated by GcoWorks. They are included to show the current working state of the application without claiming final parity with mature commercial tools.
3D Print sample
- Machine ready: true
- Layer count: 657
- G-code lines: 441,706
- Filament: 93.21 g
- Estimated time: 9.21 h
- Support preset: Balanced
Note: difficult overhang / support reach warnings may still require review.
CNC sample
- Machine ready: true
- Production ready: true
- Passes: 10
- Cut path: 141,264 mm
- Detail score: 96
- Validation errors: 0
Laser sample
- Machine ready: true
- Process: Engrave
- Vector segments: 142
- Objects: 5
- Layers: 3
- Generation time: 90 ms
Browser STL preview demo
This public browser demo is a lightweight but working preview of the active GcoWorks desktop workflow currently being tested for fabrication use. It uses the actual GcoWorks application UI structure: mode rail, workspace panel, models list, transform panel, viewport toolbar, quick status dock, and inspector panel. STL files are previewed locally in the browser and are not uploaded.
GcoWorks
GcoWorks Privacy Policy
Effective date: May 27, 2026
GcoWorks is a fabrication-focused desktop application for 3D printing, CNC, laser preparation, G-code generation, machine-preview workflows, model inspection, validation, diagnostics, and fabrication-oriented reporting. GcoWorks is currently in development.
Information We Collect
GcoWorks does not require users to create an account for core local 3D print, CNC, laser, model-preview, and G-code preparation workflows. Imported files, machine settings, material settings, tool settings, process settings, screenshots, exports, generated G-code, logs, metrics, summaries, validation outputs, and project-related outputs may be stored locally on the user’s device depending on how the user chooses to use the app.
Local Files and Fabrication Data
3D model files, STL files, OBJ files, GLTF/GLB files, SVG files, DXF files, image files, CNC relief inputs, laser design files, generated G-code files, diagnostic outputs, validation reports, machine-readiness summaries, and fabrication reports are intended to remain local unless the user chooses to export, upload, send, or share them through another service.
Live Web Demo
The live browser demo is a lightweight but working preview of the active GcoWorks desktop workflow currently being tested for fabrication use. It may allow users to select an STL file from their device and preview it in the browser. The public demo is limited compared with the desktop app and does not generate production G-code. Selected STL files are intended to be read locally by the browser and are not uploaded to our own servers by the demo. Users should avoid selecting sensitive, confidential, or proprietary files unless they understand how their browser and device handle local file access.
Diagnostics and Logs
GcoWorks may generate local diagnostic logs, G-code timing information, validation results, machine-readiness reports, motion metrics, support reports, quality summaries, technical reports, and other diagnostic outputs to help the user understand G-code behavior, preview machine output, and troubleshoot issues. These files are intended for local use unless the user chooses to share them.
Third-Party Services
If future versions include third-party integrations, cloud services, licensing services, analytics, update systems, app-store services, or online collaboration features, this policy will be updated to explain what data is processed and why. The public website or browser demo may load standard web assets or viewer libraries from hosting or CDN providers. Those providers may receive normal web request metadata, but the demo is not designed to upload selected STL files to our own servers.
Payments
If GcoWorks is distributed through an app store or payment platform, payment processing will be handled by the relevant platform. GcoWorks does not receive or store full payment card details.
Data Sharing
GcoWorks does not sell user data. User files are not uploaded to our own servers as part of the core local desktop workflow unless the user chooses to use a future online service that explicitly requires upload, sharing, synchronization, or cloud processing.
Children’s Privacy
GcoWorks is not designed specifically for children. It is intended for general fabrication, 3D printing, CNC, laser preparation, G-code preview, model inspection, diagnostics, validation, and machine-oriented workflows.
Changes to This Privacy Policy
This Privacy Policy may be updated from time to time. Updates will be posted on this page with a revised effective date.
Contact
If you have questions about this Privacy Policy, contact us at: creatooo.com@gmail.com