Bitbucket
Bitbucket is Atlassian's code host where teams keep Git repositories and review work in pull requests.
What it reads
- Repositories you are a member of: 10 most recently updated, of which the first 5 are read: full name (workspace/repo), name, main branch
- Merged pull requests: up to 10 per repository, state merged: id, title, summary or description text (first 3,800 characters), updated time
- Commits on the main branch: up to 100 per repository: message and date, windowed to since the last check on FoxPlug's side, grouped into one digest per repository per UTC day, newest 10 days kept
Moments
- A pull request is merged. You merge a pull request titled Add team invitations in a repository called portal. FoxPlug keeps 'Merged: Add team invitations' with the pull request summary as the description and scores it; at 35 or more it gets short posts.
- Commits land on the main branch. Six commits go to main in a day. FoxPlug makes one digest titled '6 commits in portal on 2026-11-09' listing the distinct commit messages, and the score reads the commit count.
Set up
- Open id.atlassian.com/manage-profile/security/api-tokens (Bitbucket app passwords are retired).
- Click Create API token with scopes (the plain Create API token button will not work).
- Name it (FoxPlug), choose when it expires, click Next.
- Select Bitbucket as the app, click Next.
- Tick Read repositories, click Next, then Create.
- Copy the token (Atlassian shows it once) and paste it into FoxPlug, with your Atlassian account email in the second box.
What it never reads
- The contents or diffs of your files (only repository, pull request and commit-list calls are made)
- Issues, pipelines or releases (not read for Bitbucket)
- Anything it could change: read requests only, and the token is asked for the Read repositories scope
How it differs
Like GitHub and GitLab it reads merged pull requests and a daily commit digest, but it reads no releases, no issues and no build runs. Auth differs: an Atlassian API token plus your Atlassian email, not a single token.
Why does FoxPlug ask for my Atlassian email?
Bitbucket pairs the API token with your Atlassian account email, not your Bitbucket username, so the email goes in the second box.
Do old app passwords still work?
No. The connect steps say Bitbucket app passwords are retired; use an API token created with scopes and the Read repositories box ticked.
Does it read my code?
No. It reads repository names, merged pull request titles and summaries, and commit messages and dates.
When does it look at Bitbucket?
Only when you press Check for what's new.
Lovable
Lovable is an AI app builder where you describe an app in chat and it builds and edits the project for you.
What it reads
- Your workspaces: up to 10 workspace ids
- Projects in those workspaces: up to 25: project id, name, description (first 600 characters), last edited time, whether it is published
Moments
- A project is edited since your last check. You change your Lovable project called Recipe Planner. After you press Check for what's new, FoxPlug makes one moment, 'Edited in Lovable: Recipe Planner', with the project description as its text, scored like any update.
- A published project is edited. Same moment, but the description ends with '(published)' when the project is published, so the post can say it is live.
Set up
- In Lovable, open Settings and then Access tokens.
- Make a new key with only the scope workspaces:read and a name such as FoxPlug.
- Copy the key (it starts with lov_) and paste it into FoxPlug.
What it never reads
- Your prompts or the code Lovable wrote
- A change-by-change history (Lovable's API does not publish one)
- Writes: the key is asked for the workspaces:read scope only
Does FoxPlug see each change I ask Lovable to make?
No. Lovable's API does not publish a per-change history, so FoxPlug sees which project you edited and when. For every change as it happens, the app points to Lovable's GitHub sync read through the GitHub connection.
Does it read my prompts or code?
No. It reads project name, description, last edited time and whether it is published.
Which Lovable plan do I need?
The connect panel says the project list needs a Business plan or higher.
Netlify
Netlify is a hosting platform for web sites and apps where each site gets deploys that can be published to production.
What it reads
- Your sites: 10 sites listed, first 5 read: site id, name or custom domain
- Recent deploys per site: 20 per site: deploy id, state (ready only), context (production only), published or created time, title, commit ref
Moments
- A production deploy becomes ready. Your acme-site deploy to production reaches the ready state. FoxPlug makes one moment per deploy, titled 'Deployed acme-site', with the description 'Shipped acme-site to production - ' followed by the deploy title or commit ref (or 'a new version').
- Several deploys over a few days. Each deploy is its own moment, scored on its own. A deploy whose name reads like a dependency bump or refactor counts toward the skip line instead of getting a post.
- Visits drop after a deploy (analytics connected). Netlify deploys are used as the deploy marker. A deploy 2 to 6 days old followed by a 30 percent or larger drop in daily visits puts a fix card first in Today.
Set up
- Open app.netlify.com/user/applications#personal-access-tokens.
- Under Personal access tokens click New access token.
- Name it (FoxPlug) and choose when it expires (tick the SAML option only if your team uses SAML).
- Click Generate token; Netlify shows it once. Copy it and paste it into FoxPlug.
What it never reads
- Build logs, environment variables or form submissions (only the sites list and the deploy list are requested)
- Failed, preview or branch deploys (only state ready with a production context are kept)
Is the Netlify token read-only?
No. The connect panel says Netlify has no read-only setting; the token covers your whole account. Setting an expiry date is the main way to limit it. FoxPlug only makes read requests.
Does FoxPlug see failed Netlify deploys?
No. It keeps ready deploys to production only.
When does it look at Netlify?
Only when you press Check for what's new.
Railway
Railway is a cloud platform where makers deploy apps, databases and services from a repository, organised into projects.
What it reads
- Your projects and their services: first 5 projects: project id and name; per service: id, name, created time
- Deployments per project: the latest 30 per project: deployment id, status, created time, which service it belongs to. Building, deploying, queued, waiting, removed, skipped and sleeping ones are ignored
Moments
- A deployment succeeds. A service called web in a project called acme has a deployment with status SUCCESS after your last check. FoxPlug makes the moment 'Deployed acme / web' with the description 'Shipped acme / web on Railway.'
- A deployment fails or crashes. The newest finished deployment of the web service is FAILED or CRASHED, within the last 7 days. The first card in Today names it, how many failed in a row and since when. A later SUCCESS clears it.
- A new service is added. A service created in the last 14 days becomes 'Launched a new service: acme / worker' with 'A new service went up on Railway: acme / worker.'
Set up
- In Railway, open your account settings and then Tokens.
- Make a new token named FoxPlug and choose No workspace, so it is an account token. A project token does not work here.
- Copy the token now and paste it into FoxPlug; Railway shows it only once.
What it never reads
- Variables and logs
- Custom domains (the Railway read does not fetch them)
- Writes of any kind: the only request body sent is a read-only query
Why does Railway need an account token?
The read lists your projects with one account-level query, and a project token cannot do that. The panel says a project token does not work here and to choose No workspace when creating the token.
Does it read my variables or logs?
No. It reads project and service names and deployment status and time.
Is the token read-only?
The panel says Railway account tokens can see everything on your account; FoxPlug only makes read queries.
When does it check Railway?
Only when you press Check for what's new.
Render
Render is a cloud host where makers run web services, static sites and background workers and deploy them from Git.
What it reads
- Your services: up to 20 listed, first 8 read; suspended services skipped: id, name, type, created time, service URL
- Recent deploys per service: up to 10 per service: deploy id, status, finished or created time, first line of the commit message (120 characters). Still-running, cancelled and deactivated deploys are ignored
- Custom domains per service: domain names only
Moments
- A deploy finishes live. Your service called api has a deploy that went live. FoxPlug makes the moment 'Deployed api' with the description 'Shipped api on Render - ' and the first line of the commit message, for instance 'Add rate limiting'.
- A deploy fails. The newest finished deploy of api failed (build, update or pre-deploy failure) in the last 7 days. The first card in Today says 'Your api deploy is failing on Render. Fix this first.' with how many failed in a row, since when and the last commit message. A later good deploy clears it.
- A new service is created. A service created in the last 14 days becomes 'Launched a new web service: api' (the kind is Render's own service type word) with the description 'A new web service went up on Render: api.'
Set up
- In Render, open Account Settings and then API Keys.
- Press Create API Key and name it FoxPlug (pick a read-only option if Render offers one).
- Copy the key now and paste it into FoxPlug; Render may show it only once.
What it never reads
- Environment variables and logs
- DNS records
- Suspended services, and deploys that are still building or were cancelled
Can FoxPlug tell me when my Render deploy fails?
Yes, when you press Check for what's new. A service whose newest finished deploy failed in the last 7 days becomes the first card in your Today brief, and a later good deploy clears it.
Does it read my environment variables or logs?
No. It reads services, their finished deploys and custom domains only.
Does a cancelled deploy count as a failure?
No. Cancelled, deactivated and still-building deploys are ignored.
Is the key read-only?
The connect steps say to pick a read-only option if Render offers one. FoxPlug only makes read requests either way.
v0
v0 is Vercel's AI app and interface builder where you chat to generate and refine web components and apps.
What it reads
- Your chats: the 25 most recently updated: chat id, title, updated or created time, and whether it is linked to a Vercel project
Moments
- A chat is updated since your last check. You keep refining a v0 chat titled Pricing table. After you press Check for what's new, FoxPlug makes one moment, 'Built in v0: Pricing table', with the chat title as its text, scored like any update.
- The chat is linked to a Vercel project. Same moment, with '(deploys to Vercel)' added to its description when the chat has a Vercel project. The deploy itself is read through the Vercel connection, not here.
Set up
- In v0, open your account settings and find the API keys page (v0's API docs, linked in the panel, say where).
- Make a new API key and name it FoxPlug.
- Copy the key and paste it into FoxPlug.
What it never reads
- Your prompts or generated code
- The deploy list (v0 deploys land on Vercel, which the Vercel connection reads)
Does FoxPlug read my v0 prompts or code?
No. It reads each chat's title, update time and whether it has a Vercel project.
Where do my v0 deploys show up?
In FoxPlug they come from the Vercel connection. Connect Vercel too if the v0 app deploys there.
Which v0 plan do I need?
The connect panel says v0's API is in beta and needs a Premium or Team plan.
FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.