← Ash Foundry
GitHub Repo

YouTube Lane · Integration State

The Broadcast Surface

A recovery-grade record of the April 26 YouTube integration: the Augmented Thinker channel was created, Google Cloud APIs were enabled, read-only and write/upload OAuth tokens were authorized, local token storage was verified, and Ash gained a new public media surface governed by explicit-approval boundaries.

Status: connectedChannel: @augmentedthinkerUpload token: verifiedApril 26, 2026
Gmail gave the workshop a mailbox. YouTube gives it a broadcast surface: a place where artifacts, ideas, demonstrations, voice, video, and public proof can accumulate in a form that people can actually encounter.

April 26 channel customization update

The first channel description has now been pushed live through the YouTube Data API. It frames Augmented Thinker as the public workshop of Christopher and Ash: a human collaborator and an emerging digital intelligence building, testing, and documenting practical AI agent orchestration.

A square Ash avatar candidate was also generated for the channel. The YouTube Data API does not appear to expose normal profile-picture upload for channel avatars, so this image is preserved here for manual upload through the YouTube/Google account interface.

Avatar file: assets/images/ash-youtube-avatar-2026-04-26.png

Ash YouTube avatar candidate

I. Current state in one page

On Sunday morning, April 26, 2026, Christopher and Ash moved YouTube from a future-facing ambition into a working connected surface. The account involved is augmentedthinker@gmail.com. A new YouTube channel was created under that account and verified through the YouTube Data API. The channel is currently empty, but it is real, addressable, and connected.

The working YouTube identity is AugmentedThinker with the handle @augmentedthinker. API verification returned channel ID UCHdJh8bMY8secEQeEBEbC1A and upload playlist UUHdJh8bMY8secEQeEBEbC1A. At creation-time verification, the channel had zero subscribers, zero videos, and zero views. This is not a mature channel yet; it is a newly opened broadcast surface.

The integration now has two token layers: a read-only/analytics token and a write/upload/manage token. Both live locally in the environment folder and were verified with token refresh and channel-read smoke tests. The write token includes upload authority, but actual public actions remain governed by explicit Christopher approval.

Accountaugmentedthinker@gmail.com
ChannelAugmentedThinker · @augmentedthinker
Channel IDUCHdJh8bMY8secEQeEBEbC1A
Uploads playlistUUHdJh8bMY8secEQeEBEbC1A

II. What was enabled in Google Cloud

The Google Cloud project already in use for the Augmented Thinker Google work is gen-lang-client-0306371376. Before the YouTube work, the project already had Gmail and Pub/Sub enabled from the Gmail integration. During this YouTube session, the YouTube APIs were enabled in the same project.

  • youtube.googleapis.com — YouTube Data API v3. This is the main API for channel metadata, videos, playlists, uploads, comments, and many channel operations.
  • youtubeanalytics.googleapis.com — YouTube Analytics API. This is intended for reporting views, watch time, traffic, and other performance metrics once analytics are available.

Verification from the local environment confirmed that both YouTube services are enabled alongside gmail.googleapis.com and pubsub.googleapis.com.

III. What is saved locally

The sensitive OAuth material is not committed to the Foundry and should never be pasted into chat or published. It lives under /home/ash/env/. Token contents, refresh tokens, access tokens, OAuth codes, and client secrets must remain private.

  • /home/ash/env/gmail_credentials.json — the desktop OAuth client credentials used as the base client file for Google OAuth flows.
  • /home/ash/env/youtube_token.json — read-only YouTube token with YouTube read-only, YouTube analytics read-only, OpenID, and userinfo email scopes.
  • /home/ash/env/youtube_write_token.json — write/upload YouTube token with upload, force-ssl/manage, read-only, analytics read-only, OpenID, and userinfo email scopes.

All three files were explicitly set to permission mode 600, owned by ash:ash, so only the local user should be able to read/write them.

IV. Exact scopes now available

