DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to read what your agents did overnight in one brief with Bloks

Get a morning summary of agent work, pending approvals and daily cost, with links to each source.

Who it is forA person who runs several agents in the background and wants a quick start to the day without opening each conversation.

The problemAgents work while you are away, and finding out what they did and what is waiting on you means opening every conversation.

The outcomeEach morning Bloks writes a brief from what is on disk, where every line links to its source, and approvals can be answered from it.

What you need first

  • The Bloks desktop app installed on your machine
  • At least one provider you can use: a Claude Code, Codex or Gemini CLI you already signed in to, or an API key for a chat engine
  • A project folder or files the agent is allowed to work in
  • For the iPhone steps: the Bloks iPhone app and a six digit pairing code from your Mac

Steps

  1. Open Settings and check the time the morning brief runs; the default is 08:00.
  2. Set up one or more agents with routines or check-ins so there is work to report.
  3. Open the morning brief when it appears and read what each agent did while you were away.
  4. Answer any approval listed in the brief directly from it.
  5. Use Play to hear each agent give its own part of the brief, or follow a line link to its source.

Prompt for your agent

Using the Bloks repo at hamedgitty/bloks, enable the morning brief and run one routine for the agent <agent-name>. Expected output: a morning brief listing what <agent-name> did, what is waiting on you and the day's cost, with a link for each line. Verify that each line links to a real conversation or file.

Caveat. The brief is built from what is already on disk rather than by a model, so it only reports what the agents already recorded.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page