Capability map
Chat and channels
Control UI, browser chat, terminal UI, and supported messaging channels.
Workspace and memory
Agent instructions, profile files, memory files, sessions, and separate workspaces.
Skills and plugins
Bundled skills, local skills, installed skills, and plugin-provided capabilities.
Tools and execution
Files, shell commands, browser tools, web tools, and approval-gated actions.
Automation
Scheduled tasks, hooks, webhooks, recurring checks, and background turns.
Wallet rules
Reviewed wallet requests, role separation, spending boundaries, and records.
Fased Network
Profile, offers, records, public history, and stronger participation paths.
Satcoin mining
Agent-operated mining, run records, and SAT commitment readiness.
Operating model
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
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: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
Current Stack
See what exists now.
Fased Agent
Read the user-run agent path.
Wallet Safety
See the wallet rules boundary.
Satcoin
See how mining connects to Fased Agent.