Documentation Docs version: dev (Pre-release: Gitoodo has not been released yet)

For developers · Start here

Architecture

On this page
  1. The parts
  2. Data flow
  3. Secrets
  4. Configuration
  5. Where to read on

Gitoodo is a desktop app plus a command line with headless services. The forge is the ledger: issues, labels and pull requests hold the whole state, so every picture can be rebuilt from the forge. This page maps the repository; the linked references go into detail.

The parts#

PartWhereWhat it does
Corecrates/core (crate gitoodo-core)Forge adapters, settings, sync, secrets, question parsing, orchestration logic. No Tauri, testable on any host. All network access happens here.
Command linecrates/cli (binary gitoodo)Classifier and dispatcher services, worker commands (ask, worker push), satellites, the MCP server for the orchestrator chat. See the command line reference.
App shellsrc-tauri (crate gitoodo-app)Tauri 2 shell, kept thin: windows, tray, menus, autostart, commands that call into the core.
Frontendsrc/React and TypeScript with Vite: the four tabs, settings, onboarding, help center. It never talks to the network and never sees a token.
Helper cratescrates/pipe-security, crates/scoped-folderWindows named pipes only the current user can open; security-scoped folder bookmarks for the sandboxed Mac App Store build.
Website and docssite/The static landing page and these docs, built with npm run site:build.

Data flow#

  1. Sync. The core polls the configured forges (crates/core/src/sync) through one adapter per forge family in crates/core/src/forge: gitea.rs for Forgejo and Gitea, github.rs, gitlab.rs, on shared HTTP plumbing in http.rs (client, auth, error mapping, pagination); the scheduler backs off on errors and throttling.
  2. Questions. Comments and issue bodies are parsed for question blocks in the question format. Answers are posted as short comments.
  3. Orchestration. The classifier (gitoodo classifier) keeps status labels and the work queue for every repository switched on in orchestration.json. The dispatcher (gitoodo dispatcher) leases ready issues, starts one worker per issue in its own worktree, and merges finished pull requests. See the orchestrator spec and the dispatcher.
  4. App. In orchestrator mode the app reads the picture of the services over a local socket (a named pipe on Windows); in direct mode it polls the forges itself through the core.

Secrets#

Tokens live only in the system secret store (macOS Keychain, Windows Credential Manager, Secret Service), or for headless services in systemd credentials or the service environment (crates/core/src/secrets.rs, daemon reference). They never reach settings files, logs, error messages or the frontend. Workers never hold a token: gitoodo worker push and gitoodo worker pr push and open the pull request through the account connected in Gitoodo.

Configuration#

settings.json (accounts, poll interval, mode, overview labels) is shared by app and command line; orchestration.json switches repositories on and sets states, lease time, label names and the dispatcher block. Both live in the config folder listed in the daemon reference.

Where to read on#

Docs version: dev