Configuration

ForgeDeck data locations, settings, and per-project files.

Embed
Preview of the card
<a href="https://docs.forgedeck.net/configuration"><img src="https://docs.forgedeck.net/_api/public/orgs/db9cb8ff-b606-46cf-bbcd-02c8f8a9a3e2/spaces/6f417400-93ca-41a8-a914-df2ae3981dc6/pages/d37e98bb-182d-430f-80ba-9cea5b672339/social-card.svg?v=3e7ae33eec8b" alt="Configuration" width="600" height="315"></a>

ForgeDeck is local-first — almost everything lives on your machine.

Where things live

  • App database — forgedeck.sqlite in your platform user-data directory. The source of truth for projects, tasks, terminal sessions, agent profiles, worktree metadata, and memory indexes.

  • Project memory — .forgememory/ inside each project (markdown, redacted).

  • Run artifacts — .forgedeck/runs/<task-id>/prompt.md per launch.

  • Agent contract — an optional AGENTS.md in a managed room (see below).

Settings

Settings (cloud endpoint, agent defaults, voice, MCP, memory engine) live in the app and the local DB. Cloud features are off until you sign in.

AGENTS.md

AGENTS.md is the operating guide for agents working inside ForgeDeck-managed rooms: stay within task scope, don't edit files outside the ownership list, never read or print secrets, don't modify .env, and end with a FORGEDECK_RESULT block. Honor it when an agent acts in a room.

Updated