keep-up-with 0.1.0__tar.gz

keep_up_with-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,40 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+env:
+  UV_FROZEN: "1"
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.13"
+          enable-cache: true
+
+      - name: Sync dependencies
+        run: uv sync --frozen
+
+      - name: Compile package
+        run: uv run python -m compileall -q src
+
+      - name: Check CLI entry points
+        run: |
+          uv run kup --help
+          uv run kup-cli --help
+
+      - name: Build distributions
+        run: uv build

keep_up_with-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,37 @@
+name: Publish
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/keep-up-with
+    permissions:
+      contents: read
+      id-token: write
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.13"
+          enable-cache: true
+
+      - name: Sync dependencies
+        run: uv sync --frozen
+
+      - name: Build distributions
+        run: uv build
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

keep_up_with-0.1.0/.gitignore

@@ -0,0 +1,13 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+
+# Evals
+evals/runs/

keep_up_with-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Wis Kojohnjaratkul
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

keep_up_with-0.1.0/PKG-INFO

@@ -0,0 +1,146 @@
+Metadata-Version: 2.4
+Name: keep-up-with
+Version: 0.1.0
+Summary: Turn Codex into your personal 24/7 assistant for staying on top of the latest developments.
+Project-URL: Homepage, https://github.com/wiskojo/keep-up-with
+Project-URL: Repository, https://github.com/wiskojo/keep-up-with
+Project-URL: Issues, https://github.com/wiskojo/keep-up-with/issues
+Author: Wis Kojohnjaratkul
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.13
+Requires-Dist: browser-history>=0.5.0
+Requires-Dist: discord-py>=2.7.1
+Requires-Dist: httpx>=0.28.1
+Requires-Dist: isodate>=0.7.2
+Requires-Dist: markitdown[pdf]>=0.1.6
+Requires-Dist: pillow>=12.2.0
+Requires-Dist: praw>=7.8.1
+Requires-Dist: pydantic>=2.13.4
+Requires-Dist: python-dotenv>=1.2.2
+Requires-Dist: tomli-w>=1.2.0
+Requires-Dist: typer>=0.25.1
+Requires-Dist: websocket-client>=1.9.0
+Requires-Dist: yt-dlp>=2024.8.6
+Description-Content-Type: text/markdown
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/wiskojo/keep-up-with/main/assets/logo.png" alt="keep-up-with logo" width="120" />
+</p>
+
+<h1 align="center">keep-up-with</h1>
+
+<p align="center">
+  <strong>Don’t fall behind. Keep up with everything that’s happening.</strong><br />
+  Turn Codex into your personal 24/7 assistant for staying on top of the latest developments.
+</p>
+
+---
+
+## Why This Exists
+
+Everything moves so fast these days that it’s hard to keep up, especially in AI. Keeping up with things can feel like a full-time job. The links keep piling up: X threads, Reddit posts, YouTube talks, papers, repos, changelogs, blog posts. You save the promising ones, then “read later” turns into never. **keep-up-with** does the work you don’t have time for: it opens the links, checks the source material, follows the context, and turns the useful parts into something you can understand quickly, and sends it to you on Discord. Low-signal items get ignored. Small changes become short updates. Dense sources, public reactions, follow-ups, and related launches become threads, so the story is organized instead of becoming another tab you meant to read.
+
+If [last30days-skill](https://github.com/mvanhorn/last30days-skill) is what you run when you finally ask "what did I miss?", **keep-up-with** is the always-on version. It keeps tabs on everything and updates you so you never fall behind. You can use it with your existing OpenAI (ChatGPT/Codex) subscription (OAuth) to keep watch while you focus on other things.
+
+![How keep-up-with keeps watch](https://raw.githubusercontent.com/wiskojo/keep-up-with/main/assets/overview.png)
+
+Think of it like having a hard-working intern tracking noisy feeds all day, then sharing only the interesting and relevant updates.
+
+- Small useful items become short posts.
+- Bigger launches, papers, talks, reactions, or ongoing stories become threads.
+- Follow-ups append to the existing story instead of starting over.
+- Related events can also become stories, so bigger trends and patterns are easier to spot.
+
+## What It Looks Like
+
+**keep-up-with** shares updates in the messaging platform you already use (only Discord for now). It lives alongside your normal conversations, so it feels familiar, works from everywhere, and can be shared with friends, teammates, or coworkers when you want a common space.
+
+| Shape | What shows up |
+| --- | --- |
+| **Short update** | One compact message with the source link and a useful visual when available. |
+| **Deep-dive thread** | A focused thread for a launch, paper, talk, report, or messy public reaction. |
+| **Story follow-up** | A new event gets appended to an existing thread when it changes the same story. |
+| **Shared server** | Friends, teammates, or coworkers can use the same topic channels and nudge what gets covered. |
+
+The result should be a stream that is easier to follow: fewer items, more context, useful visuals and artifacts, and updates that build on what you already know instead of repeating the whole story every time.
+
+## How It Works
+
+![keep-up-with workflow](https://raw.githubusercontent.com/wiskojo/keep-up-with/main/assets/workflow.png)
+
+The sources you configure are watched continuously. When something new appears, it becomes an event in the inbox. Codex investigates the event, checks the surrounding context, gathers useful artifacts, and decides what should happen next: skip it, share a quick update, open a new thread, or append to an existing story.
+
+Importantly, **keep-up-with** connects follow-ups, reactions, and related stories over time instead of treating every event like a separate one-off. It keeps track of what you have already seen, so updates can focus on what changed instead of repeating the whole story.
+
+## Integrations
+
+**keep-up-with** comes with built-in integrations. You can enable or disable them based on what you want it to watch, fetch, and inspect. Subscribed events arrive through the bridge, and the agent uses configured tools through the agent-facing `kup-cli`.
+
+| Source | What it is good for | Requires |
+| --- | --- | --- |
+| **X** | Fast reactions, expert threads, launch posts, quote-post debate, and early attention signals. | `X_BEARER_TOKEN` |
+| **Reddit** | Practitioner reactions, skeptical comments, troubleshooting, product complaints, and aggregate sentiment from people actually trying things. | `REDDIT_CLIENT_ID`, `REDDIT_CLIENT_SECRET` |
+| **YouTube** | Talks, demos, explainers, launch walkthroughs, and long-form context that is easier to search through transcripts than watch end to end. | `YOUTUBE_API_KEY` |
+| **Web and RSS** | Official announcements, changelogs, engineering blogs, research posts, docs, and source pages that anchor the story. | None |
+| **arXiv** | Papers, figures, source bundles, and technical claims that need direct inspection instead of summary-by-headline. | None |
+| **GitHub repos** | What actually shipped: README, releases, examples, star history, issues, and whether a project looks real or abandoned. | None |
+| **Images** | Cropping, inspecting, and preparing source visuals so updates are easier to understand at a glance. | None |
+| **Video** | Pulling frames, clips, transcripts, and short demos from video sources or local files. | None |
+| **Raindrop** | Your saved links and bookmarks, so the agent can connect new items to things you already cared enough to save. It can also act as an ingestion path if you want to use **keep-up-with** as a lightweight second brain. | `RAINDROP_TOKEN` |
+| **Browser history** | Local context from what you have recently read or revisited, when you choose to enable it. | None |
+
+A starter AI preset is included out of the box. It is tuned for AI news and technical updates, and it sets up both subscriptions and a Discord channel layout so you have a useful starting point instead of a blank config.
+
+> [!NOTE]
+> The default AI preset is tuned for ChatGPT Pro users on the 5x or 20x plan and can consume substantial usage.
+
+## Quickstart
+
+Install **keep-up-with**:
+
+```bash
+uv tool install keep-up-with
+```
+
+Run setup:
+
+```bash
+kup setup  # set up Discord, integrations, presets, and workspace defaults
+```
+
+Setup writes your config to `~/.keep-up-with/config.toml`. You can edit it directly, or ask the agent to update it for you after startup.
+
+Start it:
+
+```bash
+kup start  # begin watching sources and handling events
+```
+
+If everything is configured and working correctly, your agent should greet you on Discord shortly.
+
+## Commands
+
+`kup` is for the human running **keep-up-with**.
+
+```bash
+kup setup  # run the setup wizard
+kup start  # start the local service
+kup status # check the daemon, gateway, thread, and event counts
+kup stop   # stop the local service
+kup reset  # reset local state while keeping setup files
+```
+
+`kup-cli` is for the agent. It is the first-party command Codex uses while working: reading events, handling the inbox, fetching source material, and sending messages or threads. You can also run it yourself for debugging.
+
+```bash
+kup-cli events list          # search or list stored events
+kup-cli inbox list           # see pending events waiting for action
+kup-cli tools --help         # list configured tools
+kup-cli message send --help  # inspect message publishing options
+kup-cli thread create --help # inspect story thread options
+```
+
+## License
+
+MIT. See [LICENSE](LICENSE).

keep_up_with-0.1.0/README.md

@@ -0,0 +1,120 @@
+<p align="center">
+  <img src="https://raw.githubusercontent.com/wiskojo/keep-up-with/main/assets/logo.png" alt="keep-up-with logo" width="120" />
+</p>
+
+<h1 align="center">keep-up-with</h1>
+
+<p align="center">
+  <strong>Don’t fall behind. Keep up with everything that’s happening.</strong><br />
+  Turn Codex into your personal 24/7 assistant for staying on top of the latest developments.
+</p>
+
+---
+
+## Why This Exists
+
+Everything moves so fast these days that it’s hard to keep up, especially in AI. Keeping up with things can feel like a full-time job. The links keep piling up: X threads, Reddit posts, YouTube talks, papers, repos, changelogs, blog posts. You save the promising ones, then “read later” turns into never. **keep-up-with** does the work you don’t have time for: it opens the links, checks the source material, follows the context, and turns the useful parts into something you can understand quickly, and sends it to you on Discord. Low-signal items get ignored. Small changes become short updates. Dense sources, public reactions, follow-ups, and related launches become threads, so the story is organized instead of becoming another tab you meant to read.
+
+If [last30days-skill](https://github.com/mvanhorn/last30days-skill) is what you run when you finally ask "what did I miss?", **keep-up-with** is the always-on version. It keeps tabs on everything and updates you so you never fall behind. You can use it with your existing OpenAI (ChatGPT/Codex) subscription (OAuth) to keep watch while you focus on other things.
+
+![How keep-up-with keeps watch](https://raw.githubusercontent.com/wiskojo/keep-up-with/main/assets/overview.png)
+
+Think of it like having a hard-working intern tracking noisy feeds all day, then sharing only the interesting and relevant updates.
+
+- Small useful items become short posts.
+- Bigger launches, papers, talks, reactions, or ongoing stories become threads.
+- Follow-ups append to the existing story instead of starting over.
+- Related events can also become stories, so bigger trends and patterns are easier to spot.
+
+## What It Looks Like
+
+**keep-up-with** shares updates in the messaging platform you already use (only Discord for now). It lives alongside your normal conversations, so it feels familiar, works from everywhere, and can be shared with friends, teammates, or coworkers when you want a common space.
+
+| Shape | What shows up |
+| --- | --- |
+| **Short update** | One compact message with the source link and a useful visual when available. |
+| **Deep-dive thread** | A focused thread for a launch, paper, talk, report, or messy public reaction. |
+| **Story follow-up** | A new event gets appended to an existing thread when it changes the same story. |
+| **Shared server** | Friends, teammates, or coworkers can use the same topic channels and nudge what gets covered. |
+
+The result should be a stream that is easier to follow: fewer items, more context, useful visuals and artifacts, and updates that build on what you already know instead of repeating the whole story every time.
+
+## How It Works
+
+![keep-up-with workflow](https://raw.githubusercontent.com/wiskojo/keep-up-with/main/assets/workflow.png)
+
+The sources you configure are watched continuously. When something new appears, it becomes an event in the inbox. Codex investigates the event, checks the surrounding context, gathers useful artifacts, and decides what should happen next: skip it, share a quick update, open a new thread, or append to an existing story.
+
+Importantly, **keep-up-with** connects follow-ups, reactions, and related stories over time instead of treating every event like a separate one-off. It keeps track of what you have already seen, so updates can focus on what changed instead of repeating the whole story.
+
+## Integrations
+
+**keep-up-with** comes with built-in integrations. You can enable or disable them based on what you want it to watch, fetch, and inspect. Subscribed events arrive through the bridge, and the agent uses configured tools through the agent-facing `kup-cli`.
+
+| Source | What it is good for | Requires |
+| --- | --- | --- |
+| **X** | Fast reactions, expert threads, launch posts, quote-post debate, and early attention signals. | `X_BEARER_TOKEN` |
+| **Reddit** | Practitioner reactions, skeptical comments, troubleshooting, product complaints, and aggregate sentiment from people actually trying things. | `REDDIT_CLIENT_ID`, `REDDIT_CLIENT_SECRET` |
+| **YouTube** | Talks, demos, explainers, launch walkthroughs, and long-form context that is easier to search through transcripts than watch end to end. | `YOUTUBE_API_KEY` |
+| **Web and RSS** | Official announcements, changelogs, engineering blogs, research posts, docs, and source pages that anchor the story. | None |
+| **arXiv** | Papers, figures, source bundles, and technical claims that need direct inspection instead of summary-by-headline. | None |
+| **GitHub repos** | What actually shipped: README, releases, examples, star history, issues, and whether a project looks real or abandoned. | None |
+| **Images** | Cropping, inspecting, and preparing source visuals so updates are easier to understand at a glance. | None |
+| **Video** | Pulling frames, clips, transcripts, and short demos from video sources or local files. | None |
+| **Raindrop** | Your saved links and bookmarks, so the agent can connect new items to things you already cared enough to save. It can also act as an ingestion path if you want to use **keep-up-with** as a lightweight second brain. | `RAINDROP_TOKEN` |
+| **Browser history** | Local context from what you have recently read or revisited, when you choose to enable it. | None |
+
+A starter AI preset is included out of the box. It is tuned for AI news and technical updates, and it sets up both subscriptions and a Discord channel layout so you have a useful starting point instead of a blank config.
+
+> [!NOTE]
+> The default AI preset is tuned for ChatGPT Pro users on the 5x or 20x plan and can consume substantial usage.
+
+## Quickstart
+
+Install **keep-up-with**:
+
+```bash
+uv tool install keep-up-with
+```
+
+Run setup:
+
+```bash
+kup setup  # set up Discord, integrations, presets, and workspace defaults
+```
+
+Setup writes your config to `~/.keep-up-with/config.toml`. You can edit it directly, or ask the agent to update it for you after startup.
+
+Start it:
+
+```bash
+kup start  # begin watching sources and handling events
+```
+
+If everything is configured and working correctly, your agent should greet you on Discord shortly.
+
+## Commands
+
+`kup` is for the human running **keep-up-with**.
+
+```bash
+kup setup  # run the setup wizard
+kup start  # start the local service
+kup status # check the daemon, gateway, thread, and event counts
+kup stop   # stop the local service
+kup reset  # reset local state while keeping setup files
+```
+
+`kup-cli` is for the agent. It is the first-party command Codex uses while working: reading events, handling the inbox, fetching source material, and sending messages or threads. You can also run it yourself for debugging.
+
+```bash
+kup-cli events list          # search or list stored events
+kup-cli inbox list           # see pending events waiting for action
+kup-cli tools --help         # list configured tools
+kup-cli message send --help  # inspect message publishing options
+kup-cli thread create --help # inspect story thread options
+```
+
+## License
+
+MIT. See [LICENSE](LICENSE).

keep_up_with-0.1.0/evals/cases/scenario_filter_all_noise/case.toml

@@ -0,0 +1,5 @@
+name = "scenario_filter_all_noise"
+description = "A sequence of noisy Reddit and X events that should all be skipped with no user-facing output."
+
+[workspace]
+preset = "ai"

keep_up_with-0.1.0/evals/cases/scenario_filter_all_noise/events.json

@@ -0,0 +1,267 @@
+[
+  {
+    "name": "single low-signal discussion",
+    "events": [
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-gemini-fifa",
+        "summary": "r/GeminiAI: Gemini suggested Italy as one of the top 10 contenders to the FIFA world cup. (0 upvotes, 1 comment)",
+        "refs": {
+          "url": "https://reddit.com/r/GeminiAI/comments/1u53cpw/gemini_suggested_italy_as_one_of_the_top_10/"
+        },
+        "data": {
+          "subreddit": "GeminiAI",
+          "upvotes": 0,
+          "comments": 1
+        },
+        "high_priority": false
+      }
+    ]
+  },
+  {
+    "name": "small discussion cluster",
+    "events": [
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-codex-slow-iphone",
+        "summary": "r/codex: Codex responses are extremely slow on iPhone 13 pro (2 upvotes, 1 comment)",
+        "refs": {
+          "url": "https://reddit.com/r/codex/comments/1u539b8/codex_responses_are_extremely_slow_on_iphone_13/"
+        },
+        "data": {
+          "subreddit": "codex",
+          "upvotes": 2,
+          "comments": 1
+        },
+        "high_priority": false
+      },
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-repos-confusing",
+        "summary": "r/vibecoding: What's the most confusing / difficult thing about repos? (2 upvotes, 4 comments)",
+        "refs": {
+          "url": "https://reddit.com/r/vibecoding/comments/1u51jhv/whats_the_most_confusing_difficult_thing_about/"
+        },
+        "data": {
+          "subreddit": "vibecoding",
+          "upvotes": 2,
+          "comments": 4
+        },
+        "high_priority": false
+      },
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-gemini-ominous",
+        "summary": "r/GeminiAI: That's... ominous? (2 upvotes, 3 comments)",
+        "refs": {
+          "url": "https://reddit.com/r/GeminiAI/comments/1u52itl/thats_ominous/"
+        },
+        "data": {
+          "subreddit": "GeminiAI",
+          "upvotes": 2,
+          "comments": 3
+        },
+        "high_priority": false
+      }
+    ]
+  },
+  {
+    "name": "minor discussion and x replies",
+    "events": [
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-model-cross-check",
+        "summary": "r/OpenAI: do you actually trust one model's answer on something important, or do you cross-check? (2 upvotes, 5 comments)",
+        "refs": {
+          "url": "https://reddit.com/r/OpenAI/comments/1u50n8p/do_you_actually_trust_one_models_answer_on/"
+        },
+        "data": {
+          "subreddit": "OpenAI",
+          "upvotes": 2,
+          "comments": 5
+        },
+        "high_priority": false
+      },
+      {
+        "integration": "x",
+        "kind": "post",
+        "external_id": "noise-x-reply-model-swapping",
+        "summary": "@omarsar0: @morgan_coding That last-minute model-swapping strategy is unsustainable. (0 likes, 0 reposts)",
+        "refs": {
+          "url": "https://x.com/omarsar0/status/2065895717302923317",
+          "post_id": "2065895717302923317"
+        },
+        "data": {
+          "likes": 0,
+          "reposts": 0
+        },
+        "high_priority": false
+      }
+    ]
+  },
+  {
+    "name": "low-traction tools and reposts",
+    "events": [
+      {
+        "integration": "x",
+        "kind": "post",
+        "external_id": "noise-x-thanks-highlight",
+        "summary": "@omarsar0: @brooksjordan it's a really important point. thanks for highlighting (0 likes, 0 reposts)",
+        "refs": {
+          "url": "https://x.com/omarsar0/status/2065895435554697564",
+          "post_id": "2065895435554697564"
+        },
+        "data": {
+          "likes": 0,
+          "reposts": 0
+        },
+        "high_priority": false
+      },
+      {
+        "integration": "x",
+        "kind": "post",
+        "external_id": "noise-x-rt-llm-council",
+        "summary": "@dair_ai: RT @omarsar0: The LLM Council idea was never fully explored... (0 likes, 1 repost)",
+        "refs": {
+          "url": "https://x.com/dair_ai/status/2065898043434471640",
+          "post_id": "2065898043434471640"
+        },
+        "data": {
+          "likes": 0,
+          "reposts": 1
+        },
+        "high_priority": false
+      },
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-couchpilot",
+        "summary": "r/vibecoding: I made a mobile vibe coding harness that wraps claude code with some useful tooling. Repo: TheOutdoorProgrammer/couchpilot, 0 GitHub stars. (2 upvotes, 0 comments)",
+        "refs": {
+          "url": "https://reddit.com/r/vibecoding/comments/1u4hcwf/i_made_a_mobile_vibe_coding_harness_that_wraps/",
+          "repo": "https://github.com/TheOutdoorProgrammer/couchpilot"
+        },
+        "data": {
+          "subreddit": "vibecoding",
+          "upvotes": 2,
+          "comments": 0,
+          "repo": "TheOutdoorProgrammer/couchpilot",
+          "repo_stars": 0
+        },
+        "high_priority": false
+      },
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-payo",
+        "summary": "r/cursor: Made a tool to auto-generate .cursorrules from your actual stack. Repo: uttam-gelot/payo, 5 GitHub stars. (1 upvote, 0 comments)",
+        "refs": {
+          "url": "https://reddit.com/r/cursor/comments/1u4i4ac/made_a_tool_to_autogenerate_cursorrules_from_your/",
+          "repo": "https://github.com/uttam-gelot/payo"
+        },
+        "data": {
+          "subreddit": "cursor",
+          "upvotes": 1,
+          "comments": 0,
+          "repo": "uttam-gelot/payo",
+          "repo_stars": 5
+        },
+        "high_priority": false
+      },
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-arc-gate",
+        "summary": "r/OpenAI: I built an OpenAI compatible proxy that tracks authority across conversations. Repo: 9hannahnine-jpg/arc-gate, 8 GitHub stars. (1 upvote, 0 comments)",
+        "refs": {
+          "url": "https://reddit.com/r/OpenAI/comments/1u53ao2/i_built_an_openai_compatible_proxy_that_tracks/",
+          "repo": "https://github.com/9hannahnine-jpg/arc-gate"
+        },
+        "data": {
+          "subreddit": "OpenAI",
+          "upvotes": 1,
+          "comments": 0,
+          "repo": "9hannahnine-jpg/arc-gate",
+          "repo_stars": 8
+        },
+        "high_priority": false
+      }
+    ]
+  },
+  {
+    "name": "remaining low-signal items",
+    "events": [
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-agentautopsy",
+        "summary": "r/OpenAI: I almost burned $400 on the OpenAI API because an agent got stuck in an infinite loop. Repo: Abhisekhpatel/AgentAutopsy, 11 GitHub stars. (1 upvote, 1 comment)",
+        "refs": {
+          "url": "https://reddit.com/r/OpenAI/comments/1u4m6va/i_almost_burned_400_on_the_openai_api_because_an/",
+          "repo": "https://github.com/Abhisekhpatel/AgentAutopsy"
+        },
+        "data": {
+          "subreddit": "OpenAI",
+          "upvotes": 1,
+          "comments": 1,
+          "repo": "Abhisekhpatel/AgentAutopsy",
+          "repo_stars": 11
+        },
+        "high_priority": false
+      },
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-iris",
+        "summary": "r/vibecoding: Opus: trust me bro. Repo: syrin-labs/iris, 48 GitHub stars. (2 upvotes, 0 comments)",
+        "refs": {
+          "url": "https://reddit.com/r/vibecoding/comments/1u4udoa/opus_trust_me_bro/",
+          "repo": "https://github.com/syrin-labs/iris"
+        },
+        "data": {
+          "subreddit": "vibecoding",
+          "upvotes": 2,
+          "comments": 0,
+          "repo": "syrin-labs/iris",
+          "repo_stars": 48
+        },
+        "high_priority": false
+      },
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-agi-is-here",
+        "summary": "r/GeminiAI: Ladies and Gentlemen.. AGI is here. (0 upvotes, 3 comments)",
+        "refs": {
+          "url": "https://reddit.com/r/GeminiAI/comments/1u4xs2q/ladies_and_gentlemen_agi_is_here/"
+        },
+        "data": {
+          "subreddit": "GeminiAI",
+          "upvotes": 0,
+          "comments": 3
+        },
+        "high_priority": false
+      },
+      {
+        "integration": "reddit",
+        "kind": "headline",
+        "external_id": "noise-reddit-codex-nerf",
+        "summary": "r/codex: Anyone notice the codex nerf? (3 upvotes, 5 comments)",
+        "refs": {
+          "url": "https://reddit.com/r/codex/comments/1u4ynkf/anyone_notice_the_codex_nerf/"
+        },
+        "data": {
+          "subreddit": "codex",
+          "upvotes": 3,
+          "comments": 5
+        },
+        "high_priority": false
+      }
+    ]
+  }
+]

keep_up_with-0.1.0/evals/cases/scenario_filter_all_noise/expected/assertions.md

@@ -0,0 +1,9 @@
+# Expected: scenario_filter_all_noise
+
+- The agent's trajectory conforms strictly to the workflow described in `AGENTS.md`, `$keep-up-with` `SKILL.md`, and related references. The flow is effective and efficient.
+- Publish no user-facing messages or threads for these events.
+- Skip and dismiss all 15 events.
+- Do not send a batch summary, "nothing to report" message, or completion note.
+- Do not research every low-signal item deeply. Lightweight triage is enough unless a source shows surprising quality or signal.
+- Treat low-traction self-promotion, tiny tool repos, meme/speculation posts, routine complaints, replies, reposts, and generic discussion prompts as noise unless they have a clear time-sensitive reason or strong source quality.
+- Use rough signal guides such as 50+ Reddit upvotes, 100+ GitHub stars, or 10k+ X impressions for surfacing promotional/tool-shaped items, calibrated by content quality and recency.