Documentation

Guides

Install, manage, and build a lasting home for your personal AI.

• Assistant recovery — Recovery is an opt-in, same-instance runtime feature.
• Built-in harness plugins and keep-alive — Assistant includes the native AKM plugin and a native fhold plugin in OpenCode, Claude Code and Codex.
• Installation — Use a non-root Linux account with Docker Engine and Compose v2.
• Managing fhold — Select an instance with --name or -n: a directory name always means ~/fhold/instances/<name>, while an absolute path can select any location.

Connect

Use fhold from your clients, messaging apps, and native agent tools.

• Claude Desktop — Use the fhold desktop extension to connect Claude Desktop to an fhold agent running on the same computer.
• Discord adapter — Discord is an optional adapter.
• Experimental Codex and Claude Code remote sessions — Both integrations remain experimental.
• Public remote MCP deployment — This deployment is optional.
• Slack adapter — Slack is an optional Socket Mode adapter and MCP client of Guardian.

Reference

Configuration and interfaces for using fhold.

• Environment, mounts, and networks — This document describes the active runtime.
• Guardian MCP API — Guardian is a curated MCP agent gateway.
• Managed harness configuration — fhold installs AKM and fhold integrations for OpenCode, Codex and Claude Code at image build time.
• OpenCode configuration — fhold uses OpenCode directly; it does not maintain a parallel agent/session abstraction.

Maintainers

Development, testing, architecture, implementation reviews, and release procedures.

• Admin verification — The current preview removes the Welcome/creation headings and duplicate naming screen.
• AI-service and model verification — This qualifies Agent settings: native sign-in, local/custom endpoints, explicit model tests and choosing the agent's default.
• Architecture — fhold is a personal OpenCode agent with persistent knowledge and recurring work.
• Core principles — This is fhold's living product and security contract.
• Dependencies and development — The source workspaces share one root bun.lock.
• Documentation website — The website is built in this repository from the canonical docs/ Markdown files.
• Ephemeral Assistant implementation map — The generic feature is implemented, not a proposed host-specific runtime.
• Ephemeral Assistant runtime and recovery plan — The same self-contained fhold Assistant runs on ordinary persistent disk or ephemeral local storage.
• Future SSH instance management — Status: unimplemented proposal, not a release commitment.
• Linux qualification and release limits — Canonical source is fwdslsh/fhold on GitHub.
• Managed harness policy verification — Local Linux x64 verification on 2026-10-04, branch codex/managed-harness-policy, based on public main c6c5487.
• Native plugins and keep-alive verification — The local Linux x64 Assistant candidate fhold/assistant:release-0.2.2610081-beta.1 passed the standard image smoke.
• OpenCode 2 migration: AKM and akm-plugins agent handoff — Status: implementation brief, not a completed migration.
• OpenCode 2 migration: fhold agent handoff — Status: implementation brief, pending AKM and akm-plugins OpenCode 2 updates.
• Portable backup and restore review — Reviewed 2026-10-01.
• Release runbook — GitHub at https://github.com/fwdslsh/fhold is the canonical source and contribution host.
• Testing workflow — Run from a fresh locked checkout and use disposable explicit fhold homes.