Know the system.
The commands. The context. The consequences. A practical guide to running your community with Fork.
Input→ Context→ Plan→ Approval→ Action→ Record
Find your next step.
Start with installation, look up an exact command, or understand the boundaries before changing your server. These guides describe implemented behavior, not a product wishlist.
Built to be looked up
Section titled “Built to be looked up”Search with Ctrl/Command K, a command name, an alias or a sentence from an article. The command reference includes every public source-registry path, parameter, permission review and known dispatch limitation. It distinguishes public commands from private operator interfaces.
Choose an area
Section titled “Choose an area”| Area | What you will find |
|---|---|
| Getting Started | Installation, native permissions, setup and dashboard access |
| AI & Intelligence | Responses, channels, tools, memory, limits and provider availability |
| Moderation | Actions, warnings, staff records and role hierarchy |
| Server Manager | Drafts, exact-plan approval, application and recovery |
| Automation | Scheduling, delivery and existing tasks |
| Dashboard | Server selection, settings, analytics and audit history |
| Security & Privacy | Authorization, personal memory and data boundaries |
| Troubleshooting | Symptoms, checks and safe next steps |
| Resources | FAQ, source-edition changes, support and service status |