Verification cutoff: September 2, 2026, daily edition.

Executive Summary

Claude Fable 5.1 is now generally available, including in GitHub Copilot, but the Copilot integration retains prompts and outputs by default to operate Anthropic’s safety classifiers. That makes the rollout a policy decision before it is a model-picker decision. Also today, GitHub is running a scheduled brownout for outdated self-hosted Actions runners ahead of September 25 enforcement. A smaller but immediately useful release adds image and video uploads to GitHub CLI issue and pull-request workflows.

Action Queue

1. Review Claude Fable 5.1 retention before enabling it in Copilot

Urgency: This week
Importance: ★★★★★

What it is: Anthropic released Claude Fable 5.1 on September 1 for coding, knowledge work and long-running tasks. GitHub has made it available to Copilot Pro+, Max, Business and Enterprise customers. GitHub says that, unlike most other Claude models in Copilot, Fable 5.1 requires data retention by default: Anthropic retains prompts and outputs to operate safety classifiers, though it says the retained data is not used to train its models. Eligible enterprise customers can receive a temporary zero-data-retention exemption through the end of 2026 while Anthropic rolls out Enterprise Frontier Safeguards.

Why it matters: Model quality does not erase data-governance obligations. Code, issue context and repository material can enter prompts during agentic work, so administrators and users should understand the retention path before enabling the model for institutional, student or private-repository work.

Recommended action: Read GitHub’s retention notice before selecting or enabling Fable 5.1. If policy permits a trial, use a disposable or public test repository with no student records, credentials, unpublished institutional material or private client data. Compare one fixed coding task against the current approved model and record output quality, runtime, usage cost and disclosure behavior. Business and Enterprise administrators should leave the model policy off until retention has been reviewed.

Verified active: September 2, 2026; Anthropic’s launch and GitHub’s Copilot availability notice were checked.
Deadline: No fixed deadline; review before first use. The temporary eligible-enterprise zero-retention exemption runs through December 31, 2026.
Cost: Claude API list pricing is $10 per million input tokens, $50 per million output tokens and $0.25 per million cache-read tokens. In Copilot it is billed at provider list pricing under usage-based billing and requires an eligible Pro+, Max, Business or Enterprise plan.
Requirements: An eligible Claude or GitHub Copilot account; administrator enablement for Copilot Business and Enterprise; an approved data-handling policy; and a non-sensitive evaluation repository.
Official action: Anthropic’s Fable 5.1 launch, pricing and safeguards · GitHub Copilot availability and retention notice

2. Check self-hosted Actions runners during today’s brownout

Urgency: Immediate
Importance: ★★★★☆

What it is: GitHub’s second Enterprise Cloud brownout for outdated self-hosted Actions runners runs today, September 2, from 11:00 a.m. to 3:00 p.m. Eastern (10:00 a.m.–2:00 p.m. Central). GitHub requires version 2.329.0 or later for registration and requires runners with automatic updates disabled to stay within 30 days of current releases. Full enforcement begins September 25.

Why it matters: An old runner can leave workflows queued or unable to register. The brownout is a controlled opportunity to find stale infrastructure before permanent enforcement.

Recommended action: First determine whether any organization or repository actually uses self-hosted runners. If so, inspect today’s workflow annotations and runner versions, update installation scripts and cached images, and upgrade or recreate stale runners. No action is needed for repositories that use only GitHub-hosted runners.

Verified active: September 2, 2026; GitHub’s official enforcement schedule was checked.
Deadline: Today’s brownout is 10:00 a.m.–2:00 p.m. Central; full enforcement begins September 25, 2026.
Cost: No separate charge for the version check or runner software. Normal infrastructure and GitHub Actions plan costs still apply; no universal regular price applies.
Requirements: GitHub organization or repository administration access and at least one self-hosted Actions runner.
Official action: GitHub’s self-hosted runner enforcement timeline and upgrade guidance

3. Add screenshots directly from GitHub CLI

Urgency: No deadline
Importance: ★★★☆☆

