Start free
PRODUCT

Rubic plans, builds, runs, and delivers software tasks.

Delegate features, fixes, refactors, and maintenance work from one place. Your team stays focused on decisions and review while Rubic moves each task forward.

From request
to merged
pull request.

Rubic reads the code and rules, proposes the plan, runs the application, and opens or merges the pull request with every step visible to your team.

CODEBASE CONTEXT

Rubic starts each task with your code, knowledge, and rules.

Configure the repository once. Rubic uses its structure, application setup, shared knowledge, and working rules whenever it plans or executes a task.

REPOSITORY PROFILE

Reads how the repository is structured.

Rubic uses the repository summary, default branch, coding guidelines, and application setup in every task.

KNOWLEDGE SEARCH

Finds relevant code and past decisions.

Rubic searches indexed files and shared product knowledge before it proposes or changes anything.

PROJECT RULES

Follows the team’s working rules.

Project and repository rules define how Rubic should plan, build, review, and deliver the work.

TASK WORKFLOW

See one task go from plan to pull request.

Rubic plans the work, changes the code, runs the application, tests the result, asks for decisions, and prepares the pull request. Your team reviews and approves the work at the required checkpoints.

BEFORE CODING

Rubic proposes a plan before changing code.

Rubic reads the repository and project rules, then lists the implementation steps, affected files, risks, and checks for the task.

Your team can approve the plan or request changes before development starts.
Rubic
TASKS / T-184 Add localization to the customer portal
AWAITING PLAN APPROVAL
Chat Plan
PLAN READY FOR REVIEW Review the approach before Rubic starts building.
IMPLEMENTATION PLAN

Add English and Spanish localization while preserving existing URLs and saved language preferences.

4 steps 5 files Medium

Configure locale foundation Catalogs, fallback, and default locale

Preserve routing behavior Existing links and saved URLs stay unchanged

Verify the customer portal Preference, fallback, and regression checks

LIVE PREVIEW

Rubic runs the application for every task.

The application and its required services run in a task-specific cloud workspace. The live result is available at a dedicated https://{taskId}.rubc.run URL.

Open or share the preview while its code, services, and logs remain available in Rubic.
https://t-184.rubc.run/dashboard LIVE
Northstar
PORTAL DEL CLIENTE

Gestiona tus pedidos en un solo lugar.

Consulta el estado de tus pedidos, revisa los totales y recibe actualizaciones en tiempo real.

PEDIDOS 12 ABIERTOS 3 MENSAJES 2
PEDIDO ESTADO TOTAL

#1048 En camino €128

#1042 Entregado €84

#1037 Procesando €56

CODE AND APPLICATION REVIEW

Review the diff, tests, logs, and live application together.

The task keeps the code change, test results, application output, and live preview in one workspace for review.

Request a revision or merge the approved pull request without leaving Rubic.
Rubic
TASKS / T-184 Add localization to the customer portal
READY FOR REVIEW
config.ts src/i18n/config.ts

1 import { readProfileLocale } from './profile';

3 − export const locales = ['en'];

3 + export const locales = ['en', 'es'];

4 export const defaultLocale = 'en';

7 + const saved = readProfileLocale(request);

8 + if (saved && locales.includes(saved)) {

9 +   return saved;

10 + }

All checks passed
QUESTIONS DURING WORK

Rubic asks when it needs a decision.

If the implementation needs a product or technical choice, Rubic pauses at that point and asks the team inside the task.

Rubic applies the answer and continues the same task.
Rubic
TASKS / T-184 Add localization to the customer portal
NEEDS INPUT
Chat Plan
JL

JORDAN LEE · 09:23 Keep existing URLs unchanged and preserve each signed-in user's saved language preference.

DECISION REQUIRED How should language preference be resolved?

The answer changes locale precedence and fallback behavior.

SK

DECISION ANSWERED Profile, then browser

R

RUBIC · NOW Decision applied. Existing routes were preserved and the affected checks were rerun.

TASK CREATION

Describe the result and choose where Rubic should work.

Write the outcome, attach supporting files, and select the repository, priority, assignee, watchers, and plan approval setting for the task.

  • Start development immediately or add the task to the backlog
  • Attach requirements, designs, or customer copy
  • Choose who owns, watches, and approves the work
Rubic
←
NEW TASK

What should Rubic build today?

Add English and Spanish localization to the customer portal. Preserve existing URLs and include regression coverage.

locale-requirements.pdf customer-copy.md
Plan approval Required Priority High
northstar/customer-portal
Alex Smith 2 watchers
Rubic
TASKS / T-205

Audit production feature flags

COMPLETED
OPERATIONAL TASK

Rubic completed the work without changing the repository.

The requested audit ran against the connected environment and produced a reviewable result.

18 feature flags reviewed Across production and staging

3 differences found Owners and current values included

No code changes No branch or pull request required

CODE AND OPERATIONAL TASKS

Use Rubic for code changes, audits, research, and runbooks.

A code task ends with a branch, tests, and a pull request. An operational task ends with a report, findings, or completed procedure without changing the repository.

CODE TASKBranch, checks, pull request
OPERATIONAL TASKReport, findings, next actions
APPLICATION SETUP

Configure once how Rubic should run the application.

Store the start command, port, health check, required services, environment settings, setup commands, and restart behavior with the repository. Rubic reuses them for every task.

Rubic
REPOSITORIES / NORTHSTAR

customer-portal

READY
Overview Guidelines Application workspace Access
APPLICATION WORKSPACE ENABLED

Define once how Rubic should start and verify this application.

PostgreSQL Connected database

READY

Background service npm run worker

READY
Environment settings and setup commands are stored with this repository.
MULTI-REPOSITORY EPICS

Rubic splits larger work into tasks across repositories.

An epic creates repository-specific tasks from one implementation plan. Rubic runs tasks in sequence when one depends on another and in parallel when they are independent.

  • One implementation plan for the complete change
  • Explicit sequential and parallel task dependencies
  • Task progress, questions, and delivery visible from the epic
Rubic
EPICS / E-24

Customer portal localization rollout

PLAN READY
Overview Plan Tasks 6 Activity
IMPLEMENTATION PLAN

Coordinate the rollout across the portal and platform API.

Shared locale contracts land first. Application work then continues in parallel.

2 REPOSITORIES 6 TASKS SEQUENTIAL + PARALLEL
01
northstar/platform-api

Expose supported locales and saved preference.

FIRST
02
northstar/customer-portal

Localize account and order surfaces.

PARALLEL
03
northstar/admin-console

Add translation management controls.

PARALLEL
Shared locale schema must be available before application tasks begin.
REVIEW AND MERGE

Your team approves the plan, reviews the result, and merges the PR.

Rubic prepares the implementation, tests, live preview, and pull request. Your team can approve the plan, answer questions, request revisions, inspect the result, and perform the final merge in Rubic.

  1. 01
    PLAN APPROVAL

    Review and approve the approach before coding starts.

  2. 02
    QUESTIONS

    Answer a product or technical question inside the task.

  3. 03
    REVISIONS

    Request a change while Rubic continues the same task.

  4. 04
    FINAL REVIEW

    Inspect changed files, tests, logs, and the running application.

  5. 05
    PR MERGE

    Merge an approved pull request directly from Rubic.

Rubic
PULL REQUESTS / #284

Add localization to the customer portal

READY TO MERGE
24 checks passed PASS
Review complete APPROVED
4 files changed +237 −12
feat/T-184-portal-localization main
config.ts provider.tsx es.ts locale-routing.test.ts
Merge Pull Request

Squash and merge this pull request into main?

PRODUCT AREAS

Tasks, epics, questions, and pull requests stay connected.

Open a task to see its plan, conversation, changed files, tests, live application, and delivery state. Use the team views to track the same work across larger initiatives.

01

Tasks

Create, assign, run, and review individual software tasks.

02

Epics

Plan and track related tasks across multiple repositories.

03

Inbox

See task updates and questions that need a response.

04

Pull Requests

Review delivery status and merge approved pull requests.

05

Repositories

Configure code access, context, and application setup.

06

Knowledge Base

Search code and shared project knowledge.

07

Rules

Define how Rubic should plan, build, review, and deliver.

START WITH ONE REPOSITORY

Connect a repository and give Rubic a real task.

Rubic will read the code and rules, propose a plan, and wait for approval before it starts implementation.

Start free Talk to us