---
summary: "Set up Fased Agent with channels, wallets, Fased Network, and Satcoin mining."
read_when:
  - Onboarding a new assistant instance
  - Reviewing safety/permission implications
  - Moving from first chat to a real operator setup
title: "Fased Agent Setup"
---

# Fased Agent Setup

Fased Agent is the agent you run on your machine or server. Start with the
Gateway and browser dashboard, then add models, skills, services, channels,
wallets, Fased Network, or Satcoin mining only when they have a specific job.

Use this page after first boot to turn a working install into a real Agent
setup.

<Columns>
  <Card title="Getting Started" href="/start/getting-started" icon="rocket">
    Install Fased, onboard the machine, and open the dashboard.
  </Card>
  <Card title="Control UI Setup" href="/start/control-ui-setup" icon="layout-dashboard">
    See what belongs in onboarding, Agent setup, Services, Tasks, and Advanced Config.
  </Card>
  <Card title="Operator Glossary" href="/start/operator-glossary" icon="book-open">
    Learn the shared wallet, mining, bond, and Fased Network terms.
  </Card>
</Columns>

## Agent Model

```mermaid
flowchart TB
  entry["Channels / Control UI"] --> gateway["Gateway"]
  gateway --> agent["Fased Agent + workspace"]
  agent --> tools["Tools + plugins"]
  agent --> wallets["Wallet use"]
  agent --> network["Fased Network"]
  agent --> mining["Satcoin mining"]

  classDef entry fill:#120605,stroke:#ff5a36,color:#ffffff;
  classDef core fill:#071018,stroke:#12cfff,color:#ffffff;
  classDef operator fill:#20120a,stroke:#ffb020,color:#ffffff;
  class entry entry;
  class gateway,agent core;
  class tools,wallets,network,mining operator;
```

The recommended order is:

1. make the install stable
2. connect one trusted model
3. send the first browser chat
4. add skills, services, memory, channels, and tasks
5. add wallets, Fased Network, or Satcoin mining only when the base agent is ready

## 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 and mining workflows separate from normal chat
- review skills and services before allowing them for an Agent

For host hardening and gateway operations, use [Gateway & Ops](/gateway).

## First Operator Pass

After onboarding:

```bash
fased dashboard
fased status
```

Then work from the selected Agent:

| 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   |

Dashboard is the launch/status board. Use `/agents` for real setup.

## Workspace And Memory

The default workspace is:

```text
~/.fased/workspace
```

Fased creates starter files such as `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:

- [Agent workspace](/concepts/agent-workspace)
- [Memory](/concepts/memory)
- [Control UI Setup Model](/start/control-ui-setup)

## Wallet, Network, And Satcoin

Fased works without wallets or Satcoin. Add wallets, Fased Network, or Satcoin modules
only when they have a specific job:

| Path          | When to use it                                                                   |
| ------------- | -------------------------------------------------------------------------------- |
| Wallet use    | When the Agent needs reviewed sends, balances, receipts, or wallet-connected skills |
| Fased Network | When the Agent needs a public handle, route, offers, or operator history         |
| Satcoin mining | When the Agent will mine, claim, and build public mining history                |
| Bond          | When bonded SAT should support a stronger operator role                          |

Relevant pages:

- [Wallet](/plugins/crypto/wallet-page)
- [Fased Network](/start/federation)
- [Mining](/plugins/crypto/mining-page)
- [Advanced SAT mining](/plugins/crypto/mining-advanced)
- [Bond operator overview](/start/bond-operator-economy)

## Channels And Tasks

Connect channels only after the browser chat works. Route each account, topic,
or guild to a selected Agent from `Agent > 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

```bash
fased status
fased status --all
fased status --deep
fased health --json
```

Logs live under `/tmp/fased/` by default.

## Next Steps

<Columns>
  <Card title="Setup Matrix" href="/start/setup-matrix" icon="split">
    Choose Local or Hosting and understand setup ownership.
  </Card>
  <Card title="Gateway runbook" href="/gateway" icon="server">
    Operate the Gateway, auth, logs, health checks, and remote access.
  </Card>
  <Card title="Tasks" href="/automation/cron-jobs" icon="calendar-clock">
    Schedule recurring Agent work and understand run history.
  </Card>
  <Card title="Security" href="/gateway/security" icon="shield">
    Review tokens, allowlists, sandboxing, and host boundaries.
  </Card>
</Columns>
