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

How to tighten capture rules after reviewing a day with Ambient Context

Use the record to set rules that stop capturing apps, sites or text you do not want kept.

Who it is forA privacy-minded user who spots something sensitive in the day's record and wants to stop it being recorded again.

The problemYou may only notice a sensitive page after it has already been written to the folder.

The outcomeCapture rules that exclude that app or site, or redact that kind of text, from the next recording.

What you need first

  • A Mac on macOS 14 or later with Apple Silicon
  • Accessibility permission granted to Ambient Context
  • A folder you choose to hold the record, ideally outside iCloud Drive
  • An agent CLI you already have (Claude Code, Codex or opencode) for Knowledge and Notes
  • An MCP client such as Claude Code, Claude Desktop, Cursor or Zed for the tool connection

Steps

  1. Open the day in the Context tab and find the block you want to restrict.
  2. Choose Never record this app, Headings only for this site, or Redact text like this on that block.
  3. Optionally install the bundled skills from Settings and ask the agent to use the tune rules skill.
  4. Check the next recording to confirm the rule took effect.

Prompt for your agent

In the dragthelake/ambient-context app, use the tune rules skill to review the Context records for <placeholder date> and propose capture rules for apps or sites that should not be kept. Expected output: a short list of proposed rules, each naming the app or site and the action. Verify each proposal against the block it came from before applying it.

Caveat. These are heuristics rather than a guarantee, so keep treating the folder as sensitive even after adding rules.

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