New AI projects on Hugging Face or GitHub, May 31 to June 1 2026

Two days, two records that carry a real date. A Sunday with an empty commit log, and a Monday-night release whose load-bearing change is 37 lines across two files. Here is the window read from the dated record, not the trending page.

Matthew Diakonov, Written with AI

Published June 19, 20268 min read

Direct answer, verified 2026-06-19

Neither Hugging Face nor GitHub publishes a dated "new projects" list; both order discovery by a rolling trending score, not by calendar date. In this 48-hour window the one notable model launch was MiniMax M3 on June 1, and it shipped API-only: the weights were promised on Hugging Face about ten days later, so nothing downloadable dropped on either day. The dated, downloadable change you can read commit by commit is Fazm v2.9.58, tagged June 1, 2026, a 37-line two-file fix. May 31 itself was a Sunday with zero commits. Source: github.com/mediar-ai/fazm.

Why "projects on May 31 or June 1" has no clean answer

People search this expecting a dated changelog for the whole ecosystem. There is not one. Hugging Face ranks models, datasets, and spaces by a trending score that decays over hours; GitHub Trending does the same for repositories. Both answer "what is popular right now," which drifts every time you reload. The records that genuinely pin to a calendar day are narrower: a tagged release, a commit timestamp, a model-card revision. So the honest way to read a two-day window is to pick records that carry a real date and read them, instead of screenshotting a trending list that will look different tomorrow.

For this window the most-cited launch was MiniMax M3, announced June 1, 2026. It is a coding model with a sparse-attention architecture and a 1-million-token context window, and the company reported 59.0 on SWE-Bench Pro. But it launched as an API. The open weights were promised on the company's Hugging Face page about ten days out, so on May 31 and June 1 there was no file to pull and the benchmark numbers were vendor self-reports with no independent scores yet. That is the whole "new on Hugging Face" story for the window: a promise, not a download.

The window in numbers, from one repo's git log

This running series tracks one open-source macOS agent, Fazm, day by day, because a single repo gives you something the ecosystem-wide trending page cannot: exact timestamps you can re-run yourself. Here is the May 31 to June 1 window straight from git log.

0Commits on May 31 (Sunday)

0Commits on June 1, all after 19:56 PT

0Lines changed in the v2.9.58 fix

0Files touched (Swift + TypeScript)

May 31 was a Sunday: nothing was pushed between the v2.9.57 release on May 30 at 17:50 Pacific and the first June 1 commit at 19:56. Then four commits landed in seventeen minutes that evening and shipped as v2.9.58. An empty day is not a non-event; it is a maintainer resting, and it tells you the unit of a "new project" is a release, not a calendar square.

The bug v2.9.58 closed: a chat that hangs when your login expires

The load-bearing change of June 1 was not a feature. It was a fix for a failure mode that only shows up in long sessions: you are mid-query in a popped-out chat window, your Claude OAuth token quietly expires, and the window sits on a loading spinner that never resolves. No error, no re-auth prompt, just a frozen chat. The fix makes the window do the obvious thing: drop the spinner and show the sign-in-again message the moment auth becomes required.

Pop-out chat when Claude OAuth expires mid-query

OAuth expires mid-query. The bridge enters an indefinite wait loop, so isSending never flips back to false. The detached window's post-query handler is wired to that flip, so it never runs.

Spinner stays up indefinitely
No error and no re-auth prompt surfaces
Resolves only on flow.complete or the 10-minute OAuth timeout

Reading the fix at the line level

No roundup of this window reads a dated change line by line, because most of what they cover (an API-only model) has no public diff to read. This one does. v2.9.58 is two commits totaling 37 lines. The Swift side, commit 739e2b57, adds 22 lines to ChatQueryLifecycle.swift:

ChatQueryLifecycle.swift

The subtle half is the second commit. The flag isClaudeAuthRequired could already be true from a warmup 401 that fired before any real query was in flight. A SwiftUI subscription only reacts to a change, so if the flag is already true when you send your query, there is no transition and the spinner-clear above never runs. Commit 593b7ce8 adds 15 lines to acp-bridge/src/index.ts so that when an auth flow is already running, the bridge re-emits auth_required for the new trigger session, re-publishing the flag and forcing the transition the UI needs. Two signals, one for each layer: clear the spinner on the edge, and make sure the edge actually fires.

37 lines

“The unit of a new AI project is rarely a calendar day. It is a release, and a release is the accumulated decisions of the days before it, frozen at one timestamp.”

Fazm v2.9.58, tagged June 1, 2026

Why a 37-line fix is the better answer than a trending screenshot

If you came here to find the model everyone launched, the answer is MiniMax M3, and it was not downloadable yet. If you came to find something new you could actually run and read on May 31 or June 1, the answer is a desktop agent release and its diff. That is not a consolation prize. A token expiring mid-session is exactly the kind of failure that wrappers around Claude Code exist to handle, and watching a project fix it in 37 reviewable lines tells you more about whether to trust the tool than any benchmark a vendor self-reports.

