@gaiventures/pilotfish-mcp-managed 0.1.15 → 0.1.17

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 +13 -2
  2. package/cli.js +1 -1
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -124,7 +124,7 @@ organization. Clients that sign in with OAuth (Claude.ai, Claude Desktop, Claude
124
124
  | `list_jobs` `{status?, limit?}` | Your recent jobs with their cost; `[replay]` marks recorded ones. |
125
125
  | `follow_up` `{id, text, model?, files?, wait?}` | Carry on in the same session: same browser while it is kept, same sign-ins, what earlier turns found. |
126
126
  | `rerun_job` `{id, wait?}` | Run the same task with the same settings again. |
127
- | `answer_job` `{id, question_id, answer}` | Answer a job's question: yes, no, done, cancel or text. Codes and passwords go on the answer page, never here. |
127
+ | `answer_job` `{id, question_id, answer}` | Answer a job's question: yes, no, done, 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. |
128
128
  | `message_job` `{id, text}` | Steer a running job ("take the cheaper one"). It reads the message before its next step. |
129
129
  | `take_control` `{id}` / `hand_back` `{id}` | Pause a job and get a link to drive its browser yourself, then let it carry on from there. |
130
130
  | `cancel_job` `{id}` | Stop a job. Cancelling a tool call that is waiting on a job stops the job too. |
@@ -134,11 +134,22 @@ organization. Clients that sign in with OAuth (Claude.ai, Claude Desktop, Claude
134
134
  | `save_task` `{name, task? \| from_job?, …settings}` | Save a task, or a job's task with the settings it ran with. |
135
135
  | `update_saved_task` `{id, name?, task?, …settings}` | Rename a saved task or change its task or settings. |
136
136
  | `delete_saved_task` `{id}` | Delete a saved task. Its past runs stay in your history. |
137
- | `delete_session` `{id}` | Delete a session from your history: its turns, replay and files. Logins, saved tasks and spending stay. |
137
+ | `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. |
138
138
  | `list_logins` | Sites you have saved logins for, with what is stored and each site's settings. Never a password or code. Logins are added in the app. |
139
139
  | `get_settings` / `update_site_settings` `{site, residential?, stealth?, solve?}` | Your sites and their settings: residential IP (auto, always or never), stealth and CAPTCHA solving. |
140
140
  | `get_usage` `{days?}` | Your credit balance, this month's spending against your limits, and spending by category and model. |
141
141
 
142
+ ## Whole tasks or steps?
143
+
144
+ Send the whole web task in one `browser_task`, however many sites and steps it has: "find the cheapest return
145
+ flight on MakeMyTrip, then book a hotel near the beach for those dates on Booking.com", "read my last Swiggy
146
+ order and add it to my Splitwise group". pilotfish splits it into parts, asks for every sign-in it needs at the
147
+ start, carries what each site gives to the next (the flight's dates into the hotel search) and checks the end
148
+ result. Split it yourself only where a step is not browser work (your own code, files, an API) or needs your own
149
+ decision between steps; then send each browser step as its own `browser_task` with the values it needs written
150
+ in, or use `follow_up` to stay in the same browser and sign-ins. Say what may be completed without asking ("pay
151
+ with my saved card", "go ahead and submit"); anything else that is final waits for your yes.
152
+
142
153
  ## When a job needs you
143
154
 
144
155
  A one-time code, a CAPTCHA it could not clear, a sign-in or a payment to approve: clients that support it open
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.15" : "0.0.0-dev";
13
+ var VERSION = true ? "0.1.17" : "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.15",
3
+ "version": "0.1.17",
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",