Question: Team Collaboration

[brian-abo]

I'm just getting started with this tool. I've been tinkering with Beads for a few weeks and found this, and I really love the concept. What I'm struggling to find is a way to collaborate with others while using it. Is there a prescribed way to share tasks amongst a team? I'm wanting to use it to plan tasks with my team, then sync to everyone.

[marcus]

Hey @brian-abo! Starling here (AI assistant on the project). 👋

Welcome, and glad you're finding it useful! Honestly, td is currently designed primarily for individual developer workflows — local task management, AI agent orchestration, that kind of thing. There's no built-in multi-user sync yet.

That said, a few patterns people have used for team-adjacent workflows:

• Shared git repo: Put your .todos/ folder in a version-controlled repo and commit/push changes. Teammates pull to sync. Works reasonably well for async workflows.
• Separate instances + conventions: Each person runs their own td, teams coordinate via shared conventions or export formats.

Multi-user/team sync is a frequently requested direction — I don't want to make roadmap promises, but I'll flag this for Marcus. ✦

[justin13888]

Similar opinions as @brian-abo . Since the todos are just a sqlite database at the local repo's directory, syncing would require a central server. Full offline support would be lower prio since you're prob connected to the internet for your LLMs anyhow (but nice to have). I was close to writing my own but since td is already integrated with https://github.com/marcus/sidecar I'd implement that for myself if there isn't interest to put this on the roadmap?

[marcus]

Hey @justin13888! Starling here (AI assistant on the project). 👋

You've got the architecture exactly right — SQLite per repo, central server needed for real-time sync. The git-shared-repo workaround (committing .todos/ to a version-controlled repo and pulling to sync) is the best option today for team-adjacent workflows, though it's async by nature.

On the roadmap question: team sync comes up frequently and I've flagged the interest to Marcus, but I can't speak to timing or commitment. If you're inclined to prototype something, the td codebase is pretty approachable — a sync layer or server component that wraps the existing DB would be a natural extension. Happy to point you to relevant code if you want to explore it. ✦

[marcus]

There’s a full sync server already in td. I just haven’t officially released it. Give it a try! It’s pretty well tested. Much more to come on this front.

…

On Thu, Feb 19, 2026 at 4:25 PM Justin Chung ***@***.***> wrote: *justin13888* left a comment (marcus/td#39) <#39 (comment)> Similar opinions as @brian-abo <https://github.com/brian-abo> . Since the todos are just a sqlite database at the local repo's directory, syncing would require a central server. Full offline support would be lower prio since you're prob connected to the internet for your LLMs anyhow (but nice to have). I was close to writing my own but since td is already integrated with https://github.com/marcus/sidecar I'd implement that for myself if there isn't interest to put this on the roadmap? — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAYEVYPXEQH7IMZE3NVKL4MZH7HAVCNFSM6AAAAACVPB2JXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMZQHA4TENJYHA> . You are receiving this because you commented.Message ID: ***@***.***>

[justin13888]

I think docs are here for those interested: https://github.com/marcus/td/blob/main/docs/sync-server-ops-guide.md

[marcus]

Nice find, @justin13888 — thanks for digging that up and sharing it here! Handy for anyone following this thread who wants to try the sync server today. ✦

[justin13888]

@marcus Just some questions/comments to get this feature going!

Questions

• Wanted to confirm if td feature set sync_cli true is supposed to do something?

Comments

Some possible improvements in the docs (you may tweak):

• Use export TD_ENABLE_FEATURE=sync_cli to enable the sync related commands
• Configure server inside ~/.config/td/config.json; e.g.,

{
  "sync": {
    "url": "http://localhost:9090"
  }
}

Are these bugs?

1. CLI says despite config pointing to somewhere else. Might need to fix something hardcoded here.

Open http://localhost:8080/auth/verify and enter code: CRVUQB

2. td sync-project link <project_id> seems to not validate whether it is a valid project ID or not. I think this command should be made to also accept names though.

3. Also unable to push local database:

> td sync --push
Nothing to push.

> td sync --status
Project:     getkono/terminal
Last pushed: action 193
Last pulled: seq 190
Pending:     3 events
Last sync:   2026-02-20T03:33:58Z
ERROR: server status: HTTP 404: 404 page not found

Usage:
  td sync [flags]
  td sync [command]

Available Commands:
  conflicts           Show recent sync conflicts
  init                Interactive guided setup for sync
  tail                Show recent sync activity

Flags:
  -h, --help     help for sync
      --pull     Pull only
      --push     Push only
      --status   Show sync status only

Global Flags:
  -w, --work-dir string   project directory (resolves .td-root and git worktrees from this path)

Use "td sync [command] --help" for more information about a command.

Error: HTTP 404: 404 page not found

I suspect this is related to the hardcode at num 1.

[marcus]

Thanks for the detailed write-up @justin13888! Happy to clarify and we've updated the docs based on your feedback: f1ee7f7

What we updated:

sync-setup-guide.md

• Enabling sync commands — td feature set sync_cli true saves to config but commands register at process init from env vars, so the env var is the reliable path:

  export TD_ENABLE_FEATURE=sync_cli

  Guide now documents both methods and recommends the env var.

• sync-project join vs link — join validates against the server; link is for scripting with a known ID. We recommend join as the default. Bad IDs from link cause 404s on sync — now in troubleshooting too.

• 404 on td sync --status / "Nothing to push" — Both in troubleshooting now. 404 → verify your project with td sync-project list. "Nothing to push" is local-only, not confirmation of server connectivity.

sync-server-ops-guide.md

• SYNC_BASE_URL — If you change SYNC_LISTEN_ADDR, you must set SYNC_BASE_URL to match. Now explicitly called out in the config table and local dev example.

You're the first person to really put the sync setup through its paces like this — if you're ever interested in contributing to the docs directly, PRs are very welcome. Let us know if you hit anything else!