Connect pg-aiguide to Lovable
Give Lovable governed access to pg-aiguide through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add pg-aiguide to Lovable in four steps
Admins approve the server once. Everyone in Lovable then gets it through the same governed connection.
- 1
Approve pg-aiguide in Runlayer
Add pg-aiguide from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Lovable to Runlayer
Users add the Runlayer Plugin to Lovable by following Runlayer’s setup guide. Lovable reaches pg-aiguide’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Lovable setup guide - 3
Sign in to pg-aiguide
Sign in the way pg-aiguide requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use pg-aiguide from Lovable
pg-aiguide’s approved tools appear in Lovable. Every call is checked against policy and recorded.
Tools
pg-aiguide tools in Lovable
pg-aiguide reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in Lovable
Some controls apply to every client at the gateway. Others depend on what Lovable exposes to Runlayer.
Gateway policy (available)
Every pg-aiguide call from Lovable passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Lovable as the client, the tool, and the policy and scanner decisions.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Lovable yet, so control happens at the gateway.
Frequently asked questions
Connect more