Read Only
PresetLow Risk
Safe read operations — no file mutations or shell commands
Permission patterns5
ReadGlobGrepLSNotebookRead
Settings
Manage your Orionfold Relay configuration
Access & sessions
Trusted-local Relay stays loopback-only and does not require a browser session. Authenticated profiles are selected when the server starts.
Relay cell boundary
Host administrator trustedThis Relay process and data directory form one Relay cell. Customer and project records organize work inside this cell; they do not isolate data, files, credentials, agents, or runtimes. The Relay Host administrator can access every cell on this Host. Use a separate cell for client isolation, or a separate VM or machine when the Host administrator must not have access.
- Cell ID
- Not initialized
- Data directory
- /var/folders/f2/nwvhwzp101l0mxnhvx9c0flh0000gn/T/relay-demo-capture-TTWPuo
- Database
- /var/folders/f2/nwvhwzp101l0mxnhvx9c0flh0000gn/T/relay-demo-capture-TTWPuo/relay.db
- Launch workspace
- /srv/relay/workspace
Data directory source: explicit RELAY_DATA_DIR.
Instance maintenance
Dev modeRunning on the main dev repo. Instance upgrade features are disabled. Set RELAY_INSTANCE_MODE=true to test.
License
Licenses are verified offline and stored on this machine — the CLI banner,
relay license status, and this page all read the same store. Installed packs are yours forever; a license only gates new premium installs.- Licensed to [email protected]product:orionfold-relay1 seat
OF-RELAY-VERIFY-20260701 · issued Jul 1, 2026 · renews Jul 1, 2027
Activate a license
Relay Host deployment
Run licensed Relay Cells on a device or server you control. Your account, bill, data, backups and keys remain yours.
- 1. Placement
- 2. Configure
- 3. Estimate
- 4. Authorize
- 5. Install
- 6. Verify
- 7. Handoff
Choose where the Relay Host runs
A Host is one machine. Each managed Cell is a complete isolated Relay workspace on that Host.
DigitalOcean guided beta
Run one licensed Relay Host on your own Ubuntu Droplet using the validated manual guide. You own the cloud account, bill, DNS, backups, keys and administration.
Proven baseline: 2 vCPU · 4 GiB RAM · 80 GiB disk · authenticated HTTPS. Relay does not request a provider token or create the Droplet.
Open DigitalOcean guide opens in new tabHost administrator trust
The Host administrator can inspect every resident Cell. Put a customer on a separate machine or VM when they do not accept that administrator.
Managed Host automation is paid-license gated
A signed product:relay-host license is required for managed Host automation. Comparison, ownership and recovery guidance remain readable. A direct unmanaged Relay Cell remains free.
Open License settingsLifecycle and recovery capability
Relay only enables operations whose domain contracts are implemented and verified.
Backup, restore and export
Available separatelyCreate and verify encrypted, customer-owned recovery before export-and-release.
Open Encrypted RecoveryUpgrade and rollback
Not yet enabledA managed Cell-image upgrade contract is required; this UI does not claim a no-op succeeded.
Transfer and Fleet control
Not yet enabledThis Host controls only resident Cells. Cross-Host authority remains a separate future controller.
Providers & Runtimes
Loading provider configuration...
Ollama
Connect Relay to an Ollama server or the Ollama cloud API. Privacy, cost, and authentication depend on that endpoint.
Requests originate from the Relay server, not from this browser.
Local Ollama commonly needs no key; direct ollama.com access requires a Bearer API key.
Required only for a non-loopback http:// endpoint. Credentials and prompts can be read in transit; HTTPS is recommended.
Not tested
OpenAI-compatible servers
Relay preserves each runtime identity across Chat, tasks, workflows, schedules, and usage receipts.
LiteLLM
Connect Relay to a LiteLLM gateway. Routing, locality, privacy, and cost depend on the gateway's upstream configuration.
Requests originate from the Relay server, not from this browser.
Required only for a non-loopback http:// endpoint. Credentials and prompts can be read in transit; HTTPS is recommended.
Not tested
Gateway-managed models
Add or change upstream models in the LiteLLM administrator interface, then refresh Relay's model list.
LM Studio
Connect Relay to an LM Studio server on this host or your network. Serving and API-token policy are operator choices.
Requests originate from the Relay server, not from this browser.
Required only for a non-loopback http:// endpoint. Credentials and prompts can be read in transit; HTTPS is recommended.
Not tested
Chat
Configure defaults for the chat conversation interface.
Model preference
What matters most to you? Drives the recommended default and re-resolves sensibly when new models are released.
Default Model
Model used for new chat conversations. Can be overridden per conversation.
Runtime
Configure runtime behavior for AI operations.
SDK Timeout
Maximum seconds to wait for AI responses.
Fast Response60 secondsThorough Analysis
Recommended: 30–120s
Max Turns
Maximum number of agent turns per task execution.
Quick Execution10 turnsExtended Reasoning
Recommended: 15–40 turns
Self-Learning
Configure how agents accumulate and manage learned context from task executions.
Context Memory Limit
Maximum characters of learned context stored per agent profile.
Focused8K charactersComprehensive
Recommended: 4K–16K characters
Web Search
Enhanced web search capabilities for agents. These are free services with no API keys required. They extend the built-in WebSearch and WebFetch tools with better search quality and cleaner page reading.
Exa Semantic Search
Neural search engine that finds conceptually related content, not just keyword matches. Available to researcher, general, and data-analyst profiles. All tools are read-only and auto-approved.
Environment
How Orionfold Relay discovers and syncs skills from your environment into the agent profile registry.
Auto-promote discovered skills
When enabled, every unlinked skill in ~/.claude/skills/ with a valid SKILL.md is automatically converted into an agent profile on the next environment scan. Leave off to review and promote skills manually from the Environment dashboard.
Dashboard
Choose which local operational modules appear on Home and whether unresolved work and recent autonomous activity influence their order.
Promotes operator action, active work, health issues and recent output using deterministic local signals.
Failed, waiting, queued and active work requiring operator awareness.
Recent agent and workflow activity.
Installed operating surfaces and their active primitives.
Recently active project scopes and task completion.
Recent retained documents and task outputs.
Recent Relay capabilities with direct product destinations.
Run receipts that still lack complete provider pricing.
Detected model providers that still need configuration.
Remaining first-run milestones without repeating navigation.
Current local workshop run and checkpoint progress.
Browser Tools
Enable browser automation MCP servers for chat and task agents. Read-only tools (screenshots, snapshots) are auto-approved. Mutation tools (click, navigate, type) require permission.
Chrome DevTools MCP
Connect to a running Chrome instance via CDP. Best for debugging live apps, performance profiling, and network inspection.
Playwright MCP
Launch a headless browser for autonomous tasks. Best for research, scraping, testing, and structured page analysis.
Delivery Channels
Configure Slack, Telegram, or webhook channels for schedule notifications and agent output delivery.
No delivery channels configured. Add one to start receiving notifications.
GitHub
Connect once, then reuse the same account for public or private Pack repositories and GitHub Pages publishing.
ConnectionNot connected
Relay will never return the token to the browser or expose it to chat.
GitHub CLIInstalled
Use the active account configured with gh. Relay accesses and validates its credential only after you choose this method, and never stores it.
Grant repository Contents read/write access only to repositories Relay should publish. Repository visibility remains your GitHub setting.
Cost & Usage Guardrails
Set one monthly budget, let Orionfold Relay derive daily pacing, and keep provider spend splits aligned with the runtimes you actually have configured.
Monthly Budget
Overall spend cap
Leave blank to keep spend unlimited. Daily pacing is derived automatically.
Provider Allocation
Split the monthly cap
Adjust one slider. Orionfold Relay writes the provider cap figures for you.
Anthropic50%
Anthropic
Unlimited
50% — shared by Claude Code & Anthropic Direct
OpenAI
Unlimited
50% — shared by Codex & OpenAI Direct
Claude Plan
Claude OAuth billing
Claude OAuth uses fixed monthly subscription pricing for budgeting instead of token-priced usage.
Budget basis
Dashboard pacing and guardrail enforcement use the selected plan price as Claude's monthly cost basis. Activity and tokens still appear in audit views.
Latest Pricing
Official provider pricing with manual refresh and the last known update time.
Stale
anthropic
Updated Mar 16, 2026, 5:00 PM
Claude Opus
Input / output
$5.00 / 1M
$25.00 / 1M
Claude Sonnet
Input / output
$3.00 / 1M
$15.00 / 1M
Claude Haiku
Input / output
$1.00 / 1M
$5.00 / 1M
Claude Pro
Monthly plan
$20.00
Claude Max 5x
Monthly plan
$100
Claude Max 20x
Monthly plan
$200
openai
Updated Mar 16, 2026, 5:00 PM
Codex Mini
Input / output
$1.50 / 1M
$6.00 / 1M
GPT-5
Input / output
$10.00 / 1M
$30.00 / 1M
GPT-4o
Input / output
$2.50 / 1M
$10.00 / 1M
Live Status
Current spend pacing
Derived daily pacing is recalculated from the monthly cap using the current calendar month.
Overall monthly spend
$20.00 / Unlimited
Resets Aug 1, 2026, 12:00 AM
Today pace vs derived daily cap
$0.6452 / Unlimited
Resets Jul 21, 2026, 12:00 AM
Claude Code
Plan pricedMonthly $20.00 of Unlimited
Today $0.6452 / Unlimited
OpenAI Codex App Server
Usage pricedMonthly $0.00 of Unlimited
Today $0.00 / Unlimited
Anthropic Direct API
Usage pricedMonthly $0.00 of Unlimited
Today $0.00 / Unlimited
OpenAI Direct API
Usage pricedMonthly $0.00 of Unlimited
Today $0.00 / Unlimited
Ollama
Usage pricedMonthly $0.00 of Unlimited
Today $0.00 / Unlimited
Warning notifications fire once per window after 80% of a configured cap is reached.
Permission Presets
One-click permission bundles for common use cases. Presets are additive. Enabling a higher-risk preset includes all lower-risk permissions.
Git Safe
PresetMedium Risk
Read operations plus file editing and git commands
Permission patterns8
ReadGlobGrepLSNotebookReadWriteEditBash(command:git *)
Full Auto
PresetHigh Risk
All tools auto-approved — maximum agent autonomy
Permission patterns11
ReadGlobGrepLSNotebookReadWriteEditBashNotebookEditWebFetchWebSearch
Tool Permissions
Tools matching these patterns are automatically approved when agents request permission. Revoke a pattern to require manual approval again.
No saved permissions. Click "Always Allow" on a tool permission request in the Inbox to add one.
Database Snapshots
Create, schedule, and restore full-state backups of your database and files
Enable automatic backups
Snapshots are created at the configured interval
No snapshots yet. Create one to get started.
Encrypted recovery
Portable, customer-owned Cell recovery without an Orionfold-held key.
Customer recovery key
Not configured. Key bytes and file paths are never returned to this page.
Separate destination
Not configured. Store the bundle and key in different locations.
Create a key with
relay recovery key create --out …, then set RELAY_RECOVERY_KEY_FILE and RELAY_RECOVERY_DESTINATION on the server.Restore is intentionally offline and accepts only a missing or empty data root. Relay cannot recover a lost customer key and makes no RPO/RTO promise from a local-directory destination.
Data Management
Reset or populate your Orionfold Relay instance
Seeding and clearing sample data are staging-only tools. They are turned off on this build so your real data stays safe.