8000 feat: catch up on project work with daily digests by DominikScholz · Pull Request #1 · DominikScholz/dscode · GitHub
[go: up one dir, main page]

Skip to content

feat: catch up on project work with daily digests - #1

Draft
DominikScholz wants to merge 11 commits into
mainfrom
feat/html-render-prompt-links
Draft

DominikScholz wants to merge 11 commits into
mainfrom
feat/html-render-prompt-links

Conversation

@DominikScholz
Copy link
Copy Markdown
Owner

Problem

After time away, catching up means opening threads and checking git history project by project. Daily digests bring the results, blockers, screenshots, and useful next steps together in one page per changed project.

Change

Enable them in Settings → Daily Digest, choose the delay, model, and instructions, or use Run now. The selected environment writes local digests after every device disconnects and checks connected remote environments when you return. Investigation stays read-only, and remote work stays on its source machine.

The page leads with the summary and visuals, followed by What happened and What's next, then expandable repository counts and the same thread rows used in the sidebar. Project icons tint the page's lighting. Follow-up cards start a thread in the correct project; rendered HTML pages can use the same prompt links. Saved snapshots let existing digests pick up the current layout.

Scope and approval

Prepared at the repository owner's request for DominikScholz/dscode. The scope is generating project digests and acting on their follow-ups; prompt links, provider tool handling, and shared project identity support that workflow.

Verification

vp run check:changed passes: 883 tests across 35 files, affected-package typechecks, formatting, lint, unused-code checks, and generated GraphQL checks. The tests cover digest windows and away-state transitions, local and remote digest planning, page publishing and snapshots, source-project links, and dashboard digest selection.

The page layout and interactions target web and desktop; mobile retains the HTML page fallback and links to remote screenshots in their source threads. A new real digest has not been generated with the latest writing rules, and native mobile and packaged desktop were not checked in this preparation pass.

Recording (16 seconds; upload copy resized to 1920px wide):

daily-digest-recording-20261027-github.mp4
Earlier digest iteration and final layout

Earlier digest iteration before the redesign (user-provided crop; not the base branch):

Earlier digest iteration

Final hero and mood line:

Final digest hero

Final workstreams, next steps, stats, and thread rows:

Final digest layout

Implemented with Claude Opus 5.5 in Claude Code. PR prepared with GPT-6.1 Sol in Codex.

DominikScholz and others added 11 commits October 25, 2026 23:55
Clicking a prompt link card inside an html_render page now opens the new
thread in-app and sends the prompt, instead of opening a browser. With no
repo in the link, the thread starts in the rendered page's own project.

Only in-app clicks set the router history state that triggers the send, so
pasted, browser, and OS links keep the read-before-send draft. Prompts with
hidden characters also fall back to the draft. The html_render tool
description tells agents about the link format.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After every device has been disconnected from an environment for a set time
(8 hours by default), the server starts one digest thread for each project
with thread activity or new local-branch commits since its last digest. An
agent reads those threads and the git history and publishes one bento-style
page: a verdict, what needs the reader, what moved, risks, and ranked next
moves as prompt links. Settings > Daily Digest turns it on per environment
and sets the delay, model, and instructions; Run now starts digests at once.

Digest threads are marked on thread.create and in the shell. Opening one
collapses the sidebar and lays the thread out at full width, and the
dashboard links each project's newest digest with an unread dot. Hosted
thread links in rendered pages now open the thread in-app.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The digest agent no longer writes HTML. It reads the threads and git history,
then calls digest_publish with structured content (headline, summary, facts,
workstreams, decisions, next steps). The server checks the thread is a digest,
works out the window, counts commits per slot from git, builds the thread and
prompt links, escapes the text, and renders one fixed sectioned page: a pill
title with the project and date, a headline panel with an activity chart, What
happened, and How to proceed. Schema limits keep the copy short.

The tool's result counts as an HTML render everywhere a page is detected.
Digest threads also drop the thread details card, keep the composer at its
normal width, and widen only the page row.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…epth

The digest page now opens with a title row (project tile, name, commit chip,
date), a summary panel with a mood pill and the headline beside a commits
chart with gridlines and axis labels, then a numbers strip, a workstream table
under What happened, and decisions beside ranked next steps under How to
proceed.

Cards get gradient surfaces, top-lit borders, inner highlights, soft shadows,
and grain; controls are raised; the chart line glows over an area fill.
Status colors are muted toward the text color and problems read in amber.
The page background is transparent so it sits on the chat surface.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Digest threads hide the server-written prompt. The page now opens with a
screenshot or a bars comparison from the threads, demotes the commit chart
to a strip sparkline, and always links the main threads active in the window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each published digest keeps a snapshot of its content, context, and images
beside the page, and the asset route renders it with the current template,
so design changes reach old digests. The page drops gradients and borders
for flat surfaces and controls, shows the project's icon, and digest
threads open on the page alone without the worked-time row.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Add commit, file, branch, and thread details to digest pages
- Render digests from shared snapshots with project identity and provider marks
- Digest page: main card beside the lead screenshot, compact charts,
  What happened and What's next side by side, an activity strip whose
  counts open their lists, and threads drawn with the sidebar's own row
- Digest copy asks for less: shorter headline and summary, at most four
  workstreams, two decisions, and three next steps
- Digests for projects on other machines through their T3 tools
- New-thread links can name a project by environment and project id

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Align digest prompts and schema descriptions with the page layout and copy limits
- Clarify screenshot and chart guidance

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0