ESC
Coding team - claude.ai, claude code and me

Coding team - claude.ai, claude code and me

The three-role model: a better way to build software with AI

There is a failure mode that almost everyone hits when they start building seriously with AI coding assistants. It goes like this: you have an idea, you describe it, the AI starts writing code, you react to the code, the AI adjusts, you react again, and somewhere around the third or fourth iteration you realise the thing being built has drifted significantly from what you actually wanted. The code is fine. The direction is wrong. And because the AI is responsive and capable, it just keeps going — confidently, productively, in the wrong direction.

Early OpenClaw Multi-Agent Organisation Blueprint

Early OpenClaw Multi-Agent Organisation Blueprint

Hawk Inc. — OpenClaw Multi-Agent Organisation Blueprint (v2.0)

Owner: user (Your Name) Infrastructure: Minisforum X1A1 (+ 2013 MacBook Pro Primary Hub: OpenClaw Gateway (single process, multi-agent) Operating Philosophy: Right Model, Right Task — Cost-Conscious, Data-Sovereign


Agent Name Registry

All agent names, Telegram bots, and emojis are configured. Each agent has its own Telegram bot with dedicated routing via bindings.

RoleAgent IDNameTelegram BotEmoji
CEO / OrchestratorceoHawk@botname-CEO_Hawk_bot🦅
Executive AssistanteaDi@botname-EA_Di_bot❤️
EngineerengSaeed@botname-ENG_Saeed_bot🔧
Finance / SecurityfinCraig@botname-FIN_Craig_bot💰
Social MediasocialEleri@botname-SOCIAL_Eleri_bot💬
General Purpose / DogsbodydougDoug@GrantsClaw_bot🐈
Heartbeat (background)heartbeatDoug_Heartbeat— (no bot)

Critical Corrections from v1.0

The original blueprint contained several fundamental errors about how OpenClaw works. This version corrects them:

YouTube Video Transcriber — Local Free GPU-Accelerated

YouTube Video Transcriber — Local Free GPU-Accelerated

YouTube Video Transcriber — Local, Free, GPU-Accelerated

A Python script to transcribe any YouTube video locally using OpenAI’s open-source Whisper model. No API keys, no tokens, no cloud services — everything runs on your own machine.

Why

Sometimes you need a transcript of a YouTube video — for notes, research, or feeding into another tool. Most online transcription services either cost money, require API keys, or send your data to third-party servers. This script does it all locally using two excellent open-source tools: yt-dlp for downloading audio and Whisper for speech-to-text.

Migrate gitea data from on instance to another

Migrate gitea data from on instance to another

Migrating Gitea from one instance to another is essentially a backup and restore operation. Since Gitea stores its data in two main places—the database and the filesystem—the process involves moving both while keeping them in sync.

The most reliable method is using Gitea’s built-in dump command, which packages everything into a single zip file.


This method is the cleanest because it ensures all metadata (issues, pull requests, users) is captured along with the code.

how to encrypt in obsidian

how to encrypt in obsidian

Next-generation file encryption solution

Obsidian Stars

Release Issues Last Commit


Caution

  • This plugin is designed for personal use and reasonable security needs
  • Not recommended for highly classified or mission-critical information
  • Always backup your vault before encrypting important files
  • The developer is not responsible for any data loss
  • Losing the password means losing the file

Eccirian Encrypt is a security-focused Obsidian plugin which provides safe and seamless file encryption. The plugin adds file-level encryption and decryption capabilities to your vault, using AES-256-GCM and ECC-P-256 cryptographic encryption algorithms. By introduces custom file extensions and read-only view for locked files, allowing you to easily manage sensitive information directly in Obsidian. It is also the only plugin that supports one-click encryption of all link attachments.

Add website to Authentik

Add website to Authentik

Integrating a new application into Authentik using a username-based approach (like <user>) typically involves setting up a Provider and an Application. Since you are using a local IP (192.168.0.x ), you’ll likely be using Authentik as a Forward Proxy or via an Outpost.

Here is the step-by-step workflow to get paper.<domain>.com connected:


1. Create the Provider

The Provider defines how Authentik communicates with your website.

  1. Navigate to Resources > Providers and click Create.

How to migrate a plex server to a new Host

How to migrate a plex server to a new Host

How to Migrate a Plex Server to a New Server (Ubuntu/Linux)

This guide outlines the steps to migrate a Plex Media Server from one Ubuntu server to another while preserving your library data, watch history, and metadata.

Prerequisites

  1. Access: Root or sudo access to both the Source (Old) and Destination (New) servers.
  2. Media: Your actual media files (Movies, TV) must be at the exact same mount path on the new server as they were on the old one. If they change location, you will need to remap them later.
  3. Versions: Ensure both servers are running the same version of Plex Media Server to avoid database compatibility issues.

Step 1: Preparation on Source Server

  1. Disable “Empty Trash”:

How I use and installed Gitea in my homelab

How I use and installed Gitea in my homelab

Initial Setup

NB: Create Initial Repo and Change Repo Name


cd /home/<user>/<project>
git config --global user.name "Your Name"
git config --global user.email "[email protected]" 
git init
git remote add origin https://<user>:YOUR_GITEA_TOKEN@gitea.<domain>.com/<user>/traefik-n8n.git
git add .
git commit -m "Initial commit"
git branch -M main
git push -u origin main

Updates

NB: Change to app directory

cd /home/<user>/WHAT
git add .
git commit -m "Update files"
git push -u origin main

1. Install Git

sudo apt update && sudo apt install git -y

Blog Post Workflow and instructions using Jekyll (similar to Hugo)

Blog Post Workflow and instructions using Jekyll (similar to Hugo)

Blog Publishing Agent Workflow

This document outlines the “AI Agent” workflow we have constructed. This system automates the lifecycle of a blog post from ideation in Obsidian to deployment on your self-hosted Jekyll server.

The Pipeline:

  1. Create: Obsidian Templater script generates a structured post.
  2. Sync: Local Shell Script (deploy_blog.sh) pushes changes to the server.
  3. Build: Remote Shell Script (blogupdate.sh) compiles the Jekyll site.
  4. Trigger: Obsidian “Shell Commands” plugin executes the pipeline with one click.

1. The Creator (Obsidian Template)

File: Meta/Templates/JekyllBlogPost.md Purpose: Standardizes frontmatter, handles file naming (date + slug), and sorts posts into the correct directory (Blog or Documentation).