Claude Pro/Max plans expose a usage API at https://claude.ai/api/oauth/usage that returns two utilization counters:
five_hour.utilization — a rolling 5-hour window (well documented)seven_day.utilization — described as a "weekly" capThe seven_day object also contains a resets_at field. Monitoring this field over ~11 days (June 9–20, 2026) revealed that the "weekly" limit does not reset every 7 days — it resets every 72 hours.
Goal: a completely headless Linux box that presents a virtual display and streams 4K 120Hz HDR to a Mac/iPad over Sunshine → Moonlight, with nothing physically plugged into the GPU. This is a running log of how far that gets on current NVIDIA + KDE Wayland, what works, and exactly where it hits a wall.
TL;DR: HDR works. 4K60 works. Arbitrary native resolutions work. 120Hz does not — the NVIDIA driver refuses to bring up HDMI 2.1 FRL (or DP DSC) on a force-enabled connector that has no real sink doing the link handshake, so anything needing more than ~600 MHz TMDS
SYSTEM PROMPT:
Karpathy published his CLAUDE.md as a clean set of principles, then followed it with LOOPS.md on agent harness design. Both are correct. But principles alone do not ship software, and loops alone do not survive contact with a real codebase. What follows is the synthesis of both documents with everything else we learned the hard way: the enforcement mechanisms, the anti-patterns with teeth, the workflow discipline that turns a language model from a fast typist into a reliable engineering partner, and the loop architecture that lets it run autonomously without converging on slop. 35 rules across 6 tiers. Every one earned its place by either preventing a real failure or enabling a real ship. Nothing is theoretical.
The Linux kernel is written in C, so you should have at least a basic understanding of C before diving into kernel work. You don't need expert level C knowledge, since you can always pick some things up underway, but it certainly helps to know the language and to have written some userspace C programs already.
It will also help to be a Linux user. If you have never used Linux before, it's probably a good idea to download a distro and get comfortable with it before you start doing kernel work.
Lastly, knowing git is not actually required, but can really help you (since you can dig through changelogs and search for information you'll need). At a minimum you should probably be able to clone the git repository to a local directory.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
| ######################################################################################################################## | |
| # Script to Synchronize qBittorrent Listening Port with ProtonVPN assigned port on Windows. | |
| # | |
| # Description: | |
| # This PowerShell script automates the synchronization of qBittorrent's listening port with the | |
| # port number assigned by ProtonVPN's port forwarding feature. | |
| # | |
| # This fork: | |
| # - Fixing SQL-Lite import | |
| # - Fixing null checks |
| /* | |
| MIT License | |
| Copyright (c) 2024 Reda El Madini | |
| Permission is hereby granted, free of charge, to any person obtaining a copy | |
| of this software and associated documentation files (the "Software"), to deal | |
| in the Software without restriction, including without limitation the rights | |
| to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| copies of the Software, and to permit persons to whom the Software is | |
| furnished to do so, subject to the following conditions: | |
| The above copyright notice and this permission notice shall be included in all |