Workday AI

Workday AI AI

Workday AI AI

Workday AI AI

Workday AI AI

Workday AI AI

Workday AI AI

Workday AI AI

Workday AI AI

Workday AI AI

Workday AI AI

Sam Altman says AI superintelligence is so big that we need a "New Deal." Critics say OpenAI’s policy ideas are a cover for "regulatory nihilism"

OpenAI says the world needs to rethink everything from the tax system to the length of the workday in order to prepare for the wrenching changes of superintelligence technology—the point at which AI systems are capable of outperforming the smartest humans. On Monday, in a 13-page paper titled “Industrial Policy for the Intelligence Age,” OpenAI said it wanted to “kick-start” the conversation with a “slate of people-first policy ideas.” How much faith to put in OpenAI’s words and motives, however, seems to be one of the key questions among many of the people reading the paper. The paper was released on the same day that The New Yorker published the results of a lengthy one-and-a-half-year investigation into OpenAI that raised questions about CEO Sam Altman’s trustworthiness on various issues, including AI safety. Read more: https://fortune.com/2026/04/06/sam-altman-says-ai-superintelligence-is-so-big-that-we-need-a-new-deal-critics-say-openais-policy-ideas-are-a-cover-for-regulatory-nihilism/ submitted by /u/fortune [link] [comments]

I wrote a cron job that saves me ~2 hours of dead time on Claude Code every day

If you're on a Max plan and use Claude Code heavily, you've probably noticed the 5-hour usage window starts when you send your first message, floored to the clock hour. So if you start working at 8:30 AM and hit the limit by 11, you're stuck until 1 PM. Two hours of nothing. Turns out you can manipulate this. Send a throwaway Haiku "hi" at 6 AM before your workday, and the window anchors to 6-11 AM instead of 8 AM-1 PM. That means by 11 AM you will have a fresh usage window! The easiest way I found to do this is to set up a GitHub Actions cron that does this automatically every morning. Repo if you want it: https://github.com/vdsmon/claude-warmup —> check the edits Let me know what you think and if it makes sense! EDIT: As suggested by [u/ContextCustodian](u/ContextCustodian), the same concept can be applied (in a simpler way) using a Claude Code Web scheduled task: https://claude.ai/code/scheduled. I did not test it yet, but it should work! EDIT 2: The native scheduled task works flawlessly! This is by far the easiest way of manipulating this. You can also extend this concept to other parts of your workday, not only for the first morning window. submitted by /u/victorsmoliveira [link] [comments]

You now can ask Claude to summarize your day with this MCP

I've been building Chronoid for about a year now — a macOS time tracking app that automatically monitors what apps and websites you use throughout the day. I just shipped an MCP server that lets Claude Desktop (or Cursor, VS Code, Windsurf) query all that data directly. How Claude helped build this: Claude Code one-shot the entire MCP server — I described what I wanted, pointed it at my existing database schema, and it generated the full Swift implementation in a single pass. I've hopped between pretty much every AI coding tool over the past year — ChatGPT Codex, Aider, GitHub Copilot, Amp Code, OpenCode — and settled on Claude Code. The $100/mo Claude Max plan is insane value, I can barely hit the limit. The key insight for native macOS/Swift development: AI is genuinely bad at native Swift compared to web/frontend/Next.js. The thing that makes it work is setting up a solid end-to-end workflow where code can be verified. My setup is Claude Code + xcodebuild piped through xcsift, which compacts Xcode's awful raw output into something clean and token-efficient: xcodebuild -scheme Chronoid -configuration Debug build 2>&1 | xcsift -w This is the key — Claude can iterate in a loop, read the compact errors/warnings, fix them, and verify again without burning tokens on Xcode's verbose output. Without this, the feedback loop falls apart. What the MCP server does: Once connected, you can just ask Claude things like: "Summarize my day" "How productive was I this week?" "What distracts me the most?" "Show me my deep focus sessions" "When are my peak productivity hours?" The MCP server exposes ~10 tools — daily summaries, app usage stats, productivity analysis, distraction patterns, focus block detection, interruption tracking, and more. All read-only, all local. No data leaves your machine. Setup is one config block: { "mcpServers": { "chronoid": { "command": "/Applications/Chronoid.app/Contents/Resources/chronoid-mcp", "args": [] } } } The video shows Claude summarizing my full workday — time per app, categories, timeline, and productivity insights — all from a single prompt. Chronoid has a 30-day free trial — no credit card required. You can try the MCP server right away. Would love to hear what other MCP integrations people are finding useful with their local tools, and how others are handling native development with AI. submitted by /u/tuanvuvn007 [link] [comments]

Is it worth it to switch from a Google AI Pro ($20) subscription to a Claude Pro subscription?

I currently use Gemini CLI with the $20 AI Pro subscription, but it sometimes does really stupid shit like trying to refactor the whole file when I only ask for a small change or fix. Or sometimes after a change, a whole function is missing, indentation gets ruined, etc. I've heard in many places now that Claude is much better at coding, but also that it's way more expensive. So, does the pro subscription even get me through an 8 hour workday as a dev working on small codebases or single scripts? Currently I'm working in C, but I'm also doing Python and web languages as well. submitted by /u/KevDotCom [link] [comments]