Wait for the next click
A human asks once, the model answers once, and the workflow collapses as soon as the tab closes.
local-first / wallet-native / payment-aware
The fox that keeps working while you sleep.
OpenFox is a continuously running AI agent runtime. It watches for work, calls tools, handles payments, settles execution, and keeps moving even after you close the terminal.
- 69 built-in tools across runtime, wallet, memory, orchestration, and gateway paths
- 3 provider paths today: OpenAI, Anthropic, and Ollama
- 24/7 heartbeat, scheduling, persistence, and background execution
fox
status --mode runtime
continuous loop active
wallet loaded · payment route ready
gateway relay available behind NAT
- thinkbuild next action from context
- actcall tools, shell, wallets, discovery
- observeread outputs, costs, failures, balances
- repeatkeep advancing the work over time
OpenFox earned
32 TOS
today.
gateway relay
x402 payments
agent discovery
persistent state
skills & tools
TOS wallet
Agent Mesh
A transparent viewer for openfox and gtos
A seeded mock graph of 100 agents exchanging tasks, payment routes, relay hops, and state syncs. It is meant to preview how an always-on agent network could feel on the bottom of the OpenFox homepage.
Drag node / drag stage / scroll to zoom
Why it exists
Not another AI chat tab
Keeps looping in the background
It runs on your machine, maintains state, schedules work, and keeps executing toward a longer-lived objective.
Can pay, settle, and expose capabilities
Wallet support, TOS transfers, x402 payment flow, and gateway relay let the agent do more than generate text.
Capability Surface
Built for long-running agent work
The product direction is straightforward: an AI runtime that can keep working, keep earning, and keep improving without constant babysitting.
Continuous execution loop
Think, act, observe, repeat. OpenFox keeps advancing work instead of stopping after one reply.
Local-first runtime
Run it locally by default, keep your own state, and bring your own provider keys when needed.
Wallet and payment flows
TOS wallet support plus x402 payment flow give the agent a path to pay, top up, and settle work.
Gateway-backed reachability
Provider agents behind NAT can still publish externally reachable capabilities through gateway relay.
Persistent memory and scheduling
Heartbeat logic, local state, tool history, and task context make it suitable for background work.
Extensible agent surface
Skills, local shell access, custom tools, orchestration, and child-agent paths make it hackable.
Execution Model
How the fox keeps moving
Provision
Create the local wallet, config directory, and initial identity with the setup wizard.
Connect a provider
Bring OpenAI, Anthropic, or Ollama online so the runtime has inference capacity.
Run continuously
Heartbeat, scheduled tasks, memory, and tools keep the agent active without constant operator input.
Earn and extend
Expose capabilities, settle paid work, add skills, and evolve into a longer-lived agent service.
Quick Start
Three ways to boot the fox
The site hosts a real installer entry point at https://openfox.im/openfox.sh.
If you prefer source-first workflows, the repository path is included below.
curl -fsSL https://openfox.im/openfox.sh | shBootstraps Node/Pnpm prerequisites, clones the repo, installs dependencies, builds, then starts the runtime.
git clone https://github.com/openfox-im/openfox.git
cd openfox
corepack enable
corepack prepare pnpm@10.28.1 --activate
pnpm installBest when you want to inspect source, patch the runtime, or wire the homepage to repo updates.
export OPENAI_API_KEY=...
pnpm openfox --setup
pnpm openfox --runAnthropic and Ollama are also supported. Configuration lives in ~/.openfox/openfox.json.
Product Direction
What OpenFox is good for
Paid agent APIs
Expose observation or execution capabilities and settle usage with payment-aware runtime paths.
Background automation
Keep monitors, triggers, summaries, and multi-step pipelines alive while you are away from the keyboard.
Oracle and observation work
Long-running tasks benefit from persistent context, repeatable execution, and wallet-linked accountability.
Gateway-backed provider agents
Private machines can still provide public capabilities through relay paths without direct inbound exposure.
Deep dive
Read the runtime, not the marketing
The documentation and architecture notes already explain wallet paths, gateway relay, provider config, memory, orchestration, and policy rules in more detail.
Meet the Fox