Outlines

Outlines AI

Outlines AI

Outlines AI

Outlines AI

Outlines AI

Outlines AI

Outlines AI

Outlines AI

Outlines AI

Outlines AI

The Death of "Vibe Coding": Why un-monitored AI generation is creating a compounding technical debt.

Hey everyone, ​We are quickly approaching a major bottleneck in AI-assisted software engineering. Relying on LLMs to spit out thousands of lines of code without a strict, human-driven architectural framework—what many call "Vibe Coding"—is creating brittle, unmaintainable systems. ​I’ve formalized this structural shift into a public document on GitHub: The AI-Powered Developer Manifesto. ​Instead of treating AI as a replacement for software architecture, we need to shift our paradigm from Micro-Coding (syntax generation) to Macro-Coding (system direction and epistemic supervision). ​Here is a crucial excerpt from Section 2.5 of the Manifesto, outlining why the current trajectory is leading toward a systemic collapse: ​2.5 The Compounding Technical Debt and Systemic Collapse ​The illusion of rapid deployment via un-monitored AI generation hides a critical flaw: compounding technical debt. ​When developers act merely as "vibe coders"—accepting AI outputs without deep syntactic validation—the codebase becomes an agglomeration of statistical probabilities rather than deterministic logic. By late 2026, systems built entirely on un-vetted AI iterations are projected to hit an architectural wall: a state where the complexity of debugging AI-generated hallucinations outweighs the speed of initial deployment. ​True AI-Powered Developers do not delegate understanding; they delegate execution while retaining absolute epistemic responsibility over the system architecture. ​The goal of this manifesto is to redefine our role: we aren't syntax writers anymore; we are system directors. ​I'd love to hear your thoughts on this. Are you already seeing the limits of un-monitored "vibe coding" in your production environments? How are you structuring your prompts to maintain macro-level architectural control? ​Full Manifesto and repository for open contributions: 👉 https://github.com/FractalDevelop/ai-powered-developer-manifest.git submitted by /u/BYTES_18 [link] [comments]

AI Epistemic Risks: Emerging Mechanisms & Evidence [R]

How will AI affect our ability to think and judge for ourselves? Our new paper co-authored by 30 experts explores epistemic risks—the threats AI poses to our collective capacity to form beliefs accurately, reason well, and maintain a healthy information environment. We look at how AI can lead to harm through these mechanisms: Persuasion & Manipulation: AI systems are highly persuasive, opening the door for political/economic manipulation, incitement and radicalization, and other misuse, as well as unintentional harms like AI sycophancy and mental health risks. Cognitive Offloading: We may be delegating our thinking to AI at a deeper level than prior technologies, risking long-term degradation of individual and societal cognitive resilience. Feedback Loops: Human-AI and AI-AI interactions are narrowing the epistemic space humans and AIs draw from. This already drives homogenization, and may potentially lead to fragmentation and “lock-in” (a self-referential state that is difficult to reverse). While we believe AI could be an unprecedented lever for improving how humanity processes knowledge, we shouldn’t assume this will happen by default. We outline promising directions to change this trajectory across how AI systems are built, human-AI interaction design, institutional and individual adaptation, and information market incentives. Epistemic risks are self-perpetuating. As they can undermine the individual cognitive and social foundations needed to recognize, prioritize, and govern other threats—including the risks from AI itself—the time to act is now, before our capacity to respond is itself lost. Authors: Mick Yang, Stephen Casper, Jonathan Stray, Jasmine Li, Cameron Jones, Anna Gausen, Natasha Jaques, Brian Christian, Bálint Gyevnár, Hannah Rose Kirk, Zhonghao He, Dan Zhao, Siao Si Looi, Joshua Levy, Kobi Hackenburg, Elizabeth Seger, Matt Kowal, Michelle Malonza, Luke Hewitt, Hause Lin, Maarten Sap, Dylan Hadfield-Menell, Thomas H. Costello, Reihaneh Rabbany, Jean-François Godbout, David G. Rand, Atoosa Kasirzadeh, Gordon Pennycook, Yoshua Bengio, Kellin Pelrine Paper: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6873005 submitted by /u/KellinPelrine [link] [comments]

