{
  "video_id": "reddit_1u6mmuu",
  "channel_slug": "LocalLLaMA",
  "channel_handle": "r/LocalLLaMA",
  "title": "Local coding agents are good now, but only if you babysit them",
  "url": "https://www.reddit.com/r/LocalLLaMA/comments/1u6mmuu/local_coding_agents_are_good_now_but_only_if_you/",
  "external_url": null,
  "upload_date": "20260615",
  "published_at": "2026-06-15T17:07:20+00:00",
  "transcript": "Local coding agents are finally useful for me, but I still can’t just leave them alone.\n\nThey are great for small fixes, reading a repo, changing files, and doing boring code work. But if I give them too much freedom, they start touching random stuff, making nice looking broken code, or going way too far from the original task.\n\nThe workflow that works best for me is basically:\n\nsmall task  \nrun tests  \ncheck diff  \nfix the weird part  \nrepeat\n\nSo yeah, they save time, but your still sitting there like a tired manager with git diff open.\n\nIs that how you guys use them too, or did someone actually get a local coding agent to work alone without breaking stuff alot? I dont know if my setup is bad or this is just the current state.\n\n\n\n--- Top Comments ---\n\n\n[50 upvotes] This is how I use it for the past year. I'm not quite sure how people are doing 100% hand off to agentic loop while not understanding what is being generated. \n\n[11 upvotes] Sometimes I use Opus to babysit a local qwen.\n\nI mean that sounds, like a troll, but I give the goal to Opus and tell it to repeatedly try using the local model to achieve something, and write such notes, that future runs will be successful.\n\nThat way, same task can be done with a cheap local model in future.",
  "transcript_chars": 1261,
  "ingested_at": "2026-06-16T01:30:14.607469+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 65,
    "upvote_ratio": 0.93,
    "num_comments": 98,
    "author": "BTA_Labs",
    "is_self": true
  }
}