SpecWithCode 1.0.43

SpecWithCode 1.0.43

Computer use

• Agents can control this Mac through computer use: screenshots, clicks, typing and scrolling. macOS asks once for Screen Recording and Accessibility, and the first use waits for you to allow them.
• Turn computer use on per machine. Every provider and project on that machine can then use it.

Machines

• Add a machine by its own Tailscale name: run specweave-studio fleet invite on it and paste the line into Settings > Connections > Add a machine.
• A project stays usable when its saved machine is offline. Threads on that machine show "Host offline" instead of Blocked.
• Chats, the sidebar and Settings show one status for each machine, with when it was last seen. The machine picker says when a machine can't be reached.
• A chat whose machine drops can continue on another machine.
• Pairing links only offer addresses that other machines can open.
• Settings > Connections fits on one page, with machines first.
• A warning appears before you sign a subscription in on a rented server.

Usage and limits

• Claude starts are admitted when the Claude CLI is signed in to the Claude Console and bills API credits. A real credits failure still shows Claude's own "Credit balance is too low" message.
• When a capacity refresh fails or is busy, a start retries it and can go ahead on the last reading if it had room. Blocked, busy, exhausted and denied profiles are still refused.
• Continue a thread that hit its limit on API credits in one click.
• Limit readings from offline accounts are marked as such, and windows past their reset reopen.
• The usage popover lists machines in one aligned grid.
• Gemini CLI offers Gemini 4 Argon and records its usage.

Chats and threads

• Short replies stay inline instead of becoming report cards, and worker answers show in full.
• A new chat shows its reply without reopening.
• Chat headers take fewer rows.
• A chat can name its own folder, and Turn into project makes it a project.
• The source thread stays live beside the viewer.
• A conflicting pull request is resolved in the thread that owns it.
• Answered decisions fold into a one-line summary. Approval cards split their text and show queued approvals.
• Every report uses one page style.

Projects and routines

• Rename a project inline. Names are unique, ignoring case.
• Project workers start and continue on the machine where the coordinator runs.
• Routines go through the coordinator and follow the recommended model.
• Projects created with temporary tokens are deleted once the token ends.
• Provider logos are the official ones, and skill details appear above Settings.

Removed

• Anthropic cloud sessions are gone. Use your own machines or a Linux VPS worker instead.