DocumentationBrowse documentation
- Documentation
- Local Models
Local Models Docs
Understand where local model work fits.
Local Models Docs explain local lanes, open-weight models, runtime requirements, and how local work can fit alongside Gateway, Code, and workflows. Local execution depends on the device, runtime, model availability, resources, and workspace configuration.
Local work depends on the setup.
A local lane can keep some model execution closer to the user where supported. It does not automatically make the entire Ethen experience offline, and it is not the right path for every task.
- 01
Local lanes can support private or controlled work where the runtime makes them available.
- 02
Open-weight models can support experimentation and controlled workflows.
- 03
Behavior depends on device, runtime, model files, available resources, and workspace settings.
- 04
Local and cloud paths can complement each other through Gateway and workflow design where supported.
Core local model concepts
Use these concepts to decide whether a local path fits the work and what must be configured first.
- Local lanes
- Use a local lane for sensitive or controlled context where local support and runtime configuration are available.
- Open-weight models
- Open-weight models provide another option for experimentation, controlled workflows, and cost-aware iteration when the configured runtime supports them.
- Runtime requirements
- Local behavior depends on the device, runtime, model files, resource limits, model availability, and workspace configuration.
- Hybrid workflows
- Local steps can fit alongside flagship or open lanes, Gateway routing, and repeatable workflows where supported. Local outputs can still feed into broader reviewable workflows when the surrounding product surfaces support that path.
How local model work fits
- 01
Identify the context
Decide whether the task involves private code, internal notes, customer-related context, or draft material that may benefit from a local path.
- 02
Check local support
Confirm the device, runtime, model availability, resources, and workspace configuration for the intended work.
- 03
Choose the lane
Use a local lane where supported, or choose flagship or open lanes when they better fit the task.
- 04
Review the result
Keep the model choice, relevant context, outputs, and review notes connected to workspace history where available.
- 05
Connect the workflow
Use Gateway and Workflow concepts when local model steps need to become part of a repeatable process.
- 06
Scope
Local Models Docs explain local lanes, open-weight models, runtime requirements, and workflow fit. Exact setup and compatibility depend on the current product, model, device, and runtime configuration.
FAQ
Understand the local path before you depend on it.
Use Local Models Docs to understand local lanes, runtime requirements, open-weight models, and where local work fits inside Ethen.