Fased Agent Setup
Fased Agent is a self-hosted agent runtime. Start with the Gateway and browser dashboard, then add models, skills, services, channels, wallets, Fased Network, or SAT mining only when the base agent is trusted and the operator setup needs them. Use this page after first boot to turn a working install into a real Agent setup.Getting Started
Install Fased, onboard the machine, and open the dashboard.
Control UI Setup
See what belongs in onboarding, Agent setup, Services, Tasks, and Advanced Config.
Operator Glossary
Learn the shared wallet, mining, bond, and Fased Network terms.
Runtime Model
The recommended order is:- make the runtime stable
- connect one trusted model
- send the first browser chat
- add skills, services, memory, channels, and tasks
- add wallet, Fased Network, or SAT mining only when the base agent is trusted
Conservative Defaults
Start conservative:- keep the Gateway private by default
- use Tailscale for hosted/admin access
- connect one trusted channel before adding public routes
- keep wallet-bearing and mining workflows separate from normal chat
- review skills and services before allowing them for an Agent
First Operator Pass
After onboarding:| Surface | Use it for |
|---|---|
Agent > Models | Provider auth, primary model, fallback model, task model |
Agent > Skills | Create, install, configure, review, and allow Agent skills |
Agent > Services | Web/search, Gmail, Calendar, GitHub, browser/media, and custom APIs |
Agent > Channels | Chat app setup and routing to this Agent |
Agent > Memory | Session-memory and archive state |
Agent > Tasks | Saved tasks, triggers, workflows, graphs, programs, and templates |
/agents for real setup.
Workspace And Memory
The default workspace is:AGENTS.md, SOUL.md, TOOLS.md,
IDENTITY.md, USER.md, HEARTBEAT.md, MEMORY.md, and memory/ when the
workspace is new. Treat this folder like the agent’s operational memory and
keep it private.
Useful links:
Wallet, Network, And SAT
Fased works without wallets or SAT. Add wallet, Fased Network, or SAT modules only when they have a specific job:| Path | When to use it |
|---|---|
| Wallet policy | When the Agent needs reviewed sends, balances, receipts, or wallet-bound skills |
| Fased Network | When this runtime needs identity, hosted reachability, offers, or operator trust |
| SAT mining | When the node will mine, claim, and build public operator history |
| Bond | When SAT inventory should back an operator trust role |
Channels And Tasks
Connect channels only after the browser chat works. Route each account, topic, or guild to a selected Agent fromAgent > Channels.
Use Agent > Tasks for saved work definitions. Run history is audit data; the
owning domain page still controls the operation:
- Mining controls stay in Mining
- Wallet signing stays in Wallet
- Marketplace orders stay in Marketplace
- Channel routing stays in Channels
- Service auth stays in Services
Operations Checks
/tmp/fased/ by default.
Next Steps
Setup Matrix
Choose Local or Hosting and understand setup ownership.
Gateway runbook
Operate the Gateway, auth, logs, health checks, and remote access.
Tasks
Schedule recurring Agent work and understand run history.
Security
Review tokens, allowlists, sandboxing, and host boundaries.