Changelog
Every Monday, a recap of the previous week’s public releases.
This changelog is generated by AI.
Autofix now shows its repair allowance in the session action panel. When that allowance is exhausted, reviewers can choose to keep autofixing and give the session another bounded attempt.
Repair budgets now carry across replacement runs, so restarting a repair does not silently reset its limits.
Publication recovery now handles branches that move while work is finishing. Sandboxes are preserved while a Git push is still in progress, and paused work is less likely to be mistaken for a missing or failed sandbox.
Fixes to queue stalls, database contention, and progress detection also reduce cases where active work is incorrectly stopped or left waiting.
Older session activity loads as you scroll, with fixes to pagination so the history remains navigable.
New coding sessions can now include file attachments and pasted images alongside the prompt. Reviewers can give the agent supporting material at creation time and inspect those attachments from the session.
Discussion sessions are now available to everyone. Ask questions and explore a repository with an agent without opening a coding task or publishing a branch. Follow-up prompts keep the discussion in the same session.
Follow-up changes now wait for an explicit publish action before updating the remote branch. Reviewers can inspect the work in the session before making the next revision available on GitHub.
Tough Crowd can now record production deployment results and show a Deployed status for the associated work. This distinguishes a merged change from one that has actually reached production.
A forgot-password flow now helps users regain access to their account, with clearer authentication feedback along the way.
Sessions can recover when the sandbox provider pauses an active workspace. Paused previews are no longer incorrectly treated as deleted, and recent reviewer interaction resets the pause timer.
Publication retries and finalization were also tightened so interrupted work can settle without duplicate actions.
The setup section is now collapsed by default, keeping the agent’s work easier to find. Elapsed times include hours for longer sessions, and post-creation loading uses a consistent indicator.
Organization settings are now broadly available. Administrators can manage the organization’s name, members, and invitations from a shared settings screen.
The redesigned Sessions list is now the standard experience. Work is grouped into In progress, Review, Failed, and Ended views, with focused status and check filters for finding the sessions that need attention.
Session dates are shown in the reviewer’s local time, and each view presents the timestamp that matters for that stage of work.
Session detail now brings readiness evidence, pull-request context, and the appropriate next action into one consistent panel. Reviewers can see what is blocking a merge and act on recoverable, failed, completed, or archived work without translating internal lifecycle states.
Tough Crowd now verifies the target branch immediately before merging. If the branch has advanced since the change was reviewed, the merge stops instead of applying stale review evidence to a different base.
The Tough Crowd CLI can now cancel active work or abandon a session through the public API. These commands use the same durable lifecycle transitions as the browser, so cleanup and final state remain consistent.
Session state transitions now use a single auditable path, reducing contradictory status, sandbox, and usage records. Publication recovery and sandbox cleanup were also strengthened so interrupted workers are less likely to strand completed work or leave resources running.
Text contrast, focus behavior, navigation labels, and button states were tightened across the application. Long agent activity now stays within its column and can be copied without breaking the session layout.
Consecutive agent activity is grouped into readable units instead of appearing as a long stream of individual events. Expanded and collapsed groups keep their state while new work arrives, so a reviewer’s place is not lost during a live session.
Session lists now show created and updated timestamps, while elapsed time is displayed in hours, minutes, and seconds. This makes it easier to distinguish newly active work from sessions that have been waiting for review.
Branch publication now uses one authenticated path with stronger ownership and branch-head checks. Sessions that finish without changing files settle cleanly, and sessions whose pull-request branch advances externally are reconciled instead of being left in an ambiguous state.
Idle and review-ready sandboxes now use recent user interaction when deciding when to pause. Untouched ready sessions can pause immediately, while a reviewer who is actively inspecting the work does not lose the live workspace underneath them.
Verification and follow-up deadlocks were repaired, transient sandbox transport failures now receive bounded retries, and oversized live-diff artifacts can no longer overwhelm session monitoring. Artifact failures are surfaced explicitly instead of silently producing incomplete evidence.
Sessions that need input now pause their sandbox instead of consuming resources indefinitely. Reviewers can resume recoverable sessions, and a new “Verify and finish” path completes verification when the coding work is already done.
Several conditions that could strand sessions during GitHub authentication, sandbox recovery, artifact collection, or worker reconciliation were also fixed.
Pull-request changes are now calculated from the true merge base rather than the repository’s current default-branch head. This prevents unrelated upstream changes from appearing in the review diff.
Sandbox file and artifact failures are also surfaced explicitly instead of silently producing incomplete review evidence.
The Sessions screen now loads history incrementally. Reviewers can load additional sessions without fetching the entire history upfront.
New model options have been added to Agent Profiles. TypeScript and Python repositories also receive more reliable default toolchain setup, with setup activity visible in the session timeline.
Database contention was reduced, several sandbox lifecycle races were repaired, and deployments were changed to avoid brief API 5xx gaps while ECS tasks and load-balancer targets rotate.
A public system status page is now available at statuspage.incident.io/tough-crowd for production incidents and recovery updates.
The redesigned New Session composer is now the standard experience. Repository, branch, coding-agent profile, model, and reasoning effort can be selected in one place, and those choices are preserved through execution and retries.
Reviewers can send additional instructions while an agent is working. Prompts are held in a durable queue and can be edited, withdrawn, paused, and resumed without losing the session workspace.
Stopping an active task no longer discards queued follow-up work.
The pull-request Conversation tab is now available to everyone, bringing GitHub discussion into the session review workflow.
The merge experience now presents blocking and advisory checks separately, explains why a change is or is not ready, and supports the available merge strategies without hiding unresolved evidence.
Recoverable verification failures can be repaired and resumed instead of forcing the reviewer to abandon the session.
Images in repository and diff views can now be previewed without downloading them or leaving the review workflow.
The Files Changed view was also expanded to make larger diffs easier to inspect.
Session status and activity now update through the live event stream. Counts, verification progress, and lifecycle transitions converge without requiring repeated page refreshes.
Review-ready and inactive sessions automatically pause their sandboxes while preserving the workspace for later review or follow-up work. Cancellation and cleanup races that could leave orphaned sandboxes were also corrected.
The Tough Crowd website moved to a faster static architecture and is now deployed independently from the authenticated application.
The Tough Crowd CLI can authorize through the browser instead of asking users to manually transfer credentials. The authorization flow creates a revocable API key and returns control to the CLI after approval.
API keys can now be named, copied from a one-time reveal, inspected through safe masked previews, and revoked with explicit confirmation. The Settings screen also shows creation and last-used information without retaining recoverable key secrets.
Tough Crowd now checks whether a repository can support a coding session before committing agent time. Problems with configuration, credentials, branches, or the development environment are reported earlier and more clearly.
File changes and diff counts now appear as the agent works. Reviewers no longer need to reload the session to see newly created or modified files.
Verification failures now enter bounded repair workflows with clearer state transitions. Worker retries, session reconciliation, and CI outcome handling were strengthened so transient failures are less likely to strand otherwise valid work.