What it is: GitHub CLI 2.99.0 adds a repeatable --attach flag to issue and pull-request create, edit and comment commands. It uploads PNG, JPEG, GIF, WebP, SVG, MP4, MOV or WebM files and inserts them into the Markdown body. A #description suffix supplies alt text.

Why it matters: Reproduction screenshots, rendered-page comparisons and short bug videos can now stay in terminal-based workflows. The same capability lets coding agents show visual evidence instead of only describing a result.

Recommended action: Update gh, then test with a non-sensitive screenshot and explicit alt text: gh issue comment --attach './screenshot.png#Description of the visible result'. Review every attachment for student information, credentials, private URLs and other unintended disclosure before uploading.

Verified active: September 2, 2026; GitHub’s September 1 general-availability notice was checked.
Deadline: None.
Cost: Free across all GitHub plans. Image and GIF uploads are limited to 10 MB; video is limited to 10 MB on Free plans and 100 MB on paid plans.
Requirements: GitHub CLI 2.99.0 or later, authentication through gh, repository write access and a supported local media file. GitHub Enterprise Server is not supported in this release.
Official action: GitHub CLI media attachment announcement and examples

GitHub’s official example shows gh issue comment --attach uploading a local screenshot and returning the new comment URL.

AI

Anthropic says Fable 5.1 is the same underlying model as the restricted-access Mythos 5.1, with different safeguard levels. Its API input and output prices match Fable 5, but cache reads fell to $0.25 per million tokens—75% lower—which Anthropic estimates reduces typical workload cost by about 25% and highly agentic workload cost by as much as 45%. These are vendor measurements; a bounded evaluation on representative work is more useful than adopting benchmark claims at face value.

Anthropic also reports that Fable 5.1 can perform defensive vulnerability discovery with fewer false-positive safeguard interventions, while penetration testing, exploit generation and binary vulnerability scanning remain redirected to other models. That boundary should be tested against the actual tasks an organization permits rather than inferred from the model name.

GitHub Discoveries

The new CLI attachment path supports gh issue create, gh issue edit, gh issue comment, gh pr create, gh pr edit and gh pr comment. If a Markdown body already references a local path, gh rewrites it to the uploaded asset and preserves the alt text. This is especially useful for web-development regressions and visual verification, provided attachments are screened before upload.

Linux & Self-Hosting

The Actions change matters only to self-hosted runners; GitHub-hosted runners are outside this enforcement. For self-hosted Linux runners with automatic updates disabled, merely reaching version 2.329.0 is not a permanent fix. GitHub says any release starts a 30-day currency window, and critical security updates can pause job queuing until installed. Treat runner images and bootstrap scripts as maintained infrastructure.

Newsletter Highlights

TLDR Dev’s September 2 edition surfaced the Fable 5.1 release. The consequential availability, retention, pricing and safeguard claims above were verified against Anthropic and GitHub’s original notices.

PKb Candidates

• AI model intake record: availability, permitted data classes, retention, training use, administrator policy, price, safeguards, evaluation task and rollback choice.
• Self-hosted runner maintenance checklist: inventory, version, auto-update status, network reachability, base-image age, workflow annotations and enforcement dates.
• Visual issue-reporting checklist: crop sensitive information, remove credentials and private URLs, add useful alt text, verify file size and preview before submission.

Trends Worth Watching

Model selection is becoming a combined capability, cost and data-governance decision. “Available in the picker” does not mean “approved for every repository.” At the same time, developer agents are gaining richer ways to submit evidence, increasing the need to inspect generated screenshots and recordings before they become durable repository attachments.

Related PTIR Coverage

• Daily Briefing — August 30, 2026 — Copilot retention policy and shared-agent sessions.
• Daily Briefing — August 22, 2026 — Codex model retirement and accessibility verification.

Sources Consulted

Anthropic’s Fable 5.1 launch and system information; GitHub’s Fable 5.1 Copilot notice, Actions runner enforcement schedule and GitHub CLI media announcement; selected technology newsletters; the latest PTIR edition; and read-only searches of the legacy recipient stream, Spam and Trash.