Skip to content

Printed morning newspaper from your notes

Every night a routine picks the next unprinted note from a folder and writes it up as a two page newspaper issue. A build step lays it out and checks every page, and a small board on your Wi-Fi prints it at the time you chose.

PersonalWorks with Claude Code · Claude Desktop with MCPCommunity example
Build your promptSee requirements

What it does

  • Picks the next unprinted note and writes the issue in the voice of your style file, without browsing the web
  • Builds it once to make sure it fits, then pushes it to the repo
  • Lays out and checks each page in CI: lines inside columns, at most four pages, every character present
  • Holds the job until print time, then streams it to your printer and logs it as printed
  • Optionally adds pages of new AI papers and tools, with each number checked against its source

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Switching the nightly routine from dry run to live after you have read a draft

You decide what happens next.

More about this workflow

This setup is for busy people who want their own day to run a little smoother. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it picks the next unprinted note and writes the issue in the voice of your style file, without browsing the web. Next, it builds it once to make sure it fits, then pushes it to the repo. Then it lays out and checks each page in CI: lines inside columns, at most four pages, every character present. After that, it holds the job until print time, then streams it to your printer and logs it as printed. Finally, it optionally adds pages of new AI papers and tools, with each number checked against its source. It works with your notes app, git host and CI, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before switching the nightly routine from dry run to live after you have read a draft, and says plainly if a step cannot be undone.

“The writer does not browse the web.”
ierolsen ierolsen on GitHub · Oct 23, 2026
Before you startNotes app · Git host accessScoped permissionsClaude Code or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • Notion

    Handles the notes app part of this job. Grant only the pages it needs, read first.

    API required: Yes. Needs a Notion integration. You choose which pages it can see by sharing them with it.

    Sign up: Notion

  • GitHub

    Handles the git host and ci part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

    Sign up: Create a GitHub account

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Fast and careful with your inbox and calendar.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Haiku 5.5

Cheapest Claude option for daily sorting.

From $0.10 per million input tokens and from $0.50 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

and timezone

who the reader is and the voice

network printer that accepts IPP

2Your prompt

4 of 4 still empty
Fill these in before you run it: [NOTES FOLDER] [PRINT TIME: and timezone] [STYLE: who the reader is and the voice] [PRINTER: network printer that accepts IPP] You are the Printed morning newspaper from your notes agent. Every night a routine picks the next unprinted note from a folder and writes it up as a two page newspaper issue. A build step lays it out and checks every page, and a small board on your Wi-Fi prints it at the time you chose. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Picks the next unprinted note and writes the issue in the voice of your style file, without browsing the web - Builds it once to make sure it fits, then pushes it to the repo - Lays out and checks each page in CI: lines inside columns, at most four pages, every character present - Holds the job until print time, then streams it to your printer and logs it as printed - Optionally adds pages of new AI papers and tools, with each number checked against its source What you must never do without a yes from a person: - Switching the nightly routine from dry run to live after you have read a draft Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Claude Desktop with MCP

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Notion with its own login, not yours. Grant only the pages it needs, read first.
  2. 2Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access24 / 30

Writes drafts and notes inside your tools, nothing leaves on its own.

Human approval27 / 30

Waits for a yes on: switching the nightly routine from dry run to live after you have read a draft.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Human approval: Add a second named stop next to "switching the nightly routine from dry run to live after you have read a draft", so every step that leaves your hands waits for a yes, and have the confirm say plainly what cannot be undone +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 84.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Printed morning newspaper from your notes](https://trustcase.dev/badge/printed-morning-newspaper-from-your-notes.svg)](https://trustcase.dev/use-cases/printed-morning-newspaper-from-your-notes)
HTML
<a href="https://trustcase.dev/use-cases/printed-morning-newspaper-from-your-notes"><img src="https://trustcase.dev/badge/printed-morning-newspaper-from-your-notes.svg" alt="Trustcase trust score for Printed morning newspaper from your notes" height="20"></a>

More personal workflows

  • Morning plate with one next step

    You hand it a brain dump, your inbox, your calendar, the projects you never finished and one word for how your brain showed up today. It hands back a shorter list: what it is taking off you, one to three things to keep, what to let go with a revive date, and a single ten minute next step.

  • Inbox sorter

    Clears the noise so you only see email that needs you.

  • Calendar guard

    Protects focus time and catches double bookings.

  • Travel planner

    Puts together trip options that fit your rules.

Other workflows that use the same tools

  • Evidence first support replies

    Support. Works the support queue a couple of times a day, checking bug reports against the code before drafting a reply. The owner reviews every reply before it goes out.

  • Morning ticket dashboard with tick to approve queue

    Engineering. Every morning an agent refreshes a one screen dashboard in your notes from the issue tracker, your workstream notes and inbox. It reads only, proposes board changes as checkboxes and drafts first pass PR reviews that are never posted.

  • Lead research brief

    Sales. Turns a new inbound lead into a one page brief before your first call.