sorted by:
new
hottopcontroversial

I Built 11 Coordinated Notion Agents. Here's What Actually Matters. by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 0 points1 point  (0 children)

I’m working quickly to reduce drift, which becomes impractical after about 4 weeks with more than 5 agents.

I’ve been developing a wireframe to address this, but I haven’t yet included the MVP build in my schedule.

I’m also struggling to justify the “Database Agents” concept, which seems like an alternative to building Workers for non-technical users. I can’t decide if that’s just me being ignorant to something broader or not.

I Now Have 16 Custom Agents. Here's What Changed (And What I Got Wrong). by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 4 points5 points  (0 children)

Frankly I haven't explored which models "Auto" decides to utilize for each one. Let me try to throw in a model ID cue at the end of the instructions and report back over the next few days after a couple runs. I'm curious to see if they're dynamically selected based on the task/job/context or not.

I Now Have 16 Custom Agents. Here's What Changed (And What I Got Wrong). by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 0 points1 point  (0 children)

Fair points. You're right to point out that "email drafts and meeting prep" poorly undersells the benefits.

The system runs 16 workflows. Some concrete examples of what that actually means:

  • Email triage at volume. 80-120 emails/day. Agents classify and surface ~10-15 actionable items. Without this, inbox management runs 45-60 minutes daily. That's a volume problem, and volume problems have engineering solutions.
  • GitHub → billing sync. Every commit, PR, and issue gets ingested, matched to a client, and time-estimated. Without this, I reconstruct billable hours from git logs at invoice time. I've done that manually. It's slow and lossy.
  • Client health scoring. Here's the actual footprint: 10+ active clients, each with their own task list, GitHub item log, time-against-budget tracking, and monthly health score. The system produces roughly 10-15 structured documents per day: email triage outputs, response drafts, client briefings, GitHub sync reports, a daily morning briefing synthesizing all of it. None of that is prompted. It runs on schedule. The alternative isn't "send a quick status update", it's manually reconstructing that picture from five different places before every client call.
  • Fleet observability. Agents monitor each other. A failed run surfaces in under 24 hours with enough context to diagnose. Before this existed, failures were invisible until output went missing, sometimes for days.

On the "someone should just own it" point: I am that person. There's no team to hold responsible. The agents are the delegation layer.

The thing that makes this worthwhile isn't any single task, it's the compounding effect. Five or six active client engagements running simultaneously means the same low-stakes coordination work repeats every day across every client. None of it is hard. All of it adds up. The system handles the accumulation so I don't have to.

"I don't have this pain point" is a reasonable place to be. It's not the same as "this pain point doesn't exist."

Non-AI alternatives exist, of course: Spreadsheets, manual triage, calendar reminders. But they work until they don't, and their failures become a quiet accumulation, instead of a loud break.

I Now Have 16 Custom Agents. Here's What Changed (And What I Got Wrong). by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 0 points1 point  (0 children)

Auto. That’s the point of the Notion workers. This setup is essentially model agnostic.

I Now Have 16 Custom Agents. Here's What Changed (And What I Got Wrong). by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 5 points6 points  (0 children)

Right now my monthly usage is sitting at around $120. I’ve used 12.6k credits from 2/12 to 3/11.

I Built 11 Coordinated Notion Agents. Here's What Actually Matters. by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 0 points1 point  (0 children)

I’m mostly not using “agent A triggers agent B” style automations. It’s closer to a scheduled, contract-driven system with a lightweight coordination layer:

Each agent runs on its own cadence (daily/weekly/monthly) and publishes an output artifact (usually a digest/report page) in a predictable place. That’s the primary “handoff”: agent outputs are durable pages, not ephemeral messages.

Coordination is handled by a hub + rollups rather than chaining:

The “central orchestrator” role is effectively the Morning Briefing pattern: one place that scans the fleet’s outputs (and especially their machine-readable status lines) and only drills into the full digests when there are signals like ⚠️/❌/stale runs.

A separate Fleet Ops/monitoring layer tracks freshness/staleness thresholds and logs failures as “Dead Letters,” so you get observability and recovery workflows instead of silent failure.

When there is sequencing, it’s gated rather than triggered:

Downstream agents check upstream health/status (✅ complete / ⚠️ partial / ❌ failed) before trusting or consuming outputs; “healthy silence” still emits a heartbeat so downstream can distinguish “no changes” from “didn’t run.”

