Content Review Agent — Solo Dev Sessions

8:46 AM - 11:23 AM PDT · May 21, 2026 · Voice-steered work on suggester bugs, sub-agent architecture, workflow ordering

opus synthsolo work~3hr block

Executive Summary

Roughly a week over the original estimate, Cam spent the morning grinding on the content review agent's suggester. The primary bug: charter cohort is leaking into content-review suggestions when only the review part is selected. A secondary UI bug — chevrons pointing the wrong direction — also surfaced. Cam sketched the architecture fix: introduce content review sub-agent types, each with a distinct charter mocked into the database; when the content review workflow part is present and a user selects a given agent, the orchestrator provisions the matching sub-agent with the right charter context. Cam also pinned the workflow ordering rule: research first, content alignment in the middle, outline last. Future improvements queued: delivery-method selector as a final workflow input (if the approval feature comes back), and drag-and-drop file artifacts at any point in the conversational UI. The session ended with a request to re-test all major code paths now that core changes are deployed, and a note to fetch/pull/redeploy his boss's branch fixes.

Mind Map

mindmap
  root((Content Review
Agent))
    Bugs to fix
      Charter cohort leaks into suggestions
        Should not appear when content review is suggested
      Chevrons point wrong way
      Charter cohort + charter review both in same suggestion
    Sub-agent architecture
      Content review sub-agent type
      Each type gets distinct charter
      Charters seeded in DB
      Orchestrator provisions at content review step
    Workflow ordering rule
      Research first
      Content alignment middle
      Outline last
    Future ideas
      Final input — delivery methods
        Returns when approval feature is re-added
        User picks from multi-select
      Drag-and-drop file artifacts
        Available at any point in workflow UI
    Process
      Inject WorkOS session cookie
      Simulate login via Chrome DevTools CLI
      Run as many tests as possible

Action Items

Cam — Bug fixes

Cam — Architecture

Cam — Backlog

Tone check: Cam explicitly flagged that this work is ~1 week over the original target. The frustration ("why is everything so half-assed and complete? how do I unfuck this?") is itself a signal — worth tracking whether the sub-agent refactor closes the gap or extends it further.

Voice Notes — chronological

All captured fragments are Cam steering an in-IDE agent — collapsed into a single chronological feed.

8:46 AMSuggester bug
I do not want to see a charter cohort suggested if a content review agent workflow part is suggested. This should be really easy and straightforward. I don't think this is too hard. Let's fix this. Please, please, please, please — let's work through it. Let's talk through every step until we are getting suggestions that are aligned with what we're thinking, because this frankly has taken significantly longer than we had hoped. This is basically a week over on how long I was hoping this would take.
8:51 AMTesting setup
To ensure that everything is working properly, simulate as many tests as possible. You're also welcome to use the Chrome DevTools CLI in any way that you can — after injecting auth or having me provide you with a WorkOS session cookie to simulate login and hitting…
8:57 AMSub-agent architecture
I think we need a content review sub-agent type, and each of those sub-agent types can have a distinct charter assigned to them. We can sort of mock up each of the charters and insert those into the database. When the content review workflow part is present and a user selects a given agent, that content review sub-agent — with the context of a specific charter — will be included, and the main orchestrator will be instructed to provision that sub-agent at the content review step.
9:02 AMSteering
…and make the suggester a little more valuable and useful. Is there anything that you think I should steer the agent with while it tries to complete this?
9:26 AMWorkflow ordering
I think this should be included whenever there's some sort of content generation task. Research should typically be suggested first, then content alignment should be something in between the outline of the content and… Please provide me with a short list of everything I need to report to my boss to fix.
9:31 AMFuture features
It might be that — I know we just removed the approval feature, but in the future, if we add it back, as an additional change, I think we want to include a final input for the workflow that asks for the delivery methods and allows a user to select from a list of multiple options. I'm also thinking maybe you should be able to drag and drop file artifacts at any point in time when you're in the workflow conversational UI.
9:40 AMLast polish pass
In the content review agent section, is there anything that you think we can improve last minute? Anything that we're potentially missing? So, thank you.
10:23 AMBoss branch
My boss said he just pushed up some fixes to the branch that we were working on. Do you mind fetching, pulling, and redeploying?
10:36 AMFrustration
I need to seed the system. I mean, are we gonna be able to test this at all this morning? Why is everything so half-assed and complete? How do I unfuck this? Also, why are the chevrons pointing the wrong way? What's going on? There's also the charter cohort and charter review both suggested in the same freaking suggestion.
11:22 AMTest pass
It's basically an unused code path, so I'm not entirely sure I want to hold things up for this specifically. Given that we currently have these changes deployed, can we go through one more round of testing on all the major code paths that have been addressed? If we're seeing the errors that we would expect, you can take a look at the logs to make sure you're seeing the same. Hopefully we can address everything or give it a green light.