Codex Plugin

The DevClocked Codex plugin brings your tracked coding activity into Codex. Once it is installed, you can ask Codex about your day, active session, project totals, and weekly progress without leaving your coding thread.

Plugin vs MCP Server

The Codex plugin is the native Codex experience. It can bundle DevClocked tools, instructions, and MCP access into one installable workflow. The MCP server is the portable protocol layer used by Codex, Claude Code, Cursor, and other MCP-compatible clients.

If the DevClocked plugin is available in your Codex workspace, use it. If you do not see the plugin yet, use the MCP setup guide as the fallback path.

Install in Codex

1. Open Plugins in the Codex app or run /plugins in Codex CLI.
2. Search for DevClocked.
3. Select Add to Codex or Install plugin.
4. Start a new Codex thread after installation so the plugin tools are available.

Authenticate

If Codex asks you to connect DevClocked, follow the plugin prompt. If you are using the MCP fallback, authenticate the DevClocked CLI instead:

npx -y @devclocked/cli@latest login

Paste the API key from your DevClocked dashboard (Settings > API Keys). The CLI stores credentials locally at ~/.config/devclocked/cli.json.

What You Can Ask

• "How long have I coded today?"
• "What is my active DevClocked session?"
• "Summarize my last seven days."
• "Which projects have I spent the most time on this week?"
• "Show my raw activity for today."

Tools Provided

Tool	What it does
get_summary	Formatted summary of today's coding activity
get_today_activity	Raw JSON for today's sessions, work blocks, repos, lines changed, and tokens
get_active_session	Current active tracking session, if one is running
get_weekly_summary	Concise summary for the past seven days
get_weekly_summary_raw	Raw JSON for the past seven days
get_projects	Project stats including hours, sessions, commits, and active days

MCP Fallback for Codex

Codex supports local MCP servers through config.toml. You can register DevClocked directly with the Codex CLI:

codex mcp add devclocked -- npx -y @devclocked/cli@latest mcp-server

Then start Codex and run /mcp to confirm that devclocked is connected.

Troubleshooting

Plugin not visible?

The plugin may not be shared with your Codex workspace yet. Use the MCP fallback while plugin access is being enabled.

Codex cannot call DevClocked tools?

Start a new Codex thread after installing or enabling the plugin. For MCP setup, run npx -y @devclocked/cli@latest mcp-health and check /mcp inside Codex.