AgentDC — AI coding agents, on your machine

AgentDC

Worktree Folder Agent

agentdc

main

⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏ Fix the pane divider drift on resize Claude · The ratio rounds to integer cells before the flex pass.

⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏ Stop the flicker when a pane closes Codex · 96 passed · 0 failed

⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏ OpenCode OpenCode · typecheck clean · the branch follows cwd now

feat/detach worktree

⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏ Run the e2e suite before merge Codex · e2e · 48 passed

⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏ Detach a pane into its own window Claude · Opened PR #412 · ready for review

demo-api

main

⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏ Batch the artifact uploads Claude · Migration 0042 applied · 3 tables

⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏ Rename the leaderboard export columns Codex · Renamed 6 columns · the migration is ready.

⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏ Gemini Gemini · Finished

demo-portal 1 need you

demo-tools

Claude 42% · 5hCodex 18% · 7d

agentdcmainFix the pane divider drift on resize 1 2

The ratio rounds to integer cells before the flex pass.

● Done — the tab strip no longer jumps when a chip closes.

⎿ 3 files changed · 41 tests passed

> fix the pane divider drift on resize

● I'll trace why the pane divider drifts on resize.

● Read(src/terminal/layout-engine.ts)

⎿ 312 lines

● The ratio rounds to integer cells before the flex pass — resize twice and the drift compounds.

● Update(src/terminal/layout-engine.ts)

⎿ +14 -6 · keep the fractional ratio in the tree

✳ Testing… (npm test)

❯

[Opus 5 (1M context)] ▮▮▮▯▯▯▯▯ 32% | deck git:(main*)▶▶ auto mode on (shift+tab to cycle)

96 passed · 0 failed

› add a test for the close path

codex

Added pane-lifecycle.test.ts with the close and detach cases.

✓ 94 passed · 0 failed

› trace the flicker when a pane closes

codex

The old pane's canvas paints one frame after the grid reflows. I'll defer the removal by a frame.

✓ Applied patch src/terminal/pane-lifecycle.ts

└ requestAnimationFrame before detach

✓ 96 passed · 0 failed

▌

tokens used 4.2k · model gpt-5-codex

typecheck clean · the branch follows cwd now

> where does the branch label get its value?

From the git watcher: it reads HEAD and publishes

head-changed; the status bar subscribes to it.

read src/lib/git-watch.ts

read src/ui/status-bar.tsx

> rename the git watcher's events to match the store

Renamed four events and updated both subscribers.

edit src/lib/git-watch.ts

~ head-changed → branch-changed

✓ typecheck clean

> run the store tests too

✓ 37 passed · 0 failed

> what still reads the old branch field?

Only the status bar and one test fixture.

grep branchName src/

2 matches in 2 files

> why does the status bar lose the branch after cd?

The watcher only re-reads HEAD on focus. A cwd change from OSC 7 should also trigger it.

edit src/lib/git-status.ts

+ watch cwd from osc-7 events

✓ typecheck clean · the branch follows cwd now

>

opencode · claude-sonnet-5 · 12.4k tokens

Office 3DShared officeSample data

Select a desk to view its session. In the app, task handoffs and reports follow actual events.

ZaloAccounts & settingsNot connected

↗

Choose a conversation

Conversations linked to this session appear here.

Accounts & settings

Manage Zalo connections and behavior

Zalo is not connectedNot configured · 0 active

Settings Runtime

01

Open Zalo withHidden browser ⌄

02

Message scope◉ All incoming and outgoing messages

○ Selected group chats only

03

Human timing

Minimum 2 secondsMaximum 6 seconds

General behavior rules

Periodic recall is off. These example settings are not saved and no account is connected.

MemoryDemo website / Knowledge baseSample data

System overview

Sample note · Markdown

Project knowledge, stored on your machine.

Website structure

The homepage, docs and status page share a stylesheet. Installation links point to the official release channels.

Working conventions

Read the project guide before making changes.
Record decisions so the next session can continue.
Keep private data out of release packages.

architecturewebsitedemo

SchedulesScheduled promptsNot activated

Your schedules

◷

Morning task summary

Daily · 07:30

Demo website design

Paused

This sample schedule illustrates the settings. This website does not run any jobs.

Schedule settings

NameMorning task summary

When to runDaily

Run at07:30

Target conversationDemo website design

Send results to ZaloDo not send to Zalo

Prompt

Read the README and summarize today's tasks. Report only; do not edit files.

◉ Inject prompt ○ Run in background

About background runs

Background runs leave the terminal alone, read data and respond with text. Tool restrictions depend on the agent and safety mode.

Browser BridgeLocal extensionNot connected

›_

Browser Bridge

Let AgentDC work with your signed-in Chromium browser, on this machine only.

○ Not connected Choose the extension folder in Load unpacked.

1

Load the extension once

Select the browser-bridge-extension folder prepared by AgentDC.

2

Enable it in your browser

Open Chromium's extensions page, enable Developer mode and choose Load unpacked.

3

Local transcription

The engine and model run on your machine.

Manage connection

The app lets you pause or revoke a connection. This preview does not pair with your browser.

Keep every agent in sight.

Choose a conversation

Accounts & settings

System overview

Website structure

Working conventions

Your schedules

Schedule settings

Browser Bridge

Load the extension once

Enable it in your browser

Local transcription

Watch.

One team.
Two ways to follow along.

Keep the context.
Find the right agent.

Launch.

Open an agent straight into a branch.

Every agent AgentDC knows, and the command it will type.

Keep.

Close AgentDC. Reopen it. Pick up where the agents left off.

Files, usage and session history sit beside your terminals.

Keep every agent in sight.

Choose a conversation

Accounts & settings

System overview

Website structure

Working conventions

Your schedules

Schedule settings

Browser Bridge

Load the extension once

Enable it in your browser

Local transcription

One team.Two ways to follow along.

Keep the context.Find the right agent.

Open an agent straight into a branch.

Every agent AgentDC knows, and the command it will type.

Close AgentDC. Reopen it. Pick up where the agents left off.

Files, usage and session history sit beside your terminals.

One team.
Two ways to follow along.

Keep the context.
Find the right agent.