Simon Massey simbo1905

OpenCode Desktop v1.1 on Windows 11 with custom MSYS2 install in user folder

Prerequisites

Download and install MSYS2 into C:\Users\UserName\MSYS2. Confirm the installation has msys2.exe, ucrt64.exe, and other shell variants present. Open msys2.exe directly and run pacman -S git to verify pacman works and git installs correctly. Verify you can use both tools in the shell before proceeding.

Locate your OpenCode v1.1 installation. Find OpenCode.exe at a path like C:\Users\UserName\AppData\Local\OpenCode\OpenCode.exe. Confirm opencode-cli.exe is also present in the same directory. Test the CLI by running opencode-cli.exe web to ensure it boots correctly.

Shut down OpenCode. Close the web interface and any running OpenCode processes.

📊 Line Histogram — The File Profiler You Didn't Know You Needed

What If You Could See Your Data Before It Floods Your Context Window?

You know that moment when you asked your agent to check the data and before you can tell it not to eat the ocean it enters Compaction.

Yeah. We've all been there.

The Problem

🤯 Huge database dumps with unpredictable line sizes

RFC: Discoverable and DRY Documentation Architecture for Agents and Humans

Status: Proposed Author: Simon Massey Context: Hybrid Human/Agent Repositories

1. Abstract

This Request for Comments (RFC) defines a strict, normative standard for repository documentation architecture. It addresses the "documentation problem" of staleness, duplication, and high cognitive load for autonomous agents. The architecture mandates a single source of truth, explicit linking (no orphans), and a flat directory structure optimized for discoverability via ls, utilizing naming conventions over directory nesting.

2. Core Philosophy

OPENCODEAGT(1)

NAME

opencodeagt - One-shot execution of Opencode agents from markdown files

SYNOPSIS

opencodeagt [AGENT_NAME] [FLAGS...]

DESCRIPTION

opencodeagt facilitates a workflow for using custom Opencode agents defined in the .opencode/agent/ directory.

md2gist - CLI Tool to Sync Markdown to GitHub Gists

A Python CLI utility that uploads local Markdown files to per-branch GitHub Gists, maintaining a registry of mappings. Ideal for sharing analysis, reports, and documentation directly from your terminal.

Key Features

Branch-Specific Gists: Automatically creates or updates a unique Gist for each git branch.
Registry Mapping: Maintains a central Gist registry mapping org/repo/branch to specific Gist URLs.
Smart Updates: Adds new files or updates existing ones in the target Gist.
Format Options: Outputs Markdown or HTML links for easy pasting into PRs or other docs.

md2pdf (Markdown → PDF/HTML)

A small, self-contained CLI script that converts Markdown to PDF (or HTML) using WeasyPrint, with optional Mermaid diagram rendering via the public mermaid.ink API.

This gist contains:

md2pdf — the converter script (PEP 723 / uv run --script compatible)
professional.css — a clean corporate documentation theme
whimsical.css — a deliberately non-professional, high-contrast test theme (useful to prove CSS is being applied)

Usage

md2gist

Upload markdown files to per-branch GitHub gists with automatic registry mapping.

What It Solves

Provides a workflow for storing per-branch analysis, reports, and documentation in GitHub gists automatically organized by org/repo/branch. Each feature branch gets its own gist for test results, analysis notes, or generated reports.

How It Works

CLAUDE.md

To: Graduate Internship Programme

From: Team Manager

Subject: Termination of Intern claude-opus-4.5 for Unsafe Working Practices

	#!/bin/sh
	set -eu

	usage() {
	cat <<'EOF'
	aws_sso_env.sh - Print AWS env exports from an SSO profile

	Usage:
	bin/aws_sso_env.sh <profile>

	/* CSS styles extracted from README.md.pdf */

	body {
	font-family: "SFNS", "Menlo", "Monaco", monospace;
	background-color: #A0A0A0;
	color: #24292e;
	line-height: 1.5;
	}

	h1, h2, h3, h4, h5, h6 {