Environment Tags
Use environment tags to color-code tpaw connections by environment — production, staging, development, or local.
Environment tags add a colored dot to connection cards and a badge in the connection header, making it immediately obvious which environment you're working in. This reduces the risk of accidentally running destructive queries against production.
Available tags
| Tag | Color | Use for |
|---|---|---|
| prod | Red | Production databases — live user data |
| staging | Orange/Yellow | Pre-production staging environments |
| dev | Teal | Shared development or CI databases |
| local | Gray | Local development (localhost) |
Setting an environment tag
When creating or editing a connection, find the Environment row in the connection form. Click one of the four pill buttons: Local, Dev, Staging, or Prod.
To remove a tag, click None.
Where tags appear
Connection card — A colored dot appears in the corner of the connection card on the home screen. This makes the environment visible at a glance across all your connections.
Connection header — Once connected, a tag pill badge shows in the header bar at the top of the main content area. You always know which environment the current session is using.
Best practices
- Always tag production connections as prod — the red color serves as a constant visual reminder
- Use read-only mode together with the prod tag for production connections where you only need to query, not modify data
- Name connections clearly:
Production DB (prod),Staging DB (staging),Local Dev (local)
Read-only connections
In the connection form, enable Read-only to prevent any write operations. tpaw will refuse to execute INSERT, UPDATE, DELETE, or DDL statements. This is a useful safeguard for production connections where you should only be reading data.