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.
- Local lanes can support private or controlled work where the runtime makes them available.
- Open-weight models can support experimentation and controlled workflows.
- Behavior depends on device, runtime, model files, available resources, and workspace settings.
- 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
- What are Local Models Docs for?
- They explain local lanes, open-weight models, runtime configuration, limitations, and how local work fits into Ethen. They are the docs for understanding local lanes, open-weight model workflows, runtime assumptions, and private-context fit inside Ethen.
- Does local mean fully offline?
- Not always. Local lanes and full offline behavior are different. Exact behavior depends on runtime configuration and product support. Because users need a grounded view of local tradeoffs before they rely on the lane.
- What are open-weight models?
- Open-weight models are models whose weights are available for direct use under their applicable licenses. Only where the runtime and product surface support that behavior. The docs avoid stronger claims than the implementation proves.
- When should I use a local lane?
- Use a local lane where supported for sensitive context, private review, controlled experimentation, or workflows that benefit from staying closer to the environment. Yes. Many teams will use both, depending on the task and the sensitivity of the context.
- Can local models connect to Gateway?
- Local lanes can fit into Gateway routing where the runtime and route configuration support them. Runtime support, context boundaries, lane fit, and review posture.
- Can Ethen guarantee model compatibility?
- Model compatibility depends on the selected model, runtime, device resources, and workspace configuration. They help users choose local work intentionally instead of treating it like a vague privacy label.
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.