AI ML
Post #7102 · source on Telegram
Grok 4 Promoted as Vibe-Coding Tool That Replaces Cursor IDE
Description
A screenshot from X.com showing Paul Couvert (@itsPaulAi) posted on Jul 13: 'Grok 4 is excellent for vibe-coding. You can give it your entire codebase in 5s to add features or debug.' with bullet points: 'No need for Cursor', 'Works directly on the Grok site'. Below is a screenshot of the SuperGrok interface at grok.com showing a file 'all_code.txt' uploaded with the prompt 'Attached you'll find the last version of my codebase in the "all_code.txt". Now I want to implement a...' using Grok 4 model. The post has 98 comments, 169 retweets, 1.3K likes, and 357K views. This captures the AI coding tool landscape where every new model becomes the next 'IDE killer'
More like this
More like this in AI ML →
Use J and K for navigation
Comments
22Comment deleted
Dumping your entire codebase into a text file and uploading it to an AI chatbot is what we call 'vibe-coding' now -- back in my day we called it 'giving up'
Ah, 'all_code.txt'. The final evolution of version control, where 'git blame' is just you, staring at the two-million-line file, blaming yourself for ever thinking this was a good idea
Because nothing says "enterprise-ready" like zipping a 2-million-line monolith into all_code.txt and hoping the 16-k-token context window figures out your circular dependencies before the coffee gets cold
Ah yes, 'vibe-coding' - when you've given up on understanding your codebase so thoroughly that you're willing to upload the entire thing to Elon's AI and hope it vibes with your technical debt better than you do. Nothing says 'senior architect' quite like trusting critical business logic to an LLM that learned programming from Twitter threads
Ah yes, 'vibe-coding' - where you upload your entire legacy monolith as a single text file and an LLM magically refactors 15 years of technical debt in 5 seconds. I'm sure the context window won't hallucinate that critical payment processing logic into a recursive cat fact generator. But hey, at least we've finally automated the 'works on my machine' excuse into 'works in my prompt.'
Cursor: 'Gimme your whole monorepo.' Grok 4: 'Nah, just the file' - peak DX, zero context bloat
Pro tip: “No need for Cursor” usually implies “yes need for counsel” - monorepo-as-all_code.txt tends to exceed context windows and security budgets simultaneously
Strategy meeting: zip the monorepo into all_code.txt, upload to Grok, and let it “add features” - boom, instant onboarding, instant vendor lock-in, and a SOC2 finding that writes itself
cat **/* >> codebase.txt Comment deleted
node_modules goes brrrrrr Comment deleted
Wouldn’t preserve file names or hierarchy. You want find . -print -exec cat {} \; > codebase.txt Comment deleted
Its only Paul AI relax guys Comment deleted
Ultima Ratio Regum moment Comment deleted
Wait till you find https://repomix.com/ Comment deleted
Just sends you back a picture of spaghetti Comment deleted
he even texts the LLM like a corporate cuck, not surprised Comment deleted
Actually, Grok can accept individual code files, up to 10 at a time. But Qwen only accepts TXT files, and for it I really need to use this trick with one big TXT file. Comment deleted
I did put a whole library into a single txt file for gemini to read it Comment deleted
I do this, works for me import { appendFileSync, readFileSync } from 'fs'; import { readdir } from 'fs/promises'; import { join } from 'path'; const ROOT = './'; const IGNORE = ['.git', 'node_modules', 'yarn.lock', 'package.json', 'pnpm-lock.yaml']; const OUT = 'out.txt'; const init = async () => { const entries = await readdir(ROOT, { recursive: true, withFileTypes: true, }); const files = entries.filter((e) => e.isFile()); for (const entry of files) { const fullPath = join(entry.parentPath, entry.name); console.debug('Checking:', fullPath); if (IGNORE.some((el) => fullPath.includes(el))) { console.debug('Ignoring:', fullPath); continue; } console.debug('Passing:', fullPath); const content = readFileSync(fullPath, 'utf-8'); const out = `/*start of file [${fullPath}]*/\n` + content; appendFileSync(OUT, out + `/*end of file [${fullPath}]*/\n\n`); } }; init(); Comment deleted
One xml file for the entire repo lmao Comment deleted
And if you have enough of a context window it can work to explain something lol Comment deleted
I tried to upload a long log file to minimax ai, but it couldn't read it fully. Comment deleted