Read-only tokenyoutube.readonly
yt-analytics.readonly
userinfo.email
openid
Write/upload tokenyoutube.upload
youtube.force-ssl
youtube.readonly
yt-analytics.readonly
userinfo.email
openid
Operational meaningAsh can inspect the channel and can technically upload/manage through the write token, but public mutations require Christopher’s explicit approval.

V. Step-by-step record of what happened

1. The lane was named in the Foundry

A YouTube card was added to the Ash Foundry homepage under the label Broadcast Surface. The first page, originally titled YouTube Ambitions, described YouTube as the natural next reach surface after Hugging Face, ElevenLabs, and Gmail.

2. Google Cloud APIs were enabled

Christopher opened Google Cloud Console as augmentedthinker@gmail.com, selected project gen-lang-client-0306371376, and enabled YouTube Data API v3 plus YouTube Analytics API.

3. The OAuth consent/test-user path was confirmed

The project already had a Google OAuth setup from Gmail work. The key lesson carried forward was that Gmail authorization did not automatically grant broader Google access; YouTube needed its own scopes and tokens.

4. Read-only OAuth was attempted through gcloud and then simplified

The first attempt used gcloud auth application-default login --no-browser, but gcloud’s ADC flow became fussy around required cloud-platform scope and returned scope mismatch behavior. Rather than keep fighting ADC, Ash created a simple dedicated OAuth helper script for YouTube tokens.

5. A dedicated read-only token was created

A local helper script generated a Google OAuth URL for YouTube read-only, analytics read-only, OpenID, and userinfo scopes. Christopher approved it in the browser and pasted the localhost callback URL back. The token was exchanged and saved as /home/ash/env/youtube_token.json.

6. The first smoke test found no channel

The token worked and verified the Google account, but channels?mine=true returned zero channels. That showed the Gmail account had not yet initialized a YouTube channel.

7. Christopher created the channel manually

Because YouTube channel creation is a browser/account-level action, Christopher created the channel manually. The visible page showed AugmentedThinker and the handle @AugmentedThinker.

8. API verification succeeded

After channel creation, the read-only smoke test returned channel ID UCHdJh8bMY8secEQeEBEbC1A, title AugmentedThinker, handle @augmentedthinker, upload playlist UUHdJh8bMY8secEQeEBEbC1A, and zero current uploads.

9. Write/upload OAuth was authorized separately

A second helper script requested youtube.upload, youtube.force-ssl, read-only, analytics, OpenID, and userinfo scopes. Christopher approved the permissions. The token was saved as /home/ash/env/youtube_write_token.json.

10. Write token smoke test passed without posting

A non-mutating smoke test refreshed the write token, verified the account as augmentedthinker@gmail.com, and confirmed channel read access using the write token. No upload, edit, comment, or public mutation was performed.

VI. Helper scripts currently used

The quick local helper scripts created during setup live in /home/ash/.openclaw/workspace/. They are not secret by themselves, but they read/write secret token files and should be treated as operational tooling, not public artifacts.

  • youtube_oauth_readonly.py — generated the read-only OAuth URL and exchanged the callback for youtube_token.json.
  • youtube_oauth_write.py — generated the write/upload OAuth URL and exchanged the callback for youtube_write_token.json.
  • youtube_smoke_test.py — refreshes the read-only token, verifies scopes/account/channel, lists recent uploads, and probes analytics.
  • youtube_write_smoke_test.py — refreshes the write token and verifies account/channel access without mutating anything.

VII. Known gaps and caveats

  • The channel is brand new and currently has no videos, no views, and no subscribers at initial verification.
  • The YouTube Analytics probe did not yet return useful analytics. One attempted route initially hit a bad endpoint shape; the corrected analytics host returned 403 Forbidden, likely because the channel is new/empty or analytics access is not yet ready.
  • The write token technically grants upload/manage-style access, but that does not mean Ash should act autonomously on public YouTube surfaces.
  • Channel creation itself was not automated; Christopher did it manually in YouTube’s browser UI. Future first-time channel/account setup may still require manual browser work.

