← Documentation

PLUXIX GUIDE

Security

PLUXIX separates cloud identity and routing from local project execution.

Credentials

Service credentials and connected-account tokens are stored in protected backend or local stores according to their scope. They are not rendered back to users or placed in task prompts.

  • Never paste API keys into chat.
  • Rotate a credential after a team member or device loses access.
  • Use the smallest GitHub or MCP permission that solves the task.

Local execution

Files, Git, terminal, browser and Windows automation run through the local Agent and its permission boundary. The cloud remains the source of truth for account, routing, credit and durable metadata, while project contents stay local unless explicitly used as task context.

Review boundary

Before production work, confirm the workspace, branch, target environment, approval mode, connected tools and rollback plan. A fast Agent is still subject to the same review discipline as a human change.