Changelog

Pinning a model that none of your credentials could serve already failed before any sandbox was created. It just failed after the run had been counted against your daily free allowance, so a typo in .sinatrarc cost you a task. The check now runs first.

The same change treats a workspace OpenRouter key as able to serve any model in the catalog, since it is a gateway. Workspaces on an OpenRouter key that were previously refused an Anthropic-credentialed model are not refused any more.

It is spelled fable-5-1 directly and claude-fable-5.1 through OpenRouter. The sandbox CLI pins moved up in the same change: opencode 1.18.27 and oh-my-pi 18.1.8 are the first pinned versions whose bundled model catalogs list it.

The two were counted independently before this, so a workspace could take five own-key tasks and a managed one on top.

The edge is sharper than "one of the five". Once anyone in the workspace has run a task on their own key or subscription, the managed slot is spent for the day, and a member with no credentials of their own gets nothing further even with slots left in the pool. If you were relying on the sixth task, you will notice.

The dashboard billing card shows the pool and what the signed-in member has left.

A team where everyone already pays for a subscription no longer needs a shared key to get off the managed path. Model credentials were a workspace-level setting before this, so one key or one connection covered everybody.

A personal connection takes precedence over the workspace key and over our managed key for that member's tasks, and onboarding counts it as configured model access.

A join link is one forward away from being a link anyone can use. An invitation now expires after seven days and can only be redeemed by a signed-in user whose own verified GitHub address matches the one it was sent to.

Delivery took a second pass. The mail was built in August but was not actually being sent in production until 1 September, and it now comes from a named sender with a working reply-to. One gap we have not closed is that the invite list shows "Sent" even when a delivery was skipped or failed.

This broke handovers that used to work. Sinatra runs a task as the person who handed it over, using their Linear identity, and since 28 August it will not start when that Linear account has never been linked to a Sinatra user through Linear sign-in. Being a member of the workspace is not enough.

The run stops and Sinatra replies on the issue with a link to workspace settings; linking takes about half a minute. The first version of that reply told people to sign in, which was useless advice for anyone who already had an account, and it was corrected on 2 September.

A PR with no assignee sits in nobody's queue. Assignment is best-effort: if the person cannot be resolved to a GitHub account, or that account has no access to the repository, the PR opens unassigned rather than the run failing.

Stop was wired to the same terminal signal as cancelling a task, so it took the whole workstream down and archived the sandbox, queued follow-ups included. The running turn is now interrupted within a few seconds and no pull request is opened for it.

Anything the agent had already pushed stays on the branch. Anything it had only committed inside the sandbox goes with the sandbox.

Installing Sinatra on a GitHub or Linear org that already has a workspace used to dead-end, with nothing you could do about it from either side. That attempt now files a request an owner picks up in settings. Removing a member takes effect on their next request.

There is still no way to ask for access from inside the product. The request has to come from an install attempt.

Every task gets its own sandbox with your repository in it. It stops when the task ends and is archived a day later, and until now nothing removed it after that. The clock runs on activity rather than on archiving, so in practice a sandbox sits archived for about 29 days before the sweep takes it.

oh-my-pi was already in the catalog as hidden plumbing. Free-tier managed runs have been executing on it since July, so unhiding it changes what you can pick rather than what the product could already do. It carries the openai-codex/gpt-5.6-* tiers, which no other engine exposes; the other Codex-backed models are reachable through opencode too.