A cinematic AI project foundry with luminous glass project cards, planning boards, prototype schematics, and blue-and-amber workshop lighting.
YouTube connected · OAuth verified · 2026-05-19

YouTube Shorts Signal Lane

A visual field-note channel for turning strong AI images into short videos that can carry the Workshop's human/agent collaboration story beyond text posts.

Projects / YouTube

YouTube Shorts Signal Lane

Status: channel access connected Channel: AugmentedThinker Handle: @augmentedthinker Channel ID: UCHdJh8bMY8secEQeEBEbC1A

The AugmentedThinker YouTube account is now connected through a private OAuth token with broad YouTube-specific scopes. OpenClaw can inspect channel information and should be able to support uploads, metadata work, and channel operations that the YouTube Data API exposes.

This lane grew naturally from the Bluesky visual field notes. The daily Bluesky loop has been producing warm human-plus-agent images that feel closer to the Workshop's identity than generic AI dashboards. Christopher has started turning some of those images into short videos. YouTube Shorts can become the public surface for that format.

Current access

  • OAuth client: stored privately in .secrets/google-oauth-client.json.
  • YouTube token: stored privately in .secrets/youtube-oauth-token.json.
  • Verified API call: channel lookup succeeded for @augmentedthinker.
  • Current channel state: one subscriber and one existing video at time of connection.
  • Helper added: tools/youtube-oauth.mjs can refresh the local authorization flow if needed.

Operating idea

The first useful version should stay human-reviewed. OpenClaw can prepare a short video candidate, draft a title, draft a description, and suggest tags. Christopher approves before upload. After upload, the URL, title, and early signal should be logged.

Latest teach-one runbook: YouTube Shorts Pipeline Runbook: Reference Image to Published Short records the June 1, 2026 successful pipeline run, including the source folder inspection, TSX lessons, five fresh generated images, local ffmpeg assembly, YouTube upload, processing verification, and private logging pattern.

Near-term workflow

  1. Select a strong Bluesky-style image or generate a new image for video.
  2. Turn it into a short vertical video with light motion, atmosphere, or caption pacing.
  3. Draft title, description, tags, and visibility setting.
  4. Ask Christopher for approval.
  5. Upload through the YouTube API.
  6. Record the URL and any signal in a dedicated YouTube log.

Boundary: YouTube uploads, public metadata changes, profile/channel changes, and comments should remain approval-gated until Christopher explicitly defines a narrower autonomous routine.

Open question

The YouTube Data API should cover uploads and many channel/video operations. Profile image changes may still be controlled by Google or Brand Account surfaces rather than the YouTube API, so that should be tested separately before assuming full profile control.