Fazm is that wrapper: it runs the real Claude Code agent loop (and Codex) over ACP inside a native macOS app, with sessions that survive a restart, one-click chat forking, and no auto-compacting of context. The OAuth-expiry fix is one small entry in a public log you can read the same way for any other day. See the May 31 read for the empty Sunday on its own, or the June 1 to 2 read for the full MiniMax M3 story and how to point a working agent at an API-only model the day it drops.

Want to read your own agent's commit history this way?

Fifteen minutes on how Fazm wraps Claude Code with persistent sessions, forking, and no auto-compacting, all in a public repo you can audit.

Questions people ask about this window

Frequently asked questions

What new AI projects appeared on Hugging Face or GitHub on May 31 or June 1, 2026?

Neither platform publishes a dated release list. Models, datasets, papers, and repositories surface continuously, ordered by a rolling trending score rather than by calendar date, so there is no canonical "things launched on May 31" or "June 1" page to read. Two records in this window do carry exact dates. The notable model launch was MiniMax M3, announced June 1, 2026, but it shipped API-only: the company said open weights and a technical report would follow on its Hugging Face page within about ten days, so nothing downloadable dropped on either day. The dated change you can actually read commit by commit is Fazm v2.9.58, tagged June 1, 2026 on github.com/mediar-ai/fazm: a two-commit, 37-line fix. May 31 itself was a Sunday with an empty commit log.

So nothing downloadable shipped on May 31 or June 1, 2026?

On May 31, no. In the open-source macOS agent this running series tracks day by day, the commit log between the v2.9.57 release on May 30 at 17:50 Pacific and the first June 1 commit at 19:56 is empty: May 31 was a quiet Sunday. On June 1, the downloadable thing was an application release, not a foundation model. Fazm cut v2.9.58 that evening, and the headline model of the window (MiniMax M3) was reachable only through an API. If you want a file you could pull on June 1, the honest answer is the v2.9.58 build and its source diff, not model weights.

What is MiniMax M3 and was it actually open source on June 1, 2026?

MiniMax M3 is a coding-focused model with a sparse-attention (MSA) architecture, a 1-million-token context window, and native multimodality. On June 1 it was reachable only through the company API and third-party routing services. The promised open weights had not been released at launch; MiniMax said the weights and a technical report would land on its Hugging Face page within roughly ten days. So on June 1 it was an open-weight model in intent and a closed API in practice. MiniMax reported 59.0 on SWE-Bench Pro, ahead of its cited GPT-5.5 and Gemini 3.1 Pro figures, but those are vendor self-reports and independent scores were not published at launch. For the full read on M3, see the companion page on the June 1 to 2 window.

What did Fazm v2.9.58 actually fix on June 1, 2026?

A chat that hangs forever when your Claude OAuth token expires in the middle of a query. The fix is two commits. 739e2b57 ("Fix chat hang when Claude OAuth expires mid-query") adds 22 lines to Desktop/Sources/FloatingControlBar/ChatQueryLifecycle.swift: a subscription to isClaudeAuthRequired that clears the loading spinner and surfaces the auth message the moment auth becomes required while a pop-out chat is still loading. 593b7ce8 ("Fix query hang by re-emitting auth_required during active auth flow") adds 15 lines to acp-bridge/src/index.ts so that when an auth flow is already running, a fresh auth_required is re-emitted for the new trigger session. Together that is 37 lines across two files, tagged as v2.9.58 at roughly 20:13 Pacific.

Why did the chat hang at all? What was the root cause?

A missing state transition. The detached (pop-out) chat window finishes a query by subscribing to isSending and running its post-query handler when isSending flips back to false. But when OAuth expired, the bridge entered an indefinite wait loop, so isSending never flipped false and the post-query handler never ran. Compounding it, isClaudeAuthRequired could already be true from a warmup 401 that hit before any query was in flight, so when the user then sent a real query, there was no @Published transition to react to. The spinner-clear subscription only fires on a transition. With no transition, the window sat on a spinner until the auth flow completed or the 10-minute OAuth timeout. The two commits restore both signals: clear the spinner on the auth-required edge, and re-publish that edge from the bridge when a flow is already in progress.

How can I read any project's real May 31 to June 1 myself?

Skip the trending pages and read the dated records. For a GitHub repo, git log --since="2026-05-31" --until="2026-06-02" gives you commits with timestamps; git tag --sort=-creatordate and the releases page give you what was actually cut. For a Hugging Face model, the commit history on the model card and the files-and-versions tab carry real dates. The trending score answers "what is popular right now," which is a different question from "what was new on a specific day."

Is Fazm itself open source, and where do these claims trace?

Yes. Fazm is a native macOS app (14.0+), fully open source on GitHub at github.com/mediar-ai/fazm, and it runs locally. You bring your own Claude Pro or Max account and usage hits your existing plan. Every Fazm claim on this page is checkable in that repo: the empty May 31 commit log, the v2.9.58 tag on June 1, and the two commits 739e2b57 and 593b7ce8 with their line counts in ChatQueryLifecycle.swift and acp-bridge/src/index.ts. The MiniMax M3 details trace to its June 1, 2026 launch coverage.