Run Claude Code with Opus as the orchestrator and Sonnet as the implementation/review subagents — keeping the main session focused and cheap while delegating the heavy lifting to isolated workers.
.claude/
This PowerShell script allows you to bypass TPM 2.0, unsupported CPU, and memory checks enforced by the Windows 11 Upgrade Assistant and setup.exe from Windows installation media. It eliminates common upgrade blocks such as:
| site-functions # diff /usr/share/zsh/5.9/functions/_path_files /usr/local/share/zsh/site-functions/_path_files | |
| --- /usr/share/zsh/5.9/functions/_path_files 2024-10-01 00:10:49 | |
| +++ XX_path_files 2024-10-19 02:25:56 | |
| @@ -145,7 +145,9 @@ | |
| if [[ $#matcher -eq 0 && -o nocaseglob ]]; then | |
| # If globbing is case insensitive and there's no matcher, | |
| # do case-insensitive matching. | |
| - matcher=( -M 'm:{a-zA-Z}={A-Za-z}' ) | |
| + # work around bug in zsh 5.9 | |
| + #matcher=( -M 'm:{a-zA-Z}={A-Za-z}' ) |
These are my notes on how to build gamescope in Fedora 40
sudo dnf install SDL2-devel cmake gcc gcc-c++ git glm-devel glslang google-benchmark-devel hwdata-devel libX11-devel libXcomposite-devel libXcursor-devel libXdamage-devel libXext-devel libXfixes-devel libXmu-devel libXrender-devel libXres-devel libXtst-devel libXxf86vm-devel libcap-devel libdisplay-info-devel libdrm-devel libliftoff-devel libxkbcommon-devel meson ninja-build pipewire-devel stb_image-devel stb_image_resize-devel stb_image_write-devel vkroots-devel vulkan-loader-devel wayland-devel wayland-protocols-devel wlroots-devel xorg-x11-server-Xwayland-devel libavif-devel libseat-develStart by checking that there aren't any previous ssh keys inside the FIDO2 authenticator of your YubiKey. You can check if they exist by running the command below:
nix shell nixpkgs#yubikey-manager -c ykman fido credentials listIf the command above outputs a string mentioning "ssh" or "openssh", then you have already got a key generated and store on your YubiKey.
Before generating a new ssh key to store on your YubiKey you must consider which additional required authentication factors you want to use. Below you can see a table with the available factors and their corresponding command:
This article goes through the process of setting up a headless Qortal node using Vultr VPS, and setting up a minting account for the node.
This is extremely useful if you want to mint 24/7 without having your Desktop PC running at all times.
Register an account with Vultr (referral link, you get $100 credits): https://www.vultr.com/?ref=8976898-8H)
mkdir -p ~/.config && touch ~/.config/ssh-agent.pidssh-agent-manage.sh into your .bashrc or .bash_profile or similarkillall -9 ssh-agentThis snippet, when included in .bashrc, will ensure that your session has a working ssh-agent with all your ssh keys loaded into it. It does this without creating separate ssh-agent processes by:
| # Config file - inspired from https://gist.github.com/MateuszKubuszok/ede00892f818cf689d31c2f575e8be88 | |
| # Some tweaks to the status line | |
| set -g status-right "%H:%M" | |
| set -g window-status-current-style "underscore" | |
| # If running inside tmux ($TMUX is set), then change the status line to red | |
| %if #{TMUX} | |
| set -g status-bg red | |
| %endif |
Note that is a draft post. NOT checked by the full Routify team yet. Any feedback welcome! (You are looking at a major rewrite, this used to be more about Routify vs Sapper)
We are getting got a lot of questions about how Routify is different than Sapper. Rather than going into long comparisons about the differences with Sapper, I would like to explain the project goals of the Routify and Roxi projects. I hope this will make it clearer where things are going.
Now that we have released Routify 1.5, it's time to talk about Roxi.
In any non-trivial project, there is a need for a project structure. You've got routing, asset pipeline (CSS, images), data handling issues and more to deal with.