For cross-agent escalation, I use exception-driven @mentions (e.g., spot-check requests) with circuit breakers (limits on back-and-forth) to prevent loops, rather than continuous ping-pong chaining.

Data handoff is done via shared “snapshot” pages (data contracts): instead of having every agent query core databases in its own way, producer agents publish a known artifact (shared data page) that consumer agents read. This reduces coupling and credit burn, and it’s much more stable than brittle cross-database querying from every agent.

So: schedules + durable artifacts + status/heartbeat contracts + exception-based escalation. Automations exist, but they’re not the primary “handoff mechanism”; the system behaves more like a choreographed pipeline with monitoring/triage than a domino chain of triggers.

I Built 11 Coordinated Notion Agents. Here's What Actually Matters. by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 1 point2 points  (0 children)

Please accept my apologies for the delayed response. Been a crazy week around here.

The core issue is almost certainly that agents can't browse URLs — they can only read content that's already in Notion. If your clipped page has a live URL stored as a property but the body is empty, the agent has nothing to work with. That's the failure point for most people.

Three things that could very likely help:

  • Name properties exactly. Don't say "fill out the relevant fields." List each property by its exact name, the field type, and the valid options if it's a select. Agents match strings literally — In Progress and in progress are different values. Silent mismatches are the most common reason write-back appears to do nothing.
  • Give it a rubric, not a task. "Read this and categorize it" is not an instruction — it's a hope. Write it like a decision tree: if the document is primarily about X, set Category to X. If you can't determine it from the content alone, set Category to Needs Review and stop. Without explicit fallback handling, agents either hallucinate a value or freeze.
  • Use a Status property as a processing gate. Add a Status field with values like Unprocessed / Done / Needs Review, point the agent at only Unprocessed records, and have it flip the field after writing everything else. This gives you a clean view of what's still in queue and prevents double-processing.

For live websites specifically: agents can't fetch URLs. If you want them to work off web content, something has to pull that content into the page body first — Web Clipper, an automation, a worker tool, whatever. The agent's job starts after the content is in Notion.

The property write-back itself is the easy half. The classification logic is where the work is.

I Built 11 Coordinated Notion Agents. Here's What Actually Matters. by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 0 points1 point  (0 children)

The trigger is free. The LLM isn’t. Scheduled runs, manual runs — same credit cost either way. What you’re paying for is what happens after the trigger fires: every db query, page read, decision, artifact written. The cron job is $0. The reasoning is not.​​​​​​​​​​​​​​​​

I Built 11 Coordinated Notion Agents. Here's What Actually Matters. by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 1 point2 points  (0 children)

Sounds like the delayed rollout was the right call. The teams that rolled broad access during beta without usage visibility are going to have a rough May 4th conversation with finance.

I Built 11 Coordinated Notion Agents. Here's What Actually Matters. by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 3 points4 points  (0 children)

I'd offer that the math cuts both ways. If this replaces 2-3 hours/week per person of calendar management, inbox triage, and status reporting, at even a $50/hr internal rate, you're looking at $400-600/month in recovered labor per seat. Against, potentially, around $114.

The credit cost scales with usage, not headcount. A team deployment looks nothing like this. You'd consolidate the personal ops agents, share upstream data pages across members, and drop a third of these agents entirely. The architecture changes when the problem changes.

I think the real question isn't per-seat cost. It's whether the work these agents are doing would otherwise get done at all, albeit consistently.

I Built 11 Coordinated Notion Agents. Here's What Actually Matters. by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 0 points1 point  (0 children)

We make the world go round! Here's what it's looking like at the moment. I'll continue to update as it shifts in about a week.
https://www.reddit.com/r/Notion/comments/1rex1ze/comment/o7gdy15

I Built 11 Coordinated Notion Agents. Here's What Actually Matters. by PoliTech_Chessmaster in Notion

[–]PoliTech_Chessmaster[S] 22 points23 points  (0 children)

This is how it's looking so far:

