
StudyHour Labs
156 posts

StudyHour Labs
@studyhourlabs
Revision planning and AI study tools for UK students.



@thsottiaux @mark_k Will Windows eventually get computer use?



Codex just got a lot more powerful. Computer use, in-app browser, image generation and editing, 90+ new plugins to connect to everything, multi-terminal, SSH into devboxes, thread automations, rich document editing. Learns from experience and proactively suggestions work. And a ton more.

Has anyone actually switched from Claude Code to Codex?

Codex just got a lot more powerful. Computer use, in-app browser, image generation and editing, 90+ new plugins to connect to everything, multi-terminal, SSH into devboxes, thread automations, rich document editing. Learns from experience and proactively suggestions work. And a ton more.




You can tell the Claude app devs are only focused on macOS and not Windows, because they just hard code the Mac command symbol for Claude so I see it on Windows That would be so confusing if I didn’t know what it was lmao

PDFs break almost every AI agent pipeline I've built. Not because of the AI. Because of the parser. Here's what actually happens when your agent reads a PDF: 1. Tables get flattened into garbage text 2. Formulas turn into random symbols 3. Multi-column layouts merge into one unreadable block 4. Speed tanks when the file is more than 10 pages The AI never sees what you think it sees. Firecrawl just shipped Fire-PDF, a Rust-based parser. What changed: 1. PDF to markdown, 5x faster than before 2. Tables preserved, not flattened 3. Formulas kept intact 4. Zero config, drop it in and it works I've had Firecrawl in my stack for months. The PDF part was always the weak link. Most "AI can't read this doc" problems are parser problems. Fix the input, the AI handles the rest.

Today we're launching a rebuilt version of Claude Code on desktop. The app has been redesigned for the ground up to make it easier than ever to parallelize work with Claude. I haven't opened an IDE or terminal in weeks. Excited for you all to give it a shot!

Increasingly I'm discovering that Claude's Desktop app does a better job at doing what I need than ChatGPT's...

PDFs break almost every AI agent pipeline I've built. Not because of the AI. Because of the parser. Here's what actually happens when your agent reads a PDF: 1. Tables get flattened into garbage text 2. Formulas turn into random symbols 3. Multi-column layouts merge into one unreadable block 4. Speed tanks when the file is more than 10 pages The AI never sees what you think it sees. Firecrawl just shipped Fire-PDF, a Rust-based parser. What changed: 1. PDF to markdown, 5x faster than before 2. Tables preserved, not flattened 3. Formulas kept intact 4. Zero config, drop it in and it works I've had Firecrawl in my stack for months. The PDF part was always the weak link. Most "AI can't read this doc" problems are parser problems. Fix the input, the AI handles the rest.

If you're reading this and thinking "skill issue", you're probably working on problems that LLMs have seen thousands of times. That's fine, but don't confuse "AI works for my work" with "AI works". Get out of the AI comfort zone.



