@gaiventures/pilotfish-mcp-managed 0.1.22 → 0.1.24
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.
- package/README.md +134 -14
- package/cli.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -21,8 +21,10 @@ Want a browser on your own computer for free, driven by your agent's own model,
|
|
|
21
21
|
|
|
22
22
|
- **One call per task.** pilotfish plans and runs the task on its own models and checks the answer. Your agent spends
|
|
23
23
|
a tool call or two, not a context full of web pages.
|
|
24
|
-
- **Signed in as you.** Save a login once in the app and every task can use it
|
|
25
|
-
two-factor codes, emailed codes and phone sign-in by code are handled.
|
|
24
|
+
- **Signed in as you.** Save a login once in the app and every task can use it, several accounts a site if you have
|
|
25
|
+
them. Sessions are kept between runs, and two-factor codes, emailed codes and phone sign-in by code are handled.
|
|
26
|
+
- **Or as each of your own users.** Building a product? Run tasks for your end users in a shared project, each as an
|
|
27
|
+
identity with their own logins, sessions, residential IP and device, and see what each one's tasks cost.
|
|
26
28
|
- **Gets through where plain browsers stop.** Residential IPs in your country, stealth browsing and CAPTCHA solving
|
|
27
29
|
are on by default, with per-site settings. When something truly needs you, you get a link.
|
|
28
30
|
- **Always on.** Tasks run in the cloud, so they carry on while your laptop sleeps. A follow-up picks up the same
|
|
@@ -39,7 +41,8 @@ Want a browser on your own computer for free, driven by your agent's own model,
|
|
|
39
41
|
from $10, with optional auto reload). Members run tasks on the organization's credits within any allowance an
|
|
40
42
|
admin sets for them.
|
|
41
43
|
3. **Connect your agent** (below). The simplest way is to sign in from your client, which then acts as you. Scripts,
|
|
42
|
-
servers and shared agents use one of the organization's API keys instead.
|
|
44
|
+
servers and shared agents use one of the organization's API keys instead. The app's **MCP** page
|
|
45
|
+
(`https://pilotfish.gai.ventures/connect`) has the endpoint and every client's setup.
|
|
43
46
|
|
|
44
47
|
## Connect
|
|
45
48
|
|
|
@@ -143,17 +146,125 @@ $env:PILOTFISH_KEY = "pf_YOUR_KEY"; npx -y @gaiventures/pilotfish-mcp-managed --
|
|
|
143
146
|
| --- | --- | --- |
|
|
144
147
|
| Who it acts as | You | The organization, as no particular person |
|
|
145
148
|
| Who can use it | Only you | Anyone who has the key: keep it secret |
|
|
146
|
-
|
|
|
149
|
+
| Project | Personal, until you `switch_project` | The one shared project it belongs to |
|
|
150
|
+
| Saved logins, site profiles, saved tasks | Yours (in Personal) | No one's: each end user's logins belong to an identity |
|
|
147
151
|
| Tasks it sees | Your own; an admin can also open any of the organization's tasks by id | Only the tasks started with that key |
|
|
148
152
|
| Paid from | The organization's credits, within your allowance if you have one | The organization's credits, within the key's allowance if it has one |
|
|
149
153
|
| Who sets it up | You, from your client | The organization's admins, under **Org settings → API keys** |
|
|
150
154
|
|
|
151
155
|
**About keys.** Admins create, show again, copy, rotate and revoke keys under **Org settings → API keys**
|
|
152
|
-
(`https://pilotfish.gai.ventures/org?view=keys`).
|
|
156
|
+
(`https://pilotfish.gai.ventures/org?view=keys`). Each key belongs to one shared project, picked when it is made
|
|
157
|
+
(Default unless chosen) and movable later. Rotating gives a new value under the same name, and the old one stops
|
|
153
158
|
working at once; rotate a key when someone who had it leaves. Each key has its own page with what it spent, its tasks
|
|
154
159
|
through the MCP and the API, and its sessions. An admin can give a key an allowance: a spending limit on the
|
|
155
160
|
organization's credits, with an optional automatic top-up.
|
|
156
161
|
|
|
162
|
+
**Personal MCP keys.** Admins (the primary admin included) can also make a key of their own on the app's **MCP**
|
|
163
|
+
page: it acts as them, in their Personal project, for their own scripts. A member can have them too once an admin turns
|
|
164
|
+
on **Allow personal MCP keys** on the member's page (Org settings → the person); turning it off revokes their keys at
|
|
165
|
+
once. Until then a member is told whom to ask, and connects their AI tool by signing in (no key needed). Admins see
|
|
166
|
+
each person's key usage.
|
|
167
|
+
|
|
168
|
+
## Projects
|
|
169
|
+
|
|
170
|
+
Every task runs in a project.
|
|
171
|
+
|
|
172
|
+
- **Personal** is your own: your saved logins (several accounts a site, one of them the default), saved and scheduled
|
|
173
|
+
tasks, connected inbox and site settings. It is where you are when you sign in, in the app or from an AI tool.
|
|
174
|
+
- **Shared projects** (Default, and any an admin creates) are for product companies running tasks for their own end
|
|
175
|
+
users. They hold no one's personal logins and no saved or scheduled tasks: each end user is an **identity** there. A
|
|
176
|
+
task with no identity gets a fresh browser of its own, and nothing of it is kept for other sessions.
|
|
177
|
+
|
|
178
|
+
Switch in the app's project switcher, or with `switch_project` (no argument lists your projects); the MCP remembers
|
|
179
|
+
your choice for your next connections. An organization API key always works in its own project.
|
|
180
|
+
|
|
181
|
+
## Identities: tasks for your own users
|
|
182
|
+
|
|
183
|
+
An identity (`idn_…`) is one of your end users. pilotfish keeps, on its servers, everything that makes them look like
|
|
184
|
+
the same person to a site: their logins for any number of sites (several accounts a site), their signed-in sessions,
|
|
185
|
+
a residential IP in their country (the same region every time, kept sticky) and their device fingerprint. None of it
|
|
186
|
+
is ever handed back. You only see its id, label, your own user id for it (`external_user_id`), its country and device
|
|
187
|
+
OS, which sites it has logins for (usernames masked), its credential ids, and what its tasks cost.
|
|
188
|
+
|
|
189
|
+
- **Manage them** with the `identities` tool (`list`, `create`, `get`, `update`, `delete`) or the REST API
|
|
190
|
+
(`/identities`). Creating one with an `external_user_id` you already used gives the existing one back.
|
|
191
|
+
- **Run a task as one** with `browser_task {identity: "idn_…"}`. A `follow_up` keeps the session's identity. Each
|
|
192
|
+
identity runs one task at a time.
|
|
193
|
+
- **Delete** wipes its logins, sessions and device for good. Its tasks and their costs stay, for your billing.
|
|
194
|
+
|
|
195
|
+
### Getting a user's logins in, without an AI seeing them
|
|
196
|
+
|
|
197
|
+
Each saved login gets a credential id (`cred_…`). A password never passes through the MCP. There are three ways in:
|
|
198
|
+
|
|
199
|
+
1. **A login link.** `identities {action: "login_link", id, sites: ["linkedin.com"]}` (or `POST /identities/:id/link`)
|
|
200
|
+
returns a one-time page, valid for 30 minutes (over REST, `ttlMinutes` sets 5 to 1440). Send it to your end user; they type their own login
|
|
201
|
+
there, and it is saved sealed to their identity.
|
|
202
|
+
2. **Your own server.** `POST /identities/:id/credentials {site, username, password?, totp?, account?, default?}`
|
|
203
|
+
with your API key, from your backend. The MCP refuses this route.
|
|
204
|
+
3. **Sign-ins during a task.** With `save_logins: true` on the identity, a sign-in typed during one of its tasks is
|
|
205
|
+
kept once it works. Off by default; the signed-in session is kept either way.
|
|
206
|
+
|
|
207
|
+
Use them in a task with `credentials: ["cred_…"]`, or name the account per site with
|
|
208
|
+
`accounts: {"linkedin.com": "work"}`.
|
|
209
|
+
|
|
210
|
+
### Which account a task uses
|
|
211
|
+
|
|
212
|
+
When a site has several saved accounts (yours in Personal, or an identity's), a task takes, in order: the one the
|
|
213
|
+
request names (`accounts`, `credentials` or `login`), the one the session already chose, the one the person's own
|
|
214
|
+
words name (its name, or its username or email), the site's default, or the only one saved. Otherwise it asks once, at
|
|
215
|
+
the start: each saved account, **Use another login**, **Create a new account** or **Go without signing in**. A
|
|
216
|
+
scheduled run never asks: it takes the default, else the main account. Set a default with `manage_login {action: "set_default"}` (Personal)
|
|
217
|
+
or `identities {action: "set_default", credential}`.
|
|
218
|
+
|
|
219
|
+
### Updating a login
|
|
220
|
+
|
|
221
|
+
When an end user changes a password, send them a new login link for that site (and account, if it has a name):
|
|
222
|
+
`identities {action: "login_link", id, sites: ["linkedin.com"], account: "work"}`. What they type replaces the saved
|
|
223
|
+
login, and its credential id stays the same. Your own server can do the same with
|
|
224
|
+
`POST /identities/:id/credentials` (same site and account). A signed-in session the site keeps is used as long as it
|
|
225
|
+
lasts; the saved login signs in again when it ends.
|
|
226
|
+
|
|
227
|
+
### Usage per project
|
|
228
|
+
|
|
229
|
+
Admins see every shared project's API keys, identities and this month's spend in Org settings → Projects, or with
|
|
230
|
+
`projects {action: "list"}`; `projects {action: "usage", id, days}` gives one project's spend by kind and per key
|
|
231
|
+
(`GET /org/projects`, `GET /org/projects/:id/usage?days=`).
|
|
232
|
+
|
|
233
|
+
### What each task cost
|
|
234
|
+
|
|
235
|
+
Every result has the same layout: the outcome first (`SUCCESS`, `PARTLY DONE` or `NOT DONE`), the answer, then
|
|
236
|
+
the job, its cost by kind and where it ran:
|
|
237
|
+
|
|
238
|
+
```text
|
|
239
|
+
SUCCESS
|
|
240
|
+
Result: Applied to 3 roles: …
|
|
241
|
+
Job: job_Ab12… · 14 steps
|
|
242
|
+
Cost: $0.0213 (model $0.0081, residential IP $0.0104, browser $0.0020, CAPTCHA $0.0008)
|
|
243
|
+
Project: Acme HR app (prj_acme)
|
|
244
|
+
Identity: idn_7Hq2…
|
|
245
|
+
Open in pilotfish: https://…/tasks/job_Ab12…
|
|
246
|
+
```
|
|
247
|
+
|
|
248
|
+
`identities {action: "get"}` and `GET /identities/:id/usage?since=` give an identity's totals (tasks; model,
|
|
249
|
+
residential IP, browser and CAPTCHA cost) and each task's cost, so you can bill your own users.
|
|
250
|
+
|
|
251
|
+
### An example: Acme HR
|
|
252
|
+
|
|
253
|
+
Acme HR runs LinkedIn tasks for its users Priya (in India) and Rahul (in the US). An admin creates the shared project
|
|
254
|
+
"Acme HR" and an API key in it, and Acme's server connects with that key.
|
|
255
|
+
|
|
256
|
+
1. One identity per user:
|
|
257
|
+
`identities {action: "create", external_user_id: "u_1042", label: "Priya", country: "in"}` and
|
|
258
|
+
`identities {action: "create", external_user_id: "u_2077", label: "Rahul", country: "us"}`.
|
|
259
|
+
2. A login link for each: `identities {action: "login_link", id: "idn_priya…", sites: ["linkedin.com"]}`. Acme shows
|
|
260
|
+
the link in its own app; Priya signs in to LinkedIn there. Rahul does the same with his.
|
|
261
|
+
3. Tasks by identity: `browser_task {identity: "idn_priya…", task: "Read my new LinkedIn messages and list who wrote"}`.
|
|
262
|
+
It runs on Priya's LinkedIn session, from an Indian residential IP on her own device; Rahul's runs from the US on his.
|
|
263
|
+
4. The cost: each result ends with `Cost: …` and `identity: idn_priya…`; at month end Acme reads
|
|
264
|
+
`GET /identities/idn_priya…/usage?since=…` for each user and bills them.
|
|
265
|
+
5. Priya leaves: `identities {action: "delete", id: "idn_priya…"}` wipes her LinkedIn login, session and device. Her
|
|
266
|
+
past tasks and their costs stay in Acme's usage.
|
|
267
|
+
|
|
157
268
|
## Organizations, members and money
|
|
158
269
|
|
|
159
270
|
Everyone is in one organization, and its credits pay for every task its people and its keys run.
|
|
@@ -164,7 +275,8 @@ Everyone is in one organization, and its credits pay for every task its people a
|
|
|
164
275
|
| Add credits, card, auto reload | Yes | Yes | No |
|
|
165
276
|
| Monthly limit and overage | Yes | Yes | No |
|
|
166
277
|
| Invite people, change roles, set allowances | Yes | Yes | No |
|
|
167
|
-
| Create and manage API keys | Yes | Yes | No |
|
|
278
|
+
| Create and manage API keys, and shared projects | Yes | Yes | No |
|
|
279
|
+
| A personal MCP key | Yes | Yes | When an admin turns it on (else they sign in from their client) |
|
|
168
280
|
| See everyone's tasks and spending | Yes | Yes | No: their own, and their allowance |
|
|
169
281
|
| Hand the primary admin role to someone else | Yes | No | No |
|
|
170
282
|
|
|
@@ -172,8 +284,8 @@ Everyone is in one organization, and its credits pay for every task its people a
|
|
|
172
284
|
the default. When it is used up, new tasks are refused and running ones pause until an admin raises it.
|
|
173
285
|
- **The monthly limit.** An admin may set one for the whole organization. The primary admin is emailed at 80% and at
|
|
174
286
|
100%; at the limit, tasks pause and new ones are refused until an admin turns on overage or raises the limit.
|
|
175
|
-
- **One task at a time** per person and per
|
|
176
|
-
or is stopped.
|
|
287
|
+
- **One task at a time** per person, per key and per identity. Another task started meanwhile is refused until the
|
|
288
|
+
first finishes or is stopped.
|
|
177
289
|
- **Check-ins on long tasks.** A task that has spent a set amount ($1 by default) pauses and says what it found so
|
|
178
290
|
far; carry on with a follow-up, and it checks in again at the next step of that amount.
|
|
179
291
|
- **What your agent sees.** A refused task comes back with the reason and whom to ask:
|
|
@@ -193,11 +305,11 @@ the monthly limit and spending by category and by model.
|
|
|
193
305
|
|
|
194
306
|
| Tool | What it does |
|
|
195
307
|
| --- | --- |
|
|
196
|
-
| `browser_task` `{task, start_url?, region?, sites?, login?, stealth?, solve?, model?, quality?, max_steps?, pre_approved?, files?, wait?, wait_seconds?}` | Run a whole web task, however many sites and steps. Waits up to `wait_seconds` (default 120) and returns the result, or the job id if it is still running (it carries on; `get_job` waits again). `wait: false` returns the id at once. `model`: `gpt-6-luna` (the default), `auto` (Haiku does the task, Sonnet checks it), or one model for every step: `opus`, `sonnet`, `haiku`, `gpt-5-mini` or `gpt-5-nano`. `quality` (`auto`, `economy`, `accurate`) instead of one model; `model` wins. `region`: the country to browse from (`"us"`, `"in"`). `start_url`: the page to open first. `sites`: further sites whose saved logins the task may use. `login`: which of your accounts on those sites. `stealth` and `solve`: on by default; `false` turns them off for this run. `max_steps`: browser actions across the run. `pre_approved` (`{actions: [pay, delete, send, transfer, cancel], max_amount?, currency?}`): only with the person's say-so, final steps that run without asking. `files`: up to 10 attachments (`{name, type?, data}` in base64, 25 MB each). |
|
|
308
|
+
| `browser_task` `{task, start_url?, region?, sites?, login?, accounts?, identity?, credentials?, stealth?, solve?, model?, quality?, max_steps?, pre_approved?, files?, wait?, wait_seconds?}` | Run a whole web task, however many sites and steps. Waits up to `wait_seconds` (default 120) and returns the result with its cost by kind and its project and identity, or the job id if it is still running (it carries on; `get_job` waits again). `wait: false` returns the id at once. `model`: `gpt-6-luna` (the default), `auto` (Haiku does the task, Sonnet checks it), or one model for every step: `opus`, `sonnet`, `haiku`, `gpt-5-mini` or `gpt-5-nano`. `quality` (`auto`, `economy`, `accurate`) instead of one model; `model` wins. `region`: the country to browse from (`"us"`, `"in"`). `start_url`: the page to open first. `sites`: further sites whose saved logins the task may use. `login`: which of your accounts on those sites; `accounts` (`{"linkedin.com": "work"}`, `""` the main one): which account on each site. `identity` (`idn_…`, in a shared project): run as that end user; `credentials` (`["cred_…"]`): which of its saved logins. `stealth` and `solve`: on by default; `false` turns them off for this run. `max_steps`: browser actions across the run. `pre_approved` (`{actions: [pay, delete, send, transfer, cancel], max_amount?, currency?}`): only with the person's say-so, final steps that run without asking. `files`: up to 10 attachments (`{name, type?, data}` in base64, 25 MB each). |
|
|
197
309
|
| `get_job` `{id, wait_seconds?}` | A job's status, its open question with the link to answer it, the result, the cost so far, the live-view link while it runs, and the session's files. `wait_seconds` waits for it to finish or need you first. |
|
|
198
310
|
| `get_file` `{id, file_id}` | One of the session's files, attached or downloaded. Up to 5 MB comes back in the result (an image as an image, text as text); larger files are linked in the app. |
|
|
199
311
|
| `list_jobs` `{status?, limit?}` | Your recent jobs, newest first, with their cost; `[replay]` marks recorded ones. `status`: `queued`, `running`, `needs_input`, `done`, `failed` or `cancelled`. |
|
|
200
|
-
| `follow_up` `{id, text, model?, region?, files?, wait?, wait_seconds?}` | Carry on in the same session: the same browser while it is kept, the same sign-ins, what earlier turns found ("now also…", "open the second one", "try again with…"). `model` changes this turn's model (`auto` routes again). `region` runs the turn from another country, in a new browser session there. |
|
|
312
|
+
| `follow_up` `{id, text, model?, region?, files?, wait?, wait_seconds?}` | Carry on in the same session: the same browser while it is kept, the same sign-ins, what earlier turns found ("now also…", "open the second one", "try again with…"). `model` changes this turn's model (`auto` routes again). `region` runs the turn from another country, in a new browser session there. The session keeps its project and identity. |
|
|
201
313
|
| `rerun_job` `{id, wait?, wait_seconds?}` | Run the same task again with the same settings, as a new job. |
|
|
202
314
|
| `answer_job` `{id, question_id, answer}` | Answer a job's question: `yes`, `no`, `done` (handled in the browser), `cancel`, or text. The id is in the job's `Question …` line, which also says what answer it takes. Codes and passwords go on the answer page, never here. |
|
|
203
315
|
| `message_job` `{id, text}` | Pass on what the person says while a job runs ("take the cheaper one", a detail it asked for), in their words. It reads the message before its next step, and the person's newest words win over the task; sent while the job waits on a question, it answers it. |
|
|
@@ -206,18 +318,23 @@ the monthly limit and spending by category and by model.
|
|
|
206
318
|
| `get_replay` `{id}` | The job's steps with timings and what got in the way, and a link to its replay video (valid for an hour) when one was recorded. |
|
|
207
319
|
| `list_saved_tasks` | Your saved tasks: id, name, settings, how often and when they last ran, and what their last run needed. |
|
|
208
320
|
| `run_saved_task` `{id, extra_instructions?, start_url?, region?, sites?, stealth?, solve?, wait?, wait_seconds?}` | Run a saved task with its saved settings, with optional changes for this run only. |
|
|
209
|
-
| `save_task` `{name, task? \| from_job?, start_url?, region?, sites?, login?, stealth?, solve?, model?, quality?}` | Save a task to run again here or in the app: give the task and settings, or `from_job` to save a job's task with the settings it ran with. |
|
|
321
|
+
| `save_task` `{name, task? \| from_job?, start_url?, region?, sites?, login?, accounts?, stealth?, solve?, model?, quality?}` | Save a task to run again here or in the app: give the task and settings, or `from_job` to save a job's task with the settings it ran with. |
|
|
210
322
|
| `update_saved_task` `{id, name?, task?, …settings}` | Rename a saved task, change its task, or change only the settings given. |
|
|
211
323
|
| `delete_saved_task` `{id}` | Delete a saved task. Its past runs stay in your history. |
|
|
212
324
|
| `delete_session` `{id}` | Delete a session from your history: it no longer shows or opens anywhere; its record and cost are kept for billing. Logins, saved tasks and spending stay. Only with the person's say-so. |
|
|
213
|
-
| `list_logins` | Sites with saved logins: which accounts, whether a password and authenticator key are stored, what recent runs met there. Never a password or code.
|
|
325
|
+
| `list_logins` | Sites with saved logins in your Personal project: which accounts, whether a password and authenticator key are stored, what recent runs met there. Never a password or code. |
|
|
326
|
+
| `manage_login` `{action, site, account?}` | Your Personal logins. `add`: a link to the app where you type the login yourself (never in the chat). `set_default`: the account tasks use on a site with several when they don't say. `delete`: forget one. `save_offered` / `discard_offered`: a sign-in a run offered for saving. |
|
|
327
|
+
| `projects` `{action, id?, name?, days?}` | Admins: your organization's shared projects. `list` (each with its API keys, identities and this month's spend), `create`, `rename`, `delete` (wipes its identities, revokes its keys; its tasks' cost stays), `usage` (one project's spend by kind and per key over `days`), `keys` (its keys and what each spent). New API keys are made in the app (Org settings → API keys): a key's value never passes through a chat. |
|
|
328
|
+
| `switch_project` `{project?}` | Which project your tasks run in: `personal`, `default` or a project's id or name. No argument lists them. Remembered for your next connections; an organization API key stays in its own. |
|
|
329
|
+
| `identities` `{action, id?, external_user_id?, label?, query?, country?, device_os?, email?, save_logins?, sites?, account?, credential?}` | Your end users in a shared project. `list` (by `external_user_id` or `query`), `create`, `get` (logins by credential id, masked; signed-in sites; cost so far), `update`, `delete` (wipes logins, sessions and device; costs stay), `login_link` (`sites`: a one-time page for the user to type their own login), `set_default` and `delete_login` (by `credential`). |
|
|
214
330
|
| `get_settings` / `update_site_settings` `{site, residential?, stealth?, solve?}` | Your sites and their settings, and change one site's: residential IP (`auto`, `always` or `never`), stealth browsing, CAPTCHA solving. A change applies to every later task on that site. |
|
|
215
331
|
| `get_usage` `{days?}` | Your organization's credits as your role sees them (an admin: its balance and auto reload; a member: whether it is fine, low, out or at its limit), what is left of your allowance (or the key's), this month's spending against the organization's monthly limit, and the last `days` (default 30) of spending by category (model, residential IP, browser, CAPTCHA) and by model. |
|
|
216
332
|
|
|
217
333
|
## What a job returns
|
|
218
334
|
|
|
219
335
|
A finished job starts with `SUCCESS`, `PARTLY DONE` or `NOT DONE`. One that did not fully pass lists what of the task
|
|
220
|
-
is done, what is not (each with its evidence) and why it stopped.
|
|
336
|
+
is done, what is not (each with its evidence) and why it stopped. Every finished job ends with a `Cost:` line (model,
|
|
337
|
+
residential IP, browser, CAPTCHA) and a `Project:` line naming its project and identity. A job still running says `Still running after
|
|
221
338
|
120 s; the job carries on`, and your agent waits again with `get_job`. A job that needs a person shows the question,
|
|
222
339
|
a `Question <id>` line saying how to answer it, and the answer link.
|
|
223
340
|
|
|
@@ -265,7 +382,7 @@ Only for this package (the relay). Clients that connect to the URL need none.
|
|
|
265
382
|
|
|
266
383
|
| Variable | Default | Meaning |
|
|
267
384
|
| --- | --- | --- |
|
|
268
|
-
| `PILOTFISH_KEY` | |
|
|
385
|
+
| `PILOTFISH_KEY` | | An API key (`pf_…`): one of your organization's, or a personal key (admins, and members an admin allowed). Required. |
|
|
269
386
|
| `PILOTFISH_URL` | `https://pilotfish-be.gai.ventures` | The pilotfish API, or its `/mcp` URL. |
|
|
270
387
|
|
|
271
388
|
## Troubleshooting
|
|
@@ -275,6 +392,9 @@ Only for this package (the relay). Clients that connect to the URL need none.
|
|
|
275
392
|
- **Codex stops the call after a minute:** keep `tool_timeout_sec = 180` as above; the task itself carries on.
|
|
276
393
|
- **`npx` fails, or the relay won't start:** check `node --version` is 22 or newer; on Windows, start it through
|
|
277
394
|
`cmd /c` as above.
|
|
395
|
+
- **`shared_project` or `personal_project`:** saved logins and saved tasks are in Personal, identities in a shared
|
|
396
|
+
project: `switch_project` to the right one (an organization API key stays in its own).
|
|
397
|
+
- **`identity_busy`:** that identity already has a task running; wait for it or stop it.
|
|
278
398
|
- **A task is refused:** the reason and whom to ask are in the result; the table under "Organizations, members and
|
|
279
399
|
money" above lists each one.
|
|
280
400
|
|
package/cli.js
CHANGED
|
@@ -10,7 +10,7 @@ import { Client } from "@modelcontextprotocol/sdk/client/index.js";
|
|
|
10
10
|
import { isJSONRPCRequest, isJSONRPCResultResponse } from "@modelcontextprotocol/sdk/types.js";
|
|
11
11
|
|
|
12
12
|
// packages/mcp-managed/dist/version.js
|
|
13
|
-
var VERSION = true ? "0.1.
|
|
13
|
+
var VERSION = true ? "0.1.24" : "0.0.0-dev";
|
|
14
14
|
|
|
15
15
|
// packages/mcp-managed/dist/bridge.js
|
|
16
16
|
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.
|
|
3
|
+
"version": "0.1.24",
|
|
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",
|