I built a 16-step multi-agent content pipeline. Claude runs the writing and reasoning agents. Here is the architecture and what surprised me.

Sharing this because it is built on Claude and I think the orchestration part is the interesting bit, not the marketing. Full disclosure up front, I am the one who built it. The problem I had: I wanted a steady flow of SEO articles on my own site (vexp.dev) without hiring writers or turning into a full time prompt jockey. So instead of one giant prompt, I broke the job into a pipeline of small agents, each with one narrow task and a clear handoff to the next. Roughly how it is wired: A research agent pulls keyword candidates and ranks them by traffic divided by difficulty. A planning agent turns the chosen keyword into an outline and a search intent. A writing agent drafts in the site's voice. Then separate passes for fact tightening, internal structure, JSON-LD, and formatting for the target CMS. Sixteen steps total before anything gets published. Where Claude fits: the writing and the reasoning heavy steps (planning, voice matching, the editing passes) run on Claude, which is where most of the quality lives. I am not going to pretend it is pure Claude. A few mechanical steps use other models because they are cheaper for boring work. But the parts a reader actually feels are Claude. Things that surprised me building it: Small single purpose agents beat one mega prompt by a lot. Easier to debug, and the failure modes are isolated instead of one black box. When the voice drifts I know exactly which step to fix. Asking Claude to critique its own draft in a separate pass, with a fresh context and a specific rubric, caught more than stuffing "be critical" into the original prompt. Encoding brand voice once and passing it as a constraint to every step held up better than re-describing it each time. The receipts, with the honest caveat: on my own site over 90 days it hit 4.1% Google CTR and picked up 674 AI citations. The Search Console related to vexp.dev is public if you want to verify. That is one site in one niche though, I am showing the method, not promising you the same number. It is free to try, one article, no card. The tool is at quibo.cc if you want to look. Mostly happy to talk architecture in the comments, that is why I posted here and not somewhere salesy. submitted by /u/Objective_Law2034 [link] [comments]

Claude doesn't know what a pterodactyl looks like

Needed a simple pterodactyl outline to cut around for my kid's birthday cake. Decided to try AI as my drawing skills are not as good as my cake-making skills. Discovered my drawing skills are, in fact, better than Claude's. EDIT: I didn't even realise Claude could generate images until today. It asked me if I wanted it to show me what shapes to cut out to make the cake. That image didn't make any sense either so I thought I'd try asking it to do a simple outline instead. Lesson learnt - won't be asking it for images again in future. submitted by /u/Nikki_Ess [link] [comments]

Anyone else using AI more but feeling like they’re thinking less?

I’ve been using AI pretty heavily for the past few months — quick research, rewriting emails, brainstorming ideas, even helping outline stuff I need to write. It saves so much time and the output is usually decent. But lately I’ve noticed something weird: I’m second-guessing myself way less. I’ll get an answer from it and just kind of roll with it instead of thinking it through like I used to. Yesterday I asked it about something I already had a rough opinion on, accepted its take, and only later realized I didn’t even challenge any part of it. It feels convenient as hell, but also a little unsettling. Like I’m outsourcing the actual thinking part. Is this normal? Or am I slowly losing the habit of thinking deeply on my own? Anyone else feeling this? submitted by /u/pen-pineapple-apple [link] [comments]

Opus or Sonnet for creative tasks?

I’m not interested in a discussion about degradation over time, just to be clear. What I want to know is which model is best at the current moment for helping to draft creative content. Use case examples would be drafting narrative outlines or simulating tabletop RPG campaigns. I first started using Claude around the time Sonnet 4.6 came out, and if I remember correctly, Sonnet 4.5 was preferred for creative expression, and Opus 4.x was preferred for analytical tasks. But I feel like both Opus and Sonnet have changed a lot since then. Does it still hold that Sonnet is better for creative purposes, or does Opus currently have the edge? Again, with recognition that folks tend to feel that output quality has degraded across the board. submitted by /u/And_Im_the_Devil [link] [comments]