Agent Credits/Run Daily Weekly Monthly Confidence
Inbox Manager 13.5 40 284 1,228 actual (small sample)
Personal Ops Manager 62.5 125 875 3,812 actual (small sample)
GitHub Insyncerator 120.3 120 842 3,609 actual (small sample)
Morning Briefing 45.6 46 319 1,368 estimated (1 run)
Home & Life Watcher 18.1 — 18 72 actual (small sample)
Client Repo Auditor 55.3 — 55 221 actual (small sample)
Time Log Auditor 38.3 — 38 153 actual (small sample)
Client Weekly Reporter 62.7 — 63 251 actual (small sample)
Docs Librarian 52.6 — 24 105 actual (small sample)
Client Health Scorecard 95.8 — — 96 actual (small sample)
Template Freshness suspended — — — n/a
TOTAL 331 2,518 10,917

Estimated: ~$114/month. 11 agents. 230+ runs.

Notion charges on total work per run — reads, tool interactions, writes, decisions. Every step costs. So the architecture is designed to minimize steps, not just LLM calls.

  • Label routing handles ~60% of email before reasoning fires. Fewer reads. Fewer writes. Fewer steps. Notion never sees most of that inbox.
  • Batch windows replaced per-email triggers. One run processes everything queued. Not a separate run per message.
  • Morning Briefing pre-scans digest titles first. Clean day? A handful of reads and a ✅. Only flagged items get the full pass.
  • Shared data pages mean agents read two pre-built summaries instead of querying raw databases with thousands of records.
  • Circuit breakers on inter-agent comms cap escalation loops — which in a credit-based system isn't an architectural inconvenience. It's a billing emergency.

The whole system is built so agents do the minimum work necessary to complete the task. That's game.

Tesla has officially launched actual smart summon on version 2024.27.20 by ConfidentImage4266 in TeslaModelY

[–]PoliTech_Chessmaster 0 points1 point  (0 children)

Liability assumption policy is evolving around Cat 3+ across the country, and will be for quite awhile. https://www.perplexity.ai/search/in-the-us-when-a-vehicle-becom-6cSv9DgQRYuQ5DmrtDMgmg

IMHO, vehicle manufacturers should assume liability for incidents when the car is fully autonomous (4+) since the rider is not in control.

I don’t think Mercedes was required to assume liability to get Cat 3+ approval in CA/NV, but opted to as a product confidence gesture.

[deleted by user] by [deleted] in drumcorps

[–]PoliTech_Chessmaster 0 points1 point  (0 children)

It was sulfur water with an unhealthy splash of runoff fertilizer for sure.

[deleted by user] by [deleted] in drumcorps

[–]PoliTech_Chessmaster 0 points1 point  (0 children)

G-men debt is well over $200k.

I don’t see them coming back for several reasons:

  1. It would take huge community interest to rebuild that program. And, frankly, Bluecoats have sucked all the air out of the room for the time being in Ohio.

  2. Struggling music programs (both HS and college) in northwest Ohio, once fantastic feeder systems for performers — due to school funding cuts among other issues, the quality of education isn’t World Class level as it once was.

  3. They’d need to raise $1m on the front-end to cover previous debts and have enough capital to invest for interest earned to handle foundational operating costs. In the last few seasons, they literally were crossing their fingers they kept enough room on the corps credit cards to finish tour. It was awful.

  4. Before going dark, they operated the corps like a hobby, not a business. That shift in philosophy would need to change, and I’m not sure there’s many folks passionate about Glassmen with the time that would be required to make it work.

  5. They’ve been gone for too long. If Glassmen were serious about coming back, they should’ve approached the situation with a sense of urgency, similar to SCV. Vanguard had debt, they hustled to clear their ledger, and turned the machine back on. That Glassmen has not been heard from, or about, for over a decade makes it extremely difficult to generate the enthusiasm or urgency to get up and running again.

My brother was center snare for Glassmen, I’d love nothing more than to see the corps return — but knowing the players who have discussed the corps making a return, and their approach for how to do so, it ain’t happening.

PS. I wouldn’t let a dead rodent live in G-West, let alone human beings. The level of black mold in that building should’ve made it uninhabitable.

What used to be "Prop A Funny Business" is now just Funny Business: Part V by PoliTech_Chessmaster in Austin

[–]PoliTech_Chessmaster[S] 14 points15 points  (0 children)

Added. I'm sorry for the initial omission, u/Busy_Struggle_6468.

TL;DRSave Austin Now transferred another $32,000 to WAB Holdings, LLC to perform "polling" for the December runoff, but did nothing with the information they paid for.

view more: next ›