The 30-second pitch

You write code. DevTrack handles the rest.

A background daemon watches your commits and infers everything around them — which ticket you're on (from the branch name), what you did today, what the standup should say. It drafts the ticket comment and the EOD report in your writing voice, learned from your own git history. Your only obligation: name branches with ticket IDs.

Nothing is sent behind your back. Every outbound action — a Jira comment, a ticket transition, an email — is staged in a review queue first. You approve it, or you let it earn auto-approve over time. The daemon never prompts you, never blocks a commit, and never interrupts.

And it's the memory your AI agents lack

Available since v3.1.0: Phase 9 onboarding and the local, read-only MCP server ship in the latest public release, v3.1.1. Five native MCPB bundles are available for Windows, macOS, and Linux.

Coding agents are session-based: they exist while invoked, then forget. DevTrack is always on. One command —

devtrack mcp setup

— and Claude Code knows your active ticket, today's commits, your pending queue, and how you write. Nothing else runs at 6pm, groups the day's commits by ticket, and has the EOD ready before you ask.

Trust

Local Ollama by default; SQLite on disk. The default daily path stays on your machine. If you configure a PM system, email/chat delivery, an external server, or a cloud LLM, DevTrack sends only the payload needed for that enabled operation. Anonymous usage telemetry is opt-in and off unless you run devtrack telemetry on.

Ten-minute quickstart

The latest public release is v3.1.1. Download the matching platform asset from GitHub Releases, or build from source:

git clone --branch main --single-branch https://github.com/sraj0501/Devtrack_.git
cd Devtrack_/devtrack_client
go build -o devtrack .
sudo install -m 0755 devtrack /usr/local/bin/devtrack

Verify that this is an MCP-capable build, then run setup from the Git repository you want DevTrack to watch. Choose none when asked for a PM integration if you only want to try the local path. Managed mode requires a PostgreSQL URL for the Python service; Ollama remains the default LLM and can finish preparing in the background.

devtrack mcp status           # must report six registered tools
cd /path/to/the/repo/to/watch
devtrack setup

Minute 2: local context, no Python or model required

The Go binary and local SQLite database are ready as soon as setup finishes. Wire the current repository into Claude Code, then exercise the same MCP server locally:

devtrack mcp setup
devtrack mcp test

Reload Claude Code after mcp setup. Its DevTrack tools can now read the active ticket, today's commits, pending actions, voice profile, ticket context, and a template EOD summary. The MCP server runs on demand over stdio; it does not need a background Python process.

Minutes 3–10: start the silent worker

devtrack start
devtrack status
devtrack doctor

status and doctor report background Python, PostgreSQL, and LLM readiness without blocking Git monitoring or MCP. Once the AI server reports ready, create a normal ticket-named branch and commit:

git switch -c feature/AUTH-42-refresh-token
git commit -m "fix auth redirect"

devtrack logs                # confirm the commit and ticket were detected
devtrack queue               # review local pending actions and confidence
devtrack eod                 # generate a narrative; stages it before any delivery

Do not run queue approve while evaluating the no-send path. With the workspace PM integration set to none and no --email argument, the walkthrough uses no PM credentials and has no external destination. For a disposable, recorder-friendly version that verifies actual log output instead of using a canned transcript, see the demo storyboard.

What is ready when?

The Python service and model preparation are background work. If they are not ready by minute ten, keep coding and check devtrack doctor; the Go-native path remains usable and commits are not blocked.

Update an existing installation

devtrack upgrade

devtrack upgrade installs the latest public release, including the Phase 9 onboarding and MCP commands introduced in v3.1.0.

The daemon mines enabled local repositories in Managed mode and builds the voice profile once the local AI server is reachable. devtrack status and devtrack doctor show the persistent result and suggest devtrack work report when the profile is ready.

Setup also checks Ollama's local model inventory. An existing generation model is used immediately without another pull. If no usable local model is ready and an OpenAI or Anthropic key is already in the environment, setup offers that key as a temporary fallback while Ollama downloads; Ollama stays primary and automatically takes over when the local model becomes available.

Updating? Run devtrack upgrade to download and install the latest binary automatically (fetched from GitHub Releases; supports Linux/macOS and Windows). If the binary is in a root-owned location (e.g. /usr/local/bin), run sudo devtrack upgrade instead. On Windows, re-run as Administrator if a permission error occurs. Versioned migrations are applied automatically and the daemon is restarted after a successful upgrade.

devtrack setup writes a complete environment file under the DevTrack XDG data directory and registers it in ~/.devtrack/devtrack.conf. Visible runtime defaults are editable; valid shell, CI, and secret-manager overrides still take precedence.

Full walkthrough and guides: devtrack.cloud

Moving to a new machine?

Project memory and agent logs are committed to the repo (.claude/memory/, Data/agent_logs/). After cloning, wire up Claude Code's memory system with one command:

# Replace <path-key> with the absolute repo path, slashes replaced by hyphens
# e.g. repo at /home/sraj/devtrack → -home-sraj-devtrack
mkdir -p ~/.claude/projects/<path-key>/
ln -s $(pwd)/.claude/memory ~/.claude/projects/<path-key>/memory

Claude Code will then read and write memory directly to the repo, keeping it in sync with git.

The core loop

The daemon is silent. It does not prompt, block, or interrupt — it observes and stages.

You:  git checkout -b feat/AUTH-42-refresh-token
You:  git commit -m "fix auth redirect"
                │
                ▼
        DevTrack observes (background — you are not interrupted)
                │
        ├── infers ticket AUTH-42 from the branch name
        ├── drafts a ticket comment in your voice
        └── STAGES it — nothing is sent yet
                │
                ▼
        devtrack queue        # review what's waiting
        devtrack queue approve <id>
                │
        At 6pm: today's commits, grouped by ticket
                ▼
        devtrack eod          # the standup, already written

Review the queue whenever you like — it waits for you:

devtrack queue                  # what DevTrack wants to send
devtrack queue approve <id>     # send it
devtrack queue reject <id>      # discard it
devtrack eod                    # preview today's EOD report

Optional: AI-enhanced commits

Separately, devtrack git commit is an interactive wrapper that refines your commit message with AI, offers a ticket picker, and can log time. It is opt-in and never part of the silent daemon path:

eval "$(devtrack shell-init)"    # add to ~/.zshrc or ~/.bashrc — done once
devtrack enable-git              # opt this repo in

After that, git commit routes through DevTrack for monitored repos. Everything else (git push, git pull, git status) goes straight to real git, unmodified. Escape hatch: GIT_NO_DEVTRACK=1 git commit -m "skip".

AI commit enhancement is only active when the daemon is running. If you stop it, git commit passes through with zero delay and no errors.

What it connects to