Token usage rate comparison between models

I am trying out claude code for the first time. I'm coming from github copilot (through VS2022) where I was using claude (and others) through that. Is there anything that outlines the usage rate between models with claude code (or claude in general)? GitHub would tell you "Claude Opus 4.7 - 14x" or "Claude Sonnet 4.6 - 1x" and it would give me an idea that opus 4.7 is going to chew through tokens 14 times faster than 4.6. Is there anything that gives you an idea of just how much more Opus 4.8 is compared to 4.7 or 4.6, for example? Just looking to make a better judgement call on which model I may want to use for a task. Thanks submitted by /u/syntax53 [link] [comments]

I built an open-source Desktop App that gives your AI persistent memory across all platforms (100% Local SQLite, Zero-Docker)

Hey everyone, A few weeks ago I shared the CLI version of my project, ArcRift, on Reddit. After listening to your feedback—specifically the requests to remove heavy Docker dependencies and make it easier to install—I have just released the v1.6.1 Desktop App. If you regularly use LLMs for coding or research, you know the frustration of "amnesia." Every time you open a new chat, you have to painstakingly copy and paste your project structure and previous context just to get the AI up to speed. ArcRift is a 100% offline, local-first RAG and memory layer. It bridges the gap between your AI web chats (like Claude and ChatGPT) and your local tools (like Cursor or Claude Code) using a unified local database. I wanted something lightweight that did not require pulling Docker containers or subscribing to third-party memory APIs. It now runs as a native Tauri desktop app in your system tray, powered completely by local Ollama instances and a local SQLite database. We just launched a live website that outlines the details and demonstrates the features in action: Website: https://arcrift.vercel.app/ Codebase: https://github.com/Eshaan-Nair/ArcRift How it works & Core Features: Seamless Integration: The Chrome extension silently intercepts your prompts, surgically retrieves exactly the sentences relevant to your question from your database, and injects them before the prompt is sent to the LLM. Hybrid Search Retrieval: Uses sqlite-vec (with nomic-embed-text locally) + FTS5 keyword prefix matching to instantly find your past context. Knowledge Graph Extraction: An offline task queue uses a local LLM to extract entity relationships from your chats, mapping out a graph of your projects over time. Direct Codebase Indexing: The new Desktop App allows ArcRift to scan and index your actual project files into the graph, bridging the gap between your chat memory and your actual code architecture. Total Privacy (PII Redaction): The extension aggressively scrubs JWTs, API keys, emails, and IPs before data is even saved to your local disk. The extension works natively with Claude.ai, ChatGPT, DeepSeek, Gemini, Grok, and Mistral. If you save a conversation in ChatGPT today, you can instantly recall that exact context in Claude tomorrow. ArcRift is completely open-source (MIT). You can download the new .exe installer directly from the GitHub releases page. If you find this useful for your daily workflow, PRs are very welcome, and a star on GitHub helps the project get discovered! submitted by /u/Better-Platypus-3420 [link] [comments]

reddit brain goldmine - you are welcome

reddit.com/settings/data-request https://gamma.app/docs/Reddit-Brain-qt0g7e5vktlgifm Implementation Blueprint Your questions answered. Three steps to go from zero to a fully operational Reddit Brain. Step 0: Download Your Archive Go to reddit.com/settings/data-request and request your full data export. You'll receive a ZIP file containing comments.csv and posts.csv — everything you've ever posted on Reddit. Step 1: Get the Data Action: Request your export at reddit.com/settings/data-request. Then: Download ZIP, extract comments.csv and posts.csv. Optionally run reddit-user-to-sqlite to build a parallel SQLite archive for richer querying. Step 2: Build the Brain Action: Load into Sheets or a database. Clean, tag, and compute word count and engagement metrics. Then: Add LLM passes for canonical_question, topic, tone, and content type. Push into a vector store; connect via n8n or your preferred orchestrator. Step 3: Exploit the Hell Out of It Action: Generate content backlogs, podcast outlines, FAQs, scripts, and social copy from your corpus. Then: Use agents to draft from your own history, keep messaging on-brand, and refresh the archive with new exports on a schedule. submitted by /u/jdawgindahouse1974 [link] [comments]

