Local execution
Files, Git, terminal, tests and Windows automation run through the local Agent under explicit workspace permissions.
SECURITY BY DESIGNYour code stays
Your code stays
in your control.
PLUXIX separates account, protected service and local execution boundaries so the Agent can work without turning your workspace into a shared data store.
CONTROL SURFACEClear boundaries
✓Local workspacefiles · Git · tests
✓Protected identitysessions · connections
!Approval-awareelevated actions pause
Protected secrets
Service credentials and connected-account tokens stay encrypted in the backend and are never placed into an AI request.
Auditable usage
Every request records its role, measured service usage, cost and wallet charge so unexpected behavior can be investigated.
Controlled access
Sessions, devices, roles and account connections can be reviewed and revoked from the user portal.
What stays on the machine
The selected Windows workspace, local files, Git operations, terminal commands, tests and local Agent runtime remain on the user’s computer. The Agent asks for permission when an action crosses the configured workspace or application boundary.
What the service manages
PLUXIX manages identity, sessions, device revocation, approved routing, usage records, credit and connected account metadata. Internal provider and model identifiers are not part of the user-facing workflow.
Actions that deserve a pause
Destructive filesystem operations, access outside the workspace, package installation, Git push and other elevated actions can require an explicit approval according to workspace policy.
How to investigate
Use the portal’s devices, connections, notifications and usage views together with the Agent’s local diagnostic logs. Rotate credentials and revoke sessions when a device or connection is no longer trusted.
Security is a product feature.
Read the operational boundaries before enabling a new tool or connection, and keep production workspaces isolated from experiments.