DevDay – End-of-day recap for AI coding sessions

Name: DevDay – End-of-day recap for AI coding sessions
Availability: InStock
Author: ujjwaljainnn

by ujjwaljainnn·Feb 14, 2026·3 points·1 comment

Visit Project View on HN

AI Analysis

●MidSolve My Problem

Aggregates AI coding session logs, but "multi-tool dashboard" already solved by Cursor+Claude integrations.

Strengths

•Cross-tool session aggregation is useful if you actually juggle three AI editors daily.
•Local-first with optional LLM summaries keeps data private by default.
•Git correlation provides context; standup format generates ready-to-paste reports.

Weaknesses

•Target audience is narrow: only people using 2+ of these three specific tools simultaneously.
•Cursor itself is designed to absorb Claude Code and OpenCode workflows—feature creep, not moat.

Post Description

I built devday because I use multiple AI coding tools (OpenCode, Claude Code, Cursor) and wanted a single command to see what I actually accomplished each day. It reads local session data, cross-references with git commits, and optionally generates standup-ready summaries via OpenAI or Anthropic.

Everything runs locally — no data leaves your machine unless you opt into LLM summaries.

Install with npm install -g devday.

Currently supports OpenCode, Claude Code, and Cursor on macOS. Would love feedback on what other tools to support.

Similar Projects

Developer Tools●●Solid

DevDay – End-of-day recap for AI coding sessions

It actually pulls session files from OpenCode, Claude Code and Cursor, shows tokens/cost/duration, groups sessions by project and lines up git commits — neat, concrete data instead of fuzzy memories. Optional first-person standups via Concentrate/OpenAI/Anthropic are a useful add, and the local-first design (no network unless you opt in) feels thoughtful; main limit is platform/tool coverage today, so it's most valuable to people already using those specific AI editors.

Niche GemSolve My Problem

ujjwaljainnn

103mo ago

Productivity●●Solid