Coding Agents

Daylee integrates with AI coding agents (Claude Code, Cursor, Codex, and any other MCP-capable client) so the assistant you already use to write code can push standup updates on your behalf.

How It Works

Daylee exposes a Model Context Protocol (MCP) server. Once you’ve linked your machine to your Slack user and pointed your coding agent at the MCP server, the agent has access to three Daylee tools and can summarise your session and submit it as a standup update at your request.

Tool

Purpose

mcp__daylee__get_last_update

Returns the timestamp of your most recent submission

mcp__daylee__get_standup_window

Returns the active standup window(s) for your team(s)

mcp__daylee__submit_update

Submits a standup update on your behalf

You decide when to push. The agent never sends updates without you asking.

Enabling the Integration (Admins)

Who can do this: Daylee admins

The coding-agent integration is workspace-scoped — a Daylee admin must enable it before users can connect their devices. Reach out to support if it isn’t enabled on your workspace yet.

Linking Your Device

Each team member installs a small CLI and links their machine to their Slack user. The link is per-device — link your laptop separately from your desktop.

  1. Install the CLI:

    pipx install daylee

  2. Run daylee login. The CLI prints a 6-character code.

  3. Paste the code into Slack: /daylee link <code>.

  4. The CLI confirms the link and writes credentials to ~/.config/daylee/credentials.json.

If the link times out, run daylee login again to get a fresh code.

Connecting Your Coding Agent

Run daylee connect to print the MCP config snippet for your agent. By default it prints snippets for all supported agents; use --agent claude-code|cursor|codex to scope the output.

Claude Code

daylee connect --agent claude-code

Add the printed daylee entry under mcpServers in ~/.claude.json (user-level) or a project-local .mcp.json.

Cursor

daylee connect --agent cursor

Add the printed daylee entry under mcpServers in ~/.cursor/mcp.json.

Codex CLI

daylee connect --agent codex

Append the printed TOML to ~/.codex/config.toml.

Other MCP-Capable Agents

Any agent that speaks streamable-HTTP MCP works. Use the JSON snippet from daylee connect --agent claude-code as a template and adapt the keys to match your agent’s MCP config format.

Pushing an Update

Claude Code

Daylee ships a Claude Code plugin that adds a /daylee slash command. Install it from the plugin marketplace:

/plugin marketplace add keppler-tech/daylee.cli
/plugin install daylee

Then in any Claude Code session, run:

/daylee update

update is the default action, so /daylee on its own does the same thing.

If you prefer not to use the marketplace, you can install the command file manually:

mkdir -p ~/.claude/commands
curl -sL -o ~/.claude/commands/daylee.md \
  https://raw.githubusercontent.com/keppler-tech/daylee.cli/master/plugin/commands/daylee.md

Claude will:

  1. Ask Daylee for the last push timestamp and your team’s standup window.

  2. Read git log / git status since that timestamp.

  3. Combine that with what it knows from the conversation into a 3–6 bullet summary.

  4. Show you the proposed summary and wait for your approval.

  5. Push it to Daylee.

Cursor, Codex, and Others

Those agents don’t have first-class slash commands like Claude Code, but you can trigger the same flow by asking the agent in plain language:

“Push my Daylee update.”

The agent will use the same MCP tools.

What Gets Sent

Only the final summary you’ve approved, plus structured metadata:

  • Time window the summary covers

  • Source agent (so reports can attribute “via Claude Code” / “via Cursor”)

  • Optional: list of repos / branches / files touched during the session

What is never sent: your raw prompts, the agent’s reasoning, tool outputs, or file contents. Summarisation happens entirely on your machine.

Status and Troubleshooting

daylee status

Shows which server you’re pointed at, your linked Slack user, and the device id.

Common issues:

  • “Not linked yet” when running daylee connect - run daylee login first.

  • Agent says it can’t find Daylee tools - your MCP config snippet wasn’t picked up. Restart the agent after editing config files, or check that the daylee server entry is under the right key (mcpServers for Claude Code/Cursor, mcp_servers for Codex).

  • Submit fails with 401/403 - your device token may have been revoked. Re-run daylee login.

  • get_standup_window returns an empty teams list - you’re linked, but you’re not on a Daylee team in this workspace yet. Asking an admin to add you fixes it; the update will still be stored and shown in your next team’s report once you’re added.

Privacy

The CLI stores credentials at ~/.config/daylee/credentials.json (mode 0o600). The MCP traffic uses HTTPS bearer tokens.

Activity ingested through this integration appears in standup reports the same way GitHub / JIRA / Linear activity does — see Integrations.