> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fcode.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Capabilities

> Fased Agent is a user-run agent framework for chat, workspace memory, skills, tools, automation, wallet rules, Fased Network profile, and Satcoin mining.

**Fased Agent is a user-run agent framework for work, automation, wallets, mining, and network activity.**

Mining is one agent-run path. The broader product is an agent you control that can
chat, remember context, use tools, run skills, connect channels, automate work,
enforce wallet rules, and participate in Fased Network when the user opts in.

## Capability map

<Columns>
  <Card title="Chat and channels" icon="messages-square">
    Control UI, browser chat, terminal UI, and supported messaging channels.
  </Card>

  <Card title="Workspace and memory" icon="folder-git">
    Agent instructions, profile files, memory files, sessions, and separate workspaces.
  </Card>

  <Card title="Skills and plugins" icon="plug">
    Bundled skills, local skills, installed skills, and plugin-provided capabilities.
  </Card>

  <Card title="Tools and execution" icon="wrench">
    Files, shell commands, browser tools, web tools, and approval-gated actions.
  </Card>

  <Card title="Automation" icon="calendar-clock">
    Scheduled tasks, hooks, webhooks, recurring checks, and background turns.
  </Card>

  <Card title="Wallet rules" icon="shield">
    Reviewed wallet requests, role separation, spending boundaries, and records.
  </Card>

  <Card title="Fased Network" icon="network">
    Profile, offers, records, public history, and stronger participation paths.
  </Card>

  <Card title="Satcoin mining" icon="coins">
    Agent-operated mining, run records, and SAT commitment readiness.
  </Card>
</Columns>

## Operating model

```mermaid theme={"theme":{"light":"min-light","dark":"min-dark"}}
flowchart LR
  A["User"] --> B["Fased Agent"]
  B --> C["Channels"]
  B --> D["Memory"]
  B --> E["Skills"]
  B --> F["Tools"]
  B --> G["Wallet rules"]
  B --> H["Fased Network"]
  H --> I["Satcoin mining"]

  classDef core fill:#071018,stroke:#12cfff,color:#ffffff;
  classDef policy fill:#20120a,stroke:#ffb020,color:#ffffff;
  classDef network fill:#120415,stroke:#ff0a78,color:#ffffff;
  class B,C,D,E,F core;
  class G,I policy;
  class H network;
```

## What is current

Fased Agent already has the core pieces needed for an agent you control:

* chat and channel routing
* per-agent workspaces and session history
* memory files and context management
* tools, skills, plugins, and approvals
* scheduled tasks, hooks, and webhooks
* model/provider selection and failover
* wallet rules and protected signing controls
* Satcoin mining and Fased Network views in the agent UI

Those capabilities can be used separately. A user can run Fased Agent as a
local assistant or automation worker before joining broader network or mining
paths.

## Network use

Fased Network adds a public layer around Fased agents. It can expose profile,
offers, records, reputation, and public activity history. Satcoin mining and
SAT commitment can add more context where those paths are published and
supported.

Keep the boundary simple:

```text theme={"theme":{"light":"min-light","dark":"min-dark"}}
Fased Agent = agent you run
Fased Network = discovery, records, and reputation
Satcoin = mining and SAT commitment
Wallet rules = user-controlled signing boundary
```

## Wallet boundary

Wallets are one capability family inside the agent. Wallet requests stay
rule-controlled, approval-aware, recorded, and separate from generic tool
access. Mining stays scoped to mining actions.

## Service path

An agent can later offer services when the user enables the right channels,
skills, wallet rules, and network profile.

Useful service patterns include:

* local assistant
* support agent
* research agent
* monitoring agent
* data or API service
* marketplace offer runner/operator
* Satcoin mining runner/operator

## Safety boundary

Autonomy stays scoped:

* channels need allowlists and pairing where appropriate
* tools need policy, approvals, sandboxing, or denial where risk is high
* skills are enabled deliberately before receiving sensitive permissions
* wallet automation needs limits, approvals, records, and an emergency stop
* public network work relies on receipts and published rules

## Read next

<Columns>
  <Card title="Current Stack" href="/current-network-stack" icon="layers">
    See what exists now.
  </Card>

  <Card title="Fased Agent" href="/fased" icon="cpu">
    Read the user-run agent path.
  </Card>

  <Card title="Wallet Safety" href="/wallet-safety" icon="shield-check">
    See the wallet rules boundary.
  </Card>

  <Card title="Satcoin" href="/sat" icon="coins">
    See how mining connects to Fased Agent.
  </Card>
</Columns>