Three official dev announcements, each read at the source: Claude message threads, Expo's guide to the Apple Developer Program, and short-lived tokens in GitHub Desktop.
Three official announcements in development today: a new Claude Messages API feature from Anthropic, Expo's guide to Apple's developer program for iPhone apps, and a sign-in token change in GitHub Desktop. We opened each source and checked what it says.
| Claude message threads | Public beta | Stops resending the whole conversation on every request |
| Expo's Apple developer program guide | November 2 | Splits out the moments you need the $99 a year |
| GitHub Desktop short-lived tokens | November 2 | Leaked tokens stay usable for less time |
Claude message threads (public beta). Anthropic put message threads into the Messages API on the Claude Platform as a public beta. A coding agent can make hundreds of requests in one session, and every request resends all earlier messages and tool results. Once a conversation reaches hundreds of thousands of tokens, that resending is time before Claude starts to answer. With a thread parameter, only the first request carries the whole conversation. Each later request sends the new messages and the ID of the previous response.
- Time to first token (median)35%
Drop for Claude Code requests of 500k to 1M tokens
- Thread expiry5min
After the last request, then the full conversation is sent again
Anthropic says message threads is on by default for most Claude Code users, and for requests of 500k to 1M tokens the median time to first token fell by about 35%. That is the maker's own number, and we cannot say whether your agent would see the same drop before trying it. Threads are held in server memory, encrypted, and are not written to disk.
- First request → Thread starts
- Thread starts → Next request
- Next request → 5 minutes after the last request
- 5 minutes after the last request → After expiry, the full conversation starts a new thread (after 5 minutes)
Requests get smaller, but Claude still reads the full conversation every turn, so token usage stays the same, with standard token rates and existing rate limits. What shrinks is waiting time, not the bill. It is available in public beta on the Claude Platform, on AWS, in Microsoft Foundry and in Anthropic-managed Claude models on Google Cloud.
Expo's Apple developer program guide (November 2). Expo points out that Apple's $99 a year Developer Program is not the entry fee for iPhone development. Running an Expo Go app on your own iPhone needs no Apple account at all, and with a Mac a free Apple account is enough to install a development build. The post walks the road in three levels, with what each one needs, what it unlocks and where it stops.
| Expo Go | An iPhone and any computer | Develop with Fast Refresh and most of the Expo SDK | $0 |
| Development build | A Mac and an iPhone | Add native libraries and install on your own iPhone | $0 |
| Cloud build | No Mac, a real iPhone | Build and sign in the cloud with Expo Build | $99 a year |
| Distribution | An app for other people | TestFlight, internal distribution, the App Store | $99 a year |
Free signing has clear limits. The app expires after 7 days, you get 3 apps per device and up to 3 registered devices. Remote push notifications, in-app purchases, Sign in with Apple, NFC, iCloud and Apple Pay need the paid membership, even while developing.
- Free-signed app lifetime7days
Rebuild after that
- Apps per device3apps
Installable with free signing
The $99 opens five things: TestFlight (up to 10,000 external testers) and internal distribution, cloud signing, remote push, Apple capabilities such as in-app purchases, and the App Store. Development profiles from a paid team last up to a year, so you also stop rebuilding every week.
GitHub Desktop short-lived tokens (November 2). Eligible accounts that sign in to GitHub Desktop 3.6.10 or later can now get short-lived, automatically refreshing authentication tokens. A leaked token stays usable for less time, and Desktop refreshes it for GitHub API requests and Git operations.
It is not open to everyone yet. The rollout is gradual on github.com, including GitHub Enterprise Cloud, and GitHub Enterprise Server is not part of it. Existing sessions stay signed in after you upgrade, existing tokens are not migrated automatically, and short-lived tokens are issued at sign-in once the rollout reaches your installation. The post does not say how short the tokens are.
The three reach different people. Message threads is for teams building their own agents, and the only distinction to keep is that it cuts waiting time, not the bill. Expo's guide is most useful to someone who has not started on iOS yet. In their place, I would build with Expo Go first and enroll when push or distribution becomes necessary. GitHub Desktop needs no setting change: update, sign in again, and check whether your account got the new tokens.
- Make long-running agents faster with message threads, Claude
- Apple Developer Program explained: free vs paid, Expo blog
- GitHub Desktop adds short-lived authentication tokens, GitHub Changelog