SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

OpenAI reinstates 5-hour Codex and Work usage limits for ChatGPT Plus users

0
·7 views

OpenAI has restored the five-hour usage limits for its Codex and Work features available to ChatGPT Plus subscribers. The move reverses a previous change to how these tools were made accessible to paying users. The update was reported on August 24, 2026, suggesting the company is recalibrating access to its more advanced capabilities. The reinstatement likely reflects efforts to manage server load or ensure fair usage across its subscriber base.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

macOS LaunchAgent Blocked from ~/Documents Due to Privacy Context, Not File Permissions

A zsh script that successfully listed the ~/Documents folder in macOS Terminal failed with an 'Operation not permitted' error when run as a LaunchAgent under launchd, despite identical user IDs and home directory paths. Testing on macOS 15.6.1 revealed that the access denial was tied to the process launch context, not file ownership or permission bits, since the LaunchAgent could read other directories owned by the same user. macOS enforces a privacy context for protected folders like Documents, Desktop, and Downloads, and processes started by launchd do not inherit the same privacy access granted to interactive Terminal sessions. A negative control path outside the protected folder succeeded in both contexts, confirming that chmod or ownership changes would not resolve the issue. Developers diagnosing similar failures are advised to compare access from both launch contexts, use a control path outside protected folders, and enable pipefail in zsh scripts to avoid masked errors from pipeline status misreporting.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Hosted vs Self-Hosted Log Search: How Small Teams Should Choose the Right Fit

Choosing an app log search solution for a small business involves evaluating operational burden, data control, and search depth — not just cost. Hosted log APIs offer the easiest setup for small teams, while self-hosted Loki suits those who already manage their own infrastructure and can handle upgrades and recovery. Elastic Cloud provides deeper search and observability features but may be excessive for teams with simple recent-log needs. Critically, log search alone cannot confirm that a scheduled job ran as expected — heartbeats, job records, or freshness metrics are needed for that. Price should factor into the decision, but only after assessing which option reliably delivers trustworthy signals without forcing a small team to operate a second complex product.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Loops vs Graphs: Why AI Agent Systems Need a Verification Layer in Between

A debate in the AI agent development community has emerged between two architectural philosophies: one treating agents as iterative loops and the other as interconnected graphs. Proponents of loops emphasize temporal, self-correcting behavior such as replanning and budget enforcement, while graph advocates focus on structural composition including parallel execution and supervision trees. Both approaches share a critical gap — neither addresses how to verify that the software components wired into these systems actually do what they claim. A proposed solution called HURCULES is designed to sit between code repositories and agent runtimes, compiling raw repos into verified capability packages with file-level evidence, provenance, security scans, and approval trails. The argument is that without such a verification layer, both loops and graphs remain vulnerable to unverified, potentially malicious, or hallucinated capabilities.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Developer shares hard lessons from deploying AI agents for real small business customers

A developer who spent a year building AI automation systems for small businesses has outlined the practical failures that emerge when AI agents meet real-world users. Unlike demos built with clean, cooperative input, actual customers send vague, typo-ridden, and contradictory messages that expose gaps in even well-designed prototypes. Silent pipeline failures, hallucinated policies from overconfident bots, and runaway API loops in multi-agent systems are among the costly problems the developer encountered after launch. Key fixes included logging unusual user inputs to spot failure patterns, building mandatory human-handoff paths, and placing hard caps on agent loops to prevent runaway costs. The developer also notes that framing AI projects around eliminating a specific manual task, rather than showcasing the technology, made projects easier to scope and sustain.

0 comments Read more at DEV Community