Version: 1.0.0 Protocol Version: 2024-11-05 Last Updated: 2026-01-10
Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.
Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1
- Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
- Select "Create new custom chat mode file"
I have found a way to build Windows container images without Docker - It doesn't use a Dockerfile though.
The way I got this to work is using crane from Google (https://github.com/google/go-containerregistry/blob/main/cmd/crane/doc/crane.md) which lets you append image layers to a base image. You can build Windows images on either Linux or Windows or inside of a container (Linux/Windows) - however, you'll need to build any artefacts (e.g. EXE, DLLs) on a Windows machine since this approach is using Crane to assemble a Windows container image on a Linux host (container).
Here is a quick PoC I did to prove it works (using Docker Desktop with Windows Container mode on my laptop):
dotnet --version
# 7.0.102| package common | |
| import ( | |
| "context" | |
| "fmt" | |
| "log" | |
| "path/filepath" | |
| "runtime" | |
| "dagger.io/dagger" |
| name: On push to develop | |
| on: | |
| push: | |
| paths: | |
| - '.env.test' | |
| - '.**.js' | |
| - '**.js' | |
| - '**.json' | |
| - '**.lock' | |
| - 'public/**' |
| package common | |
| import ( | |
| "context" | |
| "log" | |
| "dagger.io/dagger" | |
| ) | |
| // PublishToAzure performs a Dockerfile build on the provided repo and pushes to the |
Refactoring (or as i often annoyingly call it, "Furniture arranging") is a skill that once practiced enough, becomes second-nature, and in a lot of cases, very easy.
It often gets conflated with design, but they are separate activities.
Refactoring is just improving existing code and not changing behaviour, and it's usually very localised changes; tests shouldn't have to change. A lot of very helpful refactorings are simple to learn, easy to do (many are almost entirely automated by your IDE) but over time become hugely impactful to the quality of our system.
| launchctl unload /Library/LaunchAgents/com.microsoft.wdav.tray.plist | |
| sudo launchctl unload /Library/LaunchDaemons/com.microsoft.fresno.plist | |
| sudo launchctl unload /Library/LaunchDaemons/com.tanium.taniumclient.plist |
| package main | |
| import ( | |
| "encoding/json" | |
| "fmt" | |
| "os" | |
| "os/exec" | |
| ) | |
| func GetCmdOutput(cmd []string) []byte { |