Roadmap

See how Orek sets roadmap priorities and where its current product boundaries are.

Explore what ships today in Using Orek, or check Release status for current platform support. The horizon tracks below outline our planned priorities in rough delivery order.

Track 1 · Foundation & trust

Post-release improvements

Immediate improvements to installer trust, customer sign-in options, and user support channels.

Signed platform installers

Native code signing and notarization for macOS and Windows downloads so first-run installation requires no operating-system security override.

Sign in with Apple

Apple account sign-in alongside Google and GitHub in the customer console for purchasing licenses and managing active devices.

Expanded user support

Streamlined issue reporting, faster diagnostic collection, and expanded troubleshooting guides across supported platforms.

Track 2 · Autonomous workflows

Agent capabilities and scheduling

Recurring background tasks, session spend controls, and richer binary, media, and file-management tools.

Scheduled & recurring prompts

Schedule prompts to run on a recurring cadence for repository monitoring, dependency checks, and automated maintenance tasks.

Session spend ceilings & cost visibility

Set optional budget ceilings per session and inspect token and cost breakdowns across delegated agents and workflow steps.

Rich media, binary & file tools

Inspect bounded binary file ranges, copy or move workspace files directly with dedicated tools, and expand cross-session project memory with structured search.

Track 3 · Credential security

Secrets and enterprise credentials

External secret managers, zero-plaintext secret references, and secure credential workflows for local and containerized environments.

Pluggable secret manager backends

Store provider API keys and runtime credentials in 1Password, HashiCorp Vault, AWS Secrets Manager, or Google Cloud Secret Manager instead of the local OS keyring.

External secret references & roaming

Reference team or personal vault items directly in configuration without writing plaintext keys to disk, and roam user credentials across workstations.

Project environment & container secrets

Mount project environment secrets with per-repository consent and authenticate headless or containerized runs through secret-manager service endpoints.

Track 4 · Intelligence & retrieval

Search, execution, and routing

Broader web research integrations, provider-hosted sandboxes, and smarter automatic model selection.

Authenticated web search

Connect external search APIs alongside provider-hosted web tools for grounded documentation lookup and issue research.

Hosted code execution & artifacts

Run isolated calculations and verification scripts in provider-hosted execution environments and return generated outputs directly to the conversation.

Adaptive model routing

Extend route and complexity matching with live prompt-cache awareness, historical verification outcomes, and latency feedback.

Track 5 · Specialized domain packs

Optional game development support

Opt-in indexing and asset discovery tools tailored for game-engine projects without adding overhead to standard software repositories.

Game-engine project indexing

Index scene hierarchies, resource metadata, and cross-asset dependencies for Unity, Godot, and Unreal Engine projects.

Faceted asset search

Filter project assets by type, tags, dimensions, and dependency references alongside standard source-code search.

Local multimodal asset tagging

Automatically classify and tag untagged textures, audio, and 3D assets using local multimodal models on your machine.

Track 6 · Perpetual licensing · BYOK

Business and enterprise licensing

Individual perpetual licenses are available today. Multi-seat team management, centralized seat assignment, and volume licensing are planned for organizations.

Each perpetual license covers its purchased major release series (such as 2026.x) across up to 3 devices, with a 14-day trial on 1 device and offline local verification. You configure your own model-provider keys locally in Orek and pay providers directly for usage.

How Orek sets priorities

Three principles shape what comes next:

  • Measured improvements: changes to code retrieval, code navigation, and compaction are tested on repeatable multi-file coding tasks with fixed models and settings. Token use and speed in your own work depend on your project, models, and settings.
  • Local-first, bring your own keys: the agent, indexing, and workflows run on your machine under your perpetual major-release license and your own model provider keys, with no required hosted service in between. Manage licenses and devices in the customer console.
  • Platform parity: macOS 14+ (Apple Silicon) and Windows x86_64 are Supported today; Linux x86_64 is Experimental while OS sandboxing and packaging mature.

Product boundaries

Area Current boundary
Model and embedding requests Orek runs on your machine. Cloud model and embedding providers receive the context sent to them; see Local models and Providers.
Saved context Compaction summarizes earlier conversation turns while keeping recent messages intact; see compaction settings.
Permissions Subagents and workflow steps share the session’s workspace and permission rules. Review subagent changes before committing them, and see Plan mode and Permissions and security.
Telemetry Sending traces and metrics to an OpenTelemetry collector is off unless you set observe.otlp_endpoint; see OpenTelemetry export.
Account services The website manages licenses, devices, and billing. Approval rules, sessions, and checklists stay on your machine.

Feedback and bug reports

Report issues or request features through Support, and see System requirements & release status for current platform coverage.