Best practices

Procedure tips that prevent churn

Workspace boundaries

• Use one workspace per project/client boundary.
• Avoid mixing unrelated providers in one workspace when auditability matters.
• Name workspaces after business context, not temporary experiments.

Loadout hygiene

• Keep loadouts small and intent-based (research, build, deploy, support).
• Add tools only when they are actively needed by that workflow.
• After any loadout change, refresh client view with tools/list.

Connection setup discipline

• Always copy setup URL from session panel; do not hand-edit owner routes.
• Prefer deep link -> npx -> manual fallback in that order.
• Rerunning npx loadoutz@latest connect <setup-url> is safe for keeping config in sync.

Failure triage checklist

1. 1. Confirm provider status is Ready in workspace.
2. 2. Confirm target tool is in active loadout.
3. 3. Re-run initialize then tools/list.
4. 4. If auth fails, reconnect OAuth for owner URL and retry.
5. 5. If still broken, use Troubleshooting and file an issue with logs.