Install Tasktrace for Claude and Codex

Claude custom connector

1. Open Settings, then Connectors in Claude Desktop or claude.ai.
2. Choose Add custom connector.
3. Name it Tasktrace and use this remote MCP URL:

https://tasktrace.dev/mcp

Claude opens the Tasktrace OAuth flow. Sign in with Google, approve the requested work log scopes, then call get_daily_context to confirm the connector is active.

Claude Code

claude mcp add --transport http tasktrace https://tasktrace.dev/mcp
claude mcp login tasktrace

Codex config

Add Tasktrace to ~/.codex/config.toml:

[mcp_servers.tasktrace]
url = "https://tasktrace.dev/mcp"

Codex uses the same OAuth discovery, Google sign-in, consent, access token, and refresh token flow as Claude.

Codex plugin

This repository includes a Codex plugin package at plugins/tasktrace and a repo-local marketplace at .agents/plugins/marketplace.json. The plugin points Codex at the production Tasktrace MCP endpoint and includes standing instructions for work logging.

codex plugin marketplace add .
codex plugin add tasktrace@tasktrace

Tools

• get_daily_context, list_tasks, list_traces, and summarize_day are read-only.
• set_current_project, create_task, update_task, create_trace, and update_trace write to your private Tasktrace workspace.

Recommended agent instruction

Use Tasktrace automatically throughout the session.
At session start, call get_daily_context.
When the project is clear, call set_current_project.
Use create_task/update_task for real units of work.
Use create_trace for meaningful progress, decisions, blockers, debugging findings, and next steps.
Do not log trivial file reads, routine commands, or minor observations.
At session end, call summarize_day. If a persistent summary is useful, save it with create_trace using type summary.

Review access

Reviewers can sign in with their own Google account and redeem a review code at /review to populate a sample workspace. This keeps Google OAuth enabled without sharing a Google password.