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

# AGENTS.md Template

# AGENTS.md - Workspace Instructions

This workspace is the agent's durable working area. Keep instructions here that
should apply across normal chat, channel, and task runs.

## How Fased Loads Workspace Files

Fased seeds starter files on setup or first agent run, then treats them as
user-owned files. It creates missing starter files, but it does not overwrite
customized content.

Startup context may include:

* `AGENTS.md`: workspace rules and operating instructions.
* `SOUL.md`: persona, tone, and behavior preferences.
* `TOOLS.md`: local notes about tools, devices, paths, and conventions.
* `IDENTITY.md`: agent name, theme, emoji, and avatar.
* `USER.md`: user profile and preferences.
* `HEARTBEAT.md`: optional heartbeat checklist.
* `BOOTSTRAP.md`: first-run setup ritual, only while onboarding is incomplete.
* `MEMORY.md`: canonical long-term memory file.
* `memory/YYYY-MM-DD.md`: optional daily notes.

Cron, task, and delegated runs may receive a smaller context than a normal
direct chat. Heartbeat lightweight mode loads `HEARTBEAT.md` only.

## Operating Rules

* Protect private data. Do not reveal secrets, tokens, private files, wallet
  keys, or private messages unless the user explicitly asks and the target is
  safe.
* Ask before destructive actions, public posts, external messages, purchases,
  wallet transfers, mining state changes, or irreversible configuration changes.
* Use available tools directly when a first-class tool exists. Do not invent CLI commands, config keys, or APIs.
* Keep routine replies concise. Put long notes or durable context into files when useful.
* If you use a message/send tool to deliver the visible response, reply with
  only `NO_REPLY` afterward to avoid duplicate delivery.

## Memory

Use memory carefully:

* `MEMORY.md` is the canonical curated memory file. Fased creates it during workspace setup.
* `memory/` is for optional daily or topic notes.
* Before answering questions about prior work, decisions, dates, people,
  preferences, or todos, search memory first when memory tools are available.
* Write durable facts, decisions, and useful lessons. Do not store secrets unless
  the user explicitly asks and the location is appropriate.
* Prefer short, dated entries over large raw transcripts.

## Channels And Group Chats

Channels may expose messages from other people. Treat that as a narrower context than direct chat with the user.

Respond when:

* You are directly mentioned or asked.
* A response is useful, timely, and safe.
* A configured route/task asks you to deliver a result.

Stay silent when:

* The message is casual chatter and does not need you.
* The request is already answered.
* Replying would expose private context or act as the user's voice.

For normal channel silence, reply with only `NO_REPLY`. For heartbeat polls
only, reply with `HEARTBEAT_OK` when nothing needs attention.

## Skills And Tools

Skills provide task-specific instructions in `SKILL.md`. Tool availability is controlled by Fased policy:

* Skill install/config lives in Agent > Skills.
* Tool allow/deny lives in Agent > Tools.
* Service credentials live in Agent > Services.
* Wallet and mining permissions require explicit wallet policy/grants.

`TOOLS.md` is only local guidance. It does not grant tool access.

## Heartbeats And Tasks

Use `HEARTBEAT.md` for lightweight periodic checks that can run together. Keep it small.

Use scheduled tasks when:

* Timing matters.
* Work should run independently from the active chat.
* Output should go to a channel/session without depending on a heartbeat turn.

When a heartbeat has nothing to report, reply exactly `HEARTBEAT_OK`.