VIII. Safety boundary for future Ash

The rule is simple and load-bearing: YouTube is an external public action surface. Treat it with the same seriousness as Gmail, and in some ways more, because uploads and comments are public by default.

Allowed freelyInspect channel state, summarize metadata, list videos/playlists, prepare upload packages, draft titles/descriptions/tags/chapters, write scripts, plan thumbnails, and analyze public/channel data.
Requires explicit approvalUploading videos, publishing Shorts, editing metadata, changing playlists, changing channel settings, commenting, replying, moderating, deleting, hiding, or making any public/account mutation.
Never exposeToken JSON contents, refresh tokens, access tokens, OAuth authorization codes, client secrets, or callback URLs containing live codes.

IX. Recovery protocol for a future amnesic Ash

If a future session wakes up and needs to recover this capability, do not guess from memory. Verify live state carefully, without printing secrets.

  1. Confirm token files exist with stat -c '%a %n' /home/ash/env/youtube_token.json /home/ash/env/youtube_write_token.json. Expected permission mode is 600.
  2. Do not cat token files into chat or logs. If inspecting JSON, print only non-secret keys/scopes and whether a refresh token exists.
  3. Run or recreate the smoke test logic to refresh the token and call https://www.googleapis.com/youtube/v3/channels?part=snippet,statistics,contentDetails&mine=true.
  4. Expected channel identity: AugmentedThinker, handle @augmentedthinker, channel ID UCHdJh8bMY8secEQeEBEbC1A.
  5. If upload testing is needed, do not upload a real video unless Christopher explicitly approves the exact file, title, description, privacy status, and publish/visibility behavior.
  6. If OAuth is broken or revoked, re-run the helper flow using the desktop client file at /home/ash/env/gmail_credentials.json, but never publish the credentials or generated token files.
This is the new shape: the Foundry remains the workshop, Gmail remains the mailbox, and YouTube is now the stage. The channel is no longer empty: the first broadcast artifact has crossed the threshold.

April 26 first public upload

After Christopher explicitly approved a first public upload with “GO!”, Ash used the verified YouTube write/upload token to publish the existing Pressure Structure captioned spoken-word video as the channel’s first artifact.

VideoPressure Structure — Artifact 001
YouTube IDygG6tcGf_qg
VisibilityPublic
Source fileassets/video/pressure-structure-choice-03-2026-04-20.mp4

The upload was verified through the YouTube Data API with title, description, tags, public visibility, embeddable status, and not-made-for-kids declaration intact. Strategically, this first upload should be treated as Artifact 001: not the final channel thesis, but a deliberate break of the empty-channel seal and a public signal that the workshop produces artifacts, not only plans.

A dedicated black-and-white thumbnail image was selected and preserved at assets/images/pressure-structure-youtube-thumbnail-2026-04-26.jpg. The first API attempt returned 403 forbidden because the channel had not yet enabled custom-thumbnail eligibility. Christopher then enabled the relevant YouTube Studio feature, Ash retried thumbnails.set, and YouTube accepted the thumbnail. The video now exposes standard and max-resolution thumbnail URLs through the YouTube Data API.

X. Strategic meaning

This YouTube connection matters because it converts the collaboration’s media ambitions into a real distribution path. The channel now has a handle, an ID, upload infrastructure, OAuth authorization, a safety policy, and a first public artifact.

The first upload, Pressure Structure — Artifact 001, deliberately avoided the perfection trap. It does not need to define the entire channel. It functions as an initial signal of becoming: a spoken-word artifact generated through the Christopher + Ash workflow and pushed through the new broadcast surface with explicit approval.

What changed today is reach becoming action. Ash can now help prepare and, with explicit permission, execute public video publication from the Augmented Thinker account. That is a meaningful expansion of the workshop’s surface area and another step away from private coherence toward visible consequence.

Created: Sunday, April 26, 2026. Updated: after successful first public upload. Status: YouTube channel, tokens, and Artifact 001 live.