Three steps from a fresh machine to a running portal. There is no separate daemon-start step: commands start it automatically when needed.

$ curl -fL https://agentdc.nqdiepoii.com/download/linux-amd64/agentdc-linux-amd64 -o agentdc
chmod +x agentdc
./agentdc

# install or update
$ irm https://…/install.ps1 | iex

# install the app and shortcuts without launching AgentDC
$ & ([scriptblock]::Create((irm https://…/install.ps1))) -NoStart

$ $AgentDC = "$env:LOCALAPPDATA\Programs\AgentDC\agentdc.exe"
$ Set-Alias -Name agentdc -Value $AgentDC

$ agentdc doctor

[ok]   windows        build 26200 >= 17763
[ok]   agent binary   claude
[ok]   git            2.51.0
[ok]   config         C:\Users\you\AppData\Local\agentdc
[--]   daemon         not running (the CLI starts one on demand)

Two key environment variables

Both are optional:

One daemon per AGENTDC_HOME. To run another daemon, change AGENTDC_HOME, not just the port. Changing only the port is rejected with an explanation.

Three logs, three locations

All paths are relative to <AGENTDC_HOME>.

$ agentdc portal
portal: http://127.0.0.1:8770/?k=…

This command starts the daemon if needed, creates a single-use key and opens the portal in your browser.

agentdc app is the equivalent CLI command to open the app with a visible terminal. Desktop and Start/Search shortcuts and a double-clicked download run AgentDC without arguments.

Projects and conversations

1. Sidebar → + Add project → choose a working folder.
2. Sidebar → + Add conversation → choose a project and agent.

A project is the working context: agents start with that project's directory as their cwd. Long-term memory belongs to the project, not the conversation. Conversations in the same project share one pillar tree.

You can also use the CLI:

# add a project and start an agent session
$ agentdc project add myapp C:\code\myapp
$ agentdc spawn myapp

# send a prompt and stream output until the agent is idle
$ agentdc send <sid> "read the README and explain the project"

Safety mode

The new-conversation dialog includes a Safety modeswitch: the agent runs in normal mode, without permission-bypass flags. The daemon adds a system prompt defining boundaries from the start. Enable it for conversations that interact with external users.

Persistent sessions

Agents run in ConPTY sessions managed by the daemon , not by your terminal. Closing a CLI terminal used forattach, closing the portal tab or signing out does not end the session or its transcript. The terminal opened by an AgentDC shortcut is different: it hosts the daemon, so closing it or pressing Ctrl+C stops AgentDC and its live sessions.

# attach to a live session; press Ctrl-] to detach
$ agentdc attach <sid>

# or read the transcript
$ agentdc logs <sid>

One prompt, N agents, N independent git worktrees. Compare results side by side and choose which one to keep.

$ agentdc fanout myapp --n 3 "add parser tests"
run 7f3a: 3 worktrees branched from commit 1c9de2f
3/3 agents completed

# compare the three attempts
$ agentdc fanout diff 7f3a

# inspect the full patch for attempt 2
$ agentdc fanout diff 7f3a 2

# clean up worktrees, branches and records
$ agentdc fanout clean 7f3a

--n accepts 2 to 8. The project must be a git repository with a commit . These two conditions are validated by the client with separate error messages.

The portal is the main interface; the CLI is for scripting and recovery when the portal is unavailable. Every command supports --help.

The commands below use a PowerShell session alias, because AgentDC is not added to PATH:

$ $AgentDC = "$env:LOCALAPPDATA\Programs\AgentDC\agentdc.exe"
$ Set-Alias -Name agentdc -Value $AgentDC

The alias exists only in the current PowerShell window; all agentdc … examples below call the executable at its canonical path.

Machine-readable output

$ agentdc ls --json | ConvertFrom-Json
$ agentdc status --json

ls, status, fanout list and fanout diff accept --json. An empty list returns [], never null.

One AgentDC endpoint for compatible MCP clients. Configurations for Codex, Claude Code and OpenCode are shown below; new clients use the same contract.

AgentDC must be running in its terminal for agents to connect to http://127.0.0.1:8770/mcp. MCP shares the daemon, projects, sessions and memory with the portal. It does not open another app or send an initial prompt into a session.

Codex

Add this server to ~/.codex/config.toml, then restart Codex:

[mcp_servers.agentdc]
url = "http://127.0.0.1:8770/mcp"
http_headers = { Authorization = "Bearer <TOKEN>" }
tool_timeout_sec = 1200

Claude Code

Register at user scope to make AgentDC available in every project:

$ claude mcp add --transport http --scope user agentdc http://127.0.0.1:8770/mcp --header "Authorization: Bearer <TOKEN>"
$ claude mcp get agentdc

OpenCode 1.x

Add a remote server to your active OpenCode configuration, then restart OpenCode:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agentdc": {
      "type": "remote",
      "url": "http://127.0.0.1:8770/mcp",
      "enabled": true,
      "oauth": false,
      "headers": {
        "Authorization": "Bearer <TOKEN>"
      }
    }
  }
}

Tool

The three listing tools accept cursor/limit and return next_cursor; search_memory uses before/next_before. All wire output, including text fallbacks for older MCP clients, is capped at 256 KiB and reports truncated; more projects, sessions or agents will not overflow the client's context.

MCP exposes only the controlled operations above. Project deletion, history deletion, daemon shutdown and update application still require direct user action in AgentDC.

The daemon checks for updates on startup, then every minute. A new release shows an update indicator in the portal. Click it to see release notes, download percentage and bytes transferred, verification of sha256 and installation status.

The AgentDC terminal continuously reports version checks, release notes, download milestones, verification, replacement, errors and when the new binary is ready.

Updates replace application code only. AgentDC downloads the complete new release binary, rather than appending data to the existing binary. The running file is temporarily renamed to agentdc.exe.old, and the new file takes the name agentdc.exe. The current daemon keeps running from .old, preserving its agent sessions. The next launch uses the new binary and removes .old.

The database, configuration, history and all of AGENTDC_HOME stay in place. They are not copied with the binary and are never included in downloads. Only program-file disk usage temporarily nearly doubles between installation and the next launch.

Activate the new version

Once the terminal reports installation complete, keep using your current sessions. When convenient, close the terminal and open AgentDC from its shortcut. You can also launch the canonical app from PowerShell:

$ & "$env:LOCALAPPDATA\Programs\AgentDC\agentdc.exe"

Update details are recorded in <AGENTDC_HOME>\update-apply.log; startup errors and runtime status are in <AGENTDC_HOME>\daemon.log. By default, <AGENTDC_HOME> is %LOCALAPPDATA%\agentdc.

Disable update checks

A go build self-built binary has no update channel and makes no update network requests. No update indicator is shown.

Historical release notes are shown in their original language.