Skip to content
wey-guPublic

About

A personal AI you run yourself: talk to one partner; it hands the work to AI agents like Claude Code and Codex on your own machines and comes back when it's done, with proof.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

32 stars

Watchers

0 watching

Forks

Ducter

Say it once. Hear back when it's done.
An open-source personal AI on your own Mac or server. You talk to one partner; it runs the work on Claude Code, Codex, pi or DeepSeek Harness with the plans you already pay for, and speaks up only when something is done or needs you.

CI License: Apache-2.0

ducter.ai · Getting started · Docs

Ducter on a Mac and a phone. On the Mac, the conversation: you asked it to fix the flaky compaction test in HawDB; it says it's fixed, with Merge into main and its proof (50 of 50 runs pass, 412 workspace tests pass, a two-file diff). Below, a question with a default: rebase fix-ci, with Reply, Hold and Rebase. The same question is open on the phone.

Why Ducter

  • One partner, not a wall of sessions. You write "Fix the flaky compaction test in HawDB and tell me when it's done." Your partner starts the task, watches it, and comes back with the result, its proof and Merge into main. You can open any task and steer it yourself.
  • Your agents, your subscriptions. Tasks run on Claude Code, Codex, pi or DeepSeek Harness, signed in as you, with your own skills and settings. No Ducter account, no API key to start.
  • Your computers. It lives on your Mac, or on a Linux server you own, at home or in the cloud, so it keeps working while your laptop sleeps. Lend it more computers to run tasks on.
  • Quiet until it matters. Done comes with proof, a question comes with a default it will take if you don't answer, and on a quiet day you hear nothing. Reply to a task's result and that task carries on.
  • Open source and self-hosted. Hosted agent workbenches come and go, and the best personal AIs are closed. Ducter is Apache 2.0 and runs where you put it, so nobody can wind it down for you (why it exists).
  • Ready the first time. One line installs it; it sets up what's missing and greets you with things to start from your own folders and accounts.

Where you use it

Mac The desktop app, Apple silicon. Ducter can live here and run tasks here.
Linux server x64 or arm64, at home or in the cloud. Runs as a service and stays on.
iPhone and iPad One app, in public beta on TestFlight. On a wide iPad, On hand stands beside the conversation.
Android The Ducter app, from each GitHub release; it updates itself, and a foldable opened like a book shows the conversation and On hand on either side of the fold. Or your phone's browser.
Terminal The ducter command, on the Mac or the server.

Away from home, a phone reaches Ducter in one of three ways: over your Tailscale network, at a server's own domain, or at a Mac at home set up From outside with your domain on Cloudflare (Your phone).

Get Ducter

You need Claude Code or Codex signed in with your own account; if neither is there, the Mac app installs one and walks you through signing in.

On a Mac (Apple silicon), paste this into Terminal. It installs the signed app and the ducter command, and opens it:

curl -fsSL https://ducter.ai/install.sh | sh

Or download the .dmg from the latest release.

On a server, run it as a service, then give it your domain (HTTPS, and a code for your Mac and phone):

curl -fsSL https://ducter.ai/install.sh | sh -s -- --service
ducter domain ducter.example.com

On iPhone or iPad, join the TestFlight beta and connect with the address and code from ducter pair.

With your AI agent: ask it to "Install the ducter-deploy skill from github.com/wey-gu/ducter/tree/main/skills and deploy Ducter on my server." (For AI agents)

Building from source, the walkthroughs and every command: Install and Getting started.

What it looks like

On hand: tasks in four lanes, Needs you, Working, Waiting and Done today, the open decision in its card, and two routines on the shelf below with their next runs An opened task: its outcome as the headline with Merge into main, what it did step by step, and the diff of one of the two files it changed
On hand. Every task, what's waiting for you, and your routines. An opened task. The outcome first, then what it did and its changes.
Your devices: this Mac as a clay island with Ducter, Claude Code and Codex on it, and what it can do around it Partner: the AI agents on this Mac, what Ducter thinks with (Claude Code, Opus), and who does the tasks
Your devices. The computers Ducter works on, and what each one can do. Partner. What it thinks with, and who does the tasks.

What you can hand it

  • Coding work. Each task gets its own git worktree and ducter/… branch; merging is your call.
  • Reviews and write-ups. "Review this week's open PRs." "Write the v0.4 release notes."
  • Things that take time. Wait for a CI run, keep trying until the tests pass, or run every Monday at 9 (Waiting and routines).
  • The web. It browses in its own Chrome; watch it from your phone and take a turn when a page needs you (Your devices).
  • Your Mac's apps, and a phone of its own. With Use the computer on a Mac, a task exports the Keynote deck or answers the mail in that Mac's apps, in the background, with Stop in reach; password managers, banks and System Settings stay out of reach. Use a phone gives it an Android phone of its own, running on a Mac with Apple silicon, for apps that live only on a phone. Anything that sends, pays or deletes waits for your Go (Your devices).
  • Errands. Book and buy with your saved sign-ins and cards, filled in without being seen, and every payment waits for your OK (Autofill). A task that needs a key (a deploy key, an API key) asks you with a card, never in the chat, and the key stays on your own computer. Calls through Tuwa, after you tap Call (Phone calls; needs a Tuwa account).
  • Your mail and calendar. Say yes once, and it tells you only what needs you: a first look over the last two weeks, then a morning message with at most three things, and right away only when waiting would cost you (Accounts it can read).
  • Where you already chat. Talk to the same partner from Telegram or Slack through a bot of your own, or from Messages on your iPhone through your Mac (Chat apps, iMessage).
  • What you did before. Find any earlier task by what it did or what you said, star it, and carry on with it; pause and resume what runs on its own (Past tasks).
  • What you already decided. With Nowledge Mem (optional), your partner and its tasks share one memory with the AI tools you use elsewhere.

Early preview. Expect rough edges and breaking changes. See the changelog.

Under the hood

For people who already run several agents at once, what makes them hold up as one partner:

  • One adapter for four agents, through OAR: clean sessions that still carry your own skills and settings, and a partner that can only read and decide on every one of them (enforced, not asked).
  • Small windows on purpose. About 200K tokens per session; a long conversation stays coherent through digests and recall (memory, context).
  • One registry of facts per agent (harness-facts.ts, readable twin): windows, compaction points and verified versions, which ducter doctor checks against what you have installed.
  • Budgets are tests. Prompt and tool-list sizes fail the build when they grow, and a partner change carries a fresh eval result.
flowchart LR
  you(["You<br/>Mac, iPhone, iPad, browser, terminal"]) <-->|one connection| partner
  subgraph main["Ducter, on your Mac or your server"]
    partner["Your partner"]
    log[("The Log<br/>local SQLite")]
    partner <--> log
  end
  partner -->|task| t1["Claude Code, Codex, pi, DeepSeek Harness<br/>own worktree and branch, here or on a computer you lend it"]
  partner <-.->|memory, optional| mem[("Nowledge Mem")]
Loading

Privacy and safety

Nothing lands without you: Ducter never merges, never works in your own checkout, never sees your passwords, and never pays, sends or calls without your OK. In your Mac's apps it never opens a password manager, a bank or System Settings. Your work reaches an AI provider only through your own agent's login or key. A server listens on itself only, and each phone or computer connects with a one-time code. Details: Privacy and safety.

Docs and contributing

Ducter is made by the people behind Nowledge Mem. Once a pull request of yours is merged, mention it and we'll send you a free lifetime Nowledge Mem license (details).

License

Apache License 2.0

About

A personal AI you run yourself: talk to one partner; it hands the work to AI agents like Claude Code and Codex on your own machines and comes back when it's done, with proof.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

32 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages