Describe
Write the outcome, constraints and acceptance criteria in a durable project chat.
THE PLUXIX WORKFLOWA development task,
A development task,
carried by evidence.
Pluxix keeps the request, the local workspace, the tool actions and the proof in one connected path. You describe the outcome; the Agent makes the work inspectable.
LIVE THREADFix inventory total
✓Contextselected
✓Plan3 checkpoints
03Verifytest in progress
SIX STOPS, ONE THREAD
From intent to a reviewable change.
The flow is deliberately visible. Each step leaves enough context for you to continue, approve, correct or stop the work.
Context
The Agent works from the selected local workspace and the project evidence relevant to the task.
Plan
Break a broad request into checkpoints so the next action and the reason for it stay visible.
Execute
Use files, terminal, Git, tests, browser and approved MCP tools within the configured boundary.
Verify
Run the checks that matter, inspect the diff and surface failures instead of hiding them.
Handoff
Return the change, evidence, open decisions and a clear next step for the person reviewing it.
TWO BOUNDARIESCloud coordination.
Cloud coordination.
Local project work.
PLUXIX keeps account identity, approved routing, credit, usage and thread continuity in the service. The Windows Agent keeps the selected project and execution tools close to the files that matter.
PLUXIX SERVICEIdentity · routing · usage · accountConnected through the public API
↕WINDOWS AGENTWorkspace · files · Git · terminal · testsRuns on the user’s machine
A CONCRETE TASK
“Fix the stale inventory total.”
Instead of handing over a repository dump, the Agent can work through the project in a sequence you can follow.
Find the path
Inspect the relevant route, service, model and test files in the local workspace.
Make the smallest change
Update the implementation and keep the working set focused on the behavior under review.
Prove and hand off
Run the relevant test, show the diff and call out anything that still needs a human decision.
DESIGNED FOR CONTROL
Autonomy with a visible edge.
You can allow the workflow to move quickly while retaining the controls that make local software work safe to review.
Start from an explicit local folder rather than an invisible environment.
Pause sensitive, destructive or elevated actions according to policy.
Keep activity, diffs, tests and usage available for the next decision.
Resume a durable thread, inspect the failure and retry after the cause is fixed.
READY TO TRY IT?