Track deep work sessions locally (start/stop/status) and generate a GitHub-contribution-graph style minutes-per-day heatmap for sharing (e.g., via Telegram). Use when the user says things like “start deep work”, “stop deep work”, “am I in a session?”, “show my deep work graph”, or asks to review deep work history.
Use the local deepwork app (SQLite-backed) at ~/clawd/deepwork/deepwork.js.
If ~/clawd/deepwork/deepwork.js does not exist, bootstrap it from the public repo:
mkdir -p ~/clawd
cd ~/clawd
# Clone if missing
[ -d ~/clawd/deepwork-tracker/.git ] || git clone https://github.com/adunne09/deepwork-tracker.git ~/clawd/deepwork-tracker
# Ensure expected runtime path exists
mkdir -p ~/clawd/deepwork
cp -f ~/clawd/deepwork-tracker/app/deepwork.js ~/clawd/deepwork/deepwork.js
chmod +x ~/clawd/deepwork/deepwork.js
(Do not fail the user request if clone/copy fails—still attempt other steps and report what’s missing.)
Run via exec:
~/clawd/deepwork/deepwork.js start --target-min 60~/clawd/deepwork/deepwork.js stop~/clawd/deepwork/deepwork.js status~/clawd/deepwork/deepwork.js report --days 7 --format text~/clawd/deepwork/deepwork.js report --days 7 --format telegram~/clawd/deepwork/deepwork.js report --mode heatmap --weeks 52 --format telegram~/clawd/deepwork/deepwork.js start --target-min 60 (or another target if the user specifies it).~/clawd/deepwork/deepwork.js stop.~/clawd/deepwork/deepwork.js report --days 7 --format telegram.8551040296) using the message tool with a Markdown monospace code block.If the user wants different ranges, support --days 7|14|30|60.
(Heatmap is still available via --mode heatmap --weeks ... when explicitly requested.)