How a task runs

The interaction

You describe the outcome. PLUXIX scopes the request to the selected workspace, loads the relevant project signal and records the conversation as a durable thread.

• The Agent reads only the context needed for the current turn.
• Complex work is split into verifiable checkpoints.
• Tools run under workspace, account and approval policy.
• The response includes evidence, not only a claim of completion.

Execution stages

The normal loop is context → plan → execute → verify → handoff. A short question may finish in one turn; a refactor or release may run through many checkpoints.

• Context: inspect files, history, symbols and dependencies.
• Plan: identify files, risks, dependencies and acceptance criteria.
• Execute: edit, run tools and request approval when required.
• Verify: run tests, build, lint or a focused manual check.
• Handoff: summarize changes, evidence and remaining decisions.

When to intervene

Pause when the plan leaves the requested scope, a destructive action is proposed, a credential is requested, or evidence contradicts the expected result. Clear feedback lets the Agent resume with a better boundary.