The rubber duck that talks back, Claude as editor

So the joke is explain your problem to a rubber duck and you'll figure out your problem when outlining it. Bewildered coworkers you enlisted and thank while still confused are living rubber ducks. Autocorrect keeps making it rubber dicks and now I want to call this dildo method lol. I'm editing a fairly dense piece of writing. I don't let it write for me because the writing is literally the average of the data. Acceptable but not exceptional. But the criticism does land. If it calls out an area as under supported lacking receipts I can see it and arguing back and forth will help me see flaws. Most of the time my logic is right and well did it actually make it into the document? No? Well, put it there! There's a lot of hate directed at ai in creative spaces and for generating the output I get it. That's putting people out or work. But for challenging and working as a partner, I think there's value. It's basically the same result if I had a human editor to pester at all hours but that's hard to come by. A human is ideal but it they are not available, the result is better than what I would do on my own. I will caveat you do need to be skeptical. It can false trigger but this is useful as well. It forces you to defend your ideas. Same as with human critics. And if you keep getting the same signal in new chats there's probably a flaw. I still consider human feedback the gold standard but this process helps you make sure you take care of easy flaws and let them diagnose issues that only humans can catch. submitted by /u/jollyreaper2112 [link] [comments]

Opus 4.8 hallucinates being in game it was designing

submitted by /u/Limp-Ad-6842 [link] [comments]

thing i wish i'd known about ai tools when i started using them seriously a year ago

the biggest unlock wasn't the model getting better. it was me getting better at knowing when to use which tool. year-ago me: opened chatgpt for everything because it was the first tab. asked it questions, got mediocre answers, accepted them, moved on. now me: actually thinks about which tool fits the task. claude for writing and reasoning. perplexity (used to, less now) or kagi for find me a source. cursor for code. notebooklm for synthesizing across many documents. chatgpt voice for thinking-out-loud. granola for meeting notes. gamma for any deck or proposal that needs to leave my computer. each one has a specific role. this sounds obvious typed out. it wasn't obvious when i was just starting. i thought i was supposed to find The One Tool and master it. turns out the skill is matching tool to task. the tools are mostly fine. the user choosing the wrong tool is most of why outputs are bad. the deck side specifically was where i wasted the most time before figuring this out. used to ask claude to format things as a presentation and accept the markdown output. it looked like a deck. it wasn't a deck. once i started piping claude's structured outline into gamma as an ai presentation tool instead of trying to make claude be the deck builder, the artifact quality jumped immediately. claude is great at thinking. gamma is great at the slide format. asking either one to do the other's job produces a worse version of both. second thing: don't trust any tool that doesn't show its work. perplexity citations matter. claude saying i'm not certain about this matters. tools that just confidently produce output with no provenance are dangerous if you're going to act on the output. early on i trusted everything equally. now i grade tools by how clearly they show me what they don't know. third thing: the cheap subscriptions add up faster than you think. i ran the math at one point — what i spent in my first year of trying ai tools was more than what i'd have paid a human freelancer to do the things i was trying to automate. would have been faster, too. AI tools have a real cost-benefit math and it's not always in your favor, especially early when you're still figuring out what works. if i'd known those three things a year ago, i'd have wasted less money and gotten better outputs sooner. posting in case it helps anyone earlier in the curve. submitted by /u/Honest-Purchase-9113 [link] [comments]

A specific Claude project setup for client work that's saved me maybe 60 hours this year This is just one project structure but it's the most useful one I've built so I'll share it.

This is just one project structure but it's the most useful one I've built so I'll share it. I'm a consultant. Multiple clients, lots of context per client (their team, their tools, their history with me, the work we've done, the work we're planning). I used to spend the first 10 minutes of every working session re-orienting Claude to whichever client I was working on. So I built a Claude project per client. Here's what's in each one: A document called CLIENT_CONTEXT with the basics: who they are, what they do, my role, the engagement scope, key stakeholders and their personalities, the political situation (who's aligned, who's blocking), and what I am NOT supposed to do or say. A document called WORK_HISTORY with bullet-style notes from every previous engagement. Updated after each major deliverable. A document called CURRENT_PROJECT with whatever we're working on right now. This one changes frequently. A document called REFERENCE with their brand guidelines, their internal tools/jargon, format preferences (do they want decks or memos), and any other how this client likes things done knowledge. Then in the project instructions: Reference these documents before answering any question. If I ask about something not covered, ask me which client this is about or what context I want you to use. The result is I can open the project, type help me think about the q3 review with [stakeholder] and get useful work immediately. Without the project context, I'd spend 10 minutes setting up. Across 4 active clients and many sessions per week, the time savings compound. The setup took me maybe 90 minutes per client the first time. Updates are 5 min after major work. the one extension i'd add for anyone running this. i pair the project with a gamma workspace per client. claude does the thinking, gamma builds the artifact. the REFERENCE doc in claude includes a line that says ""this client wants decks, not memos"" or ""this client wants memos, not decks."" when claude outputs the structured thinking, i paste the outline into gamma using whichever sales deck template or board deck template matches the deliverable. ai presentation tool plus the per-client context means the deck comes out client-shaped without me reformatting it. across 4 clients, the artifact-build step went from an hour per deliverable to 20 minutes. Sharing in case it's useful to other consultants/freelancers who context-switch a lot. submitted by /u/Lanky_Revolution8174 [link] [comments]

I tried building an mcp server for my own use and it's surprisingly easy and also surprisingly limited

heard about mcp (model context protocol) like 100 times before i actually tried it. claude desktop, you can give it access to your local files and tools. seemed cool. spent a saturday building one for my personal use case. built: an mcp server that lets claude desktop search my obsidian vault, read my calendar, and check my todoist tasks. so i can ask claude what do i have on for next thursday and is anything overdue and it actually answers from my real data. what worked: the protocol itself is well-documented. claude wrote most of the code for me. setup is a config file and a process. genuinely under 2 hours of work. what didn't: it only works with claude desktop. so the give claude superpowers framing only applies to one specific surface. on the web app, on my phone, in claude code, none of those see my mcp server. so the utility is bottlenecked to when i'm at my desk in the desktop app. the second issue: claude doesn't always know it has the tools. i'd ask it to check my calendar and it would just answer generically about calendar best practices. i had to explicitly say use the calendar tool half the time. that'll probably improve but right now it's annoying. separately, the thing i was hoping mcp would unlock was ai actually generating my weekly client decks by reading my obsidian notes directly. doesn't work end-to-end yet. claude desktop reads the notes fine, but then i still have to manually paste the outline into gamma to build the actual deck. ai presentation tool side of the workflow isn't mcp-integrated for me. so the chain is mcp pulls the notes, claude structures the outline, gamma builds the slides. three steps where i wanted one. maybe a year from now. would i recommend trying it: yes if you're curious and have a saturday. no if you expect it to materially change how you use claude every day. it's cool but it's not quite the unlock the demos make it look like submitted by /u/OkAcanthisitta1576 [link] [comments]

Overnight autonomous coding

At work we've been prompted about running Claude Code overnight. The suggestion came in form of a document that loosely outlined how this could be done... use git worktrees, make tight specs, no commit to main, static code analysis and lining etc. Very high level. Had a bit of sales pitch smell to it, but has enough content to peak my interest in spite of it. I looked at reddit to verify if this is even an idea that could be taken seriously. I could only find a couple of reddit posts with little actual information and usually from about 4-6 months ago so not much credibility for today. I'd like some more opinions on the matter. So... For today, does the idea of running AI agents overnight to do coding tasks make sense? If so, what use cases does it make sense for and what would a sensible setup look like? What are the trade-off and practical costs you may face? submitted by /u/mehow_j [link] [comments]