Runtime settings, optional review, and clearer work summaries
Configure a task without editing repository files, choose when Rubic should review its work, and follow multi-step development more clearly.
Configure Runtime Env for each task
Add task-specific environment values from the task workspace. Rubic applies them to development and preview processes without requiring a change to the repository’s environment files.
Run Review & Fix when you need it
Review is now an explicit action after development. Start Review & Fix from the completed work, let Rubic inspect the latest changes, and return the task for approval with any required fixes applied.
Use Rubic for work beyond code changes
Plans now distinguish code changes from operational work. Rubic can complete audits, investigations, and runbook tasks while keeping the commands and verification details attached to the task.
See the complete development loop
- Multi-attempt work is summarized as one readable development history.
- Changed files stay grouped with the run that produced them.
- Failed checks show the actual command output Rubic used for the next attempt.
- Task and epic replies follow the language used by your team.