@gaiventures/pilotfish-mcp-managed 0.1.37 → 0.1.39

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +5 -2
  2. package/cli.js +1 -1
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -46,7 +46,7 @@ Want a browser on your own computer for free, driven by your agent's own model,
46
46
  1. **Have an account.** [Sign up with Google](https://pilotfish.gai.ventures/signup) and name your organization (you
47
47
  become its primary admin), or accept an emailed invitation to join an existing one as a member or an admin.
48
48
  2. **Make sure the organization has credits.** Admins add them under **Org settings → Credits** in the app (pay as you go,
49
- from $5, with optional auto reload). Members run tasks on the organization's credits within any allowance an
49
+ from $5, with optional auto reload; new sign-ups get $1 of free credit to try it, while the offer lasts). Members run tasks on the organization's credits within any allowance an
50
50
  admin sets for them.
51
51
  3. **Connect your agent** (below). The simplest way is to sign in from your client, which then acts as you. Scripts,
52
52
  servers and shared agents use an API key instead (Org settings → API keys). The app's **MCP** page
@@ -188,7 +188,10 @@ make one in the app's **Org settings → API keys** and pick the project **Perso
188
188
  Personal project, with your own saved logins, and only you can see or manage it. Admins (the primary admin included)
189
189
  can always do this; a member can once an admin turns on **Allow personal API keys** on the member's page (turning it
190
190
  off revokes their keys at once), and then finds their keys on their Org settings page. Admins see each person's key
191
- usage, never the keys. Most people need no key at all: Claude Code, the Claude app, Cursor and VS Code sign in, and
191
+ usage, never the keys. Every key, personal ones included, can have a spending limit of its own: admins set it on the
192
+ key's page (a member sees the limit and how much of it is used, and asks an admin to change it). At the limit, new
193
+ tasks with that key are refused and running ones pause until it is raised; `get_usage` with a personal key says what
194
+ is left of it. Most people need no key at all: Claude Code, the Claude app, Cursor and VS Code sign in, and
192
195
  a client that starts this package signs in once with `login` (see **Sign in a terminal**).
193
196
 
194
197
  ## Projects
package/cli.js CHANGED
@@ -15,7 +15,7 @@ import { Client } from "@modelcontextprotocol/sdk/client/index.js";
15
15
  import { isJSONRPCRequest, isJSONRPCResultResponse } from "@modelcontextprotocol/sdk/types.js";
16
16
 
17
17
  // packages/mcp-managed/dist/version.js
18
- var VERSION = true ? "0.1.37" : "0.0.0-dev";
18
+ var VERSION = true ? "0.1.39" : "0.0.0-dev";
19
19
 
20
20
  // packages/mcp-managed/dist/bridge.js
21
21
  var DEFAULT_URL = "https://pilotfish-be.gai.ventures";
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@gaiventures/pilotfish-mcp-managed",
3
- "version": "0.1.37",
3
+ "version": "0.1.39",
4
4
  "description": "Whole browser tasks done in pilotfish's cloud for any MCP agent, signed in with your saved logins. mcprush.com-37c48d491684ec6011385ea5",
5
5
  "license": "MIT",
6
6
  "type": "module",