@integrity-labs/agt-cli 0.28.1149 → 0.28.1151
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/dist/bin/agt.js +3 -3
- package/dist/{chunk-LMJH26IW.js → chunk-MVZDF2MR.js} +2 -2
- package/dist/lib/manager-worker.js +259 -25
- package/dist/lib/manager-worker.js.map +1 -1
- package/dist/mcp/index.js +8 -3
- package/package.json +1 -1
- /package/dist/{chunk-LMJH26IW.js.map → chunk-MVZDF2MR.js.map} +0 -0
package/dist/mcp/index.js
CHANGED
|
@@ -50798,7 +50798,7 @@ var ROUTINE_CADENCE_GUESS = external_exports.enum(["hourly", "daily", "weekdays"
|
|
|
50798
50798
|
);
|
|
50799
50799
|
server.tool(
|
|
50800
50800
|
"routine_propose",
|
|
50801
|
-
'Propose a recurring ROUTINE the user just asked you to take on. The platform sends them an accept/decline offer; on acceptance it creates the routine and its schedule with full lifecycle (hand-back anytime, approval ramp). Prefer this over schedule_create for recurring responsibilities. If the user named a time, pass it as `at` - the reply tells you the schedule that was actually compiled, so check it matches what they asked for before you go quiet. For a routine with MORE THAN ONE cadence (e.g. "check hourly, but only report once a day"), or several separate JOBS under one responsibility (e.g. "an hourly alert sweep AND a weekly health report"), or one job at several times of day (e.g. 08:00, 12:30 and 16:30), use `schedules` instead of the flat cadence_guess/at/day_of_week - one entry per schedule, each with its own cadence.',
|
|
50801
|
+
'Propose a recurring ROUTINE the user just asked you to take on. The platform sends them an accept/decline offer; on acceptance it creates the routine and its schedule with full lifecycle (hand-back anytime, approval ramp). Prefer this over schedule_create for recurring responsibilities. If the user named a time, pass it as `at` - the reply tells you the schedule that was actually compiled, so check it matches what they asked for before you go quiet. For a routine with MORE THAN ONE cadence (e.g. "check hourly, but only report once a day"), or several separate JOBS under one responsibility (e.g. "an hourly alert sweep AND a weekly health report"), or one job at several times of day (e.g. 08:00, 12:30 and 16:30), use `schedules` instead of the flat cadence_guess/at/day_of_week - one entry per schedule, each with its own cadence. A managing agent can propose a routine FOR an agent it manages by passing `target_agent`; the Accept then goes to that agent\'s human manager.',
|
|
50802
50802
|
{
|
|
50803
50803
|
name: external_exports.string().describe('Short routine name (e.g. "Morning inbox summary")'),
|
|
50804
50804
|
description: external_exports.string().describe("What the routine does, self-contained (this text is shown to the user and becomes the routine prompt basis)"),
|
|
@@ -50841,9 +50841,13 @@ server.tool(
|
|
|
50841
50841
|
})
|
|
50842
50842
|
).optional().describe(
|
|
50843
50843
|
'One entry per schedule, for a routine that runs on more than one cadence (up to 8). At least one entry must have role "execute". Examples: hourly execute plus a daily report at 17:00 - [{role:"execute", cadence_guess:"hourly"}, {role:"daily-report", cadence_guess:"daily", at:"17:00"}]; two independent jobs - [{role:"execute", name:"Alert sweep", instructions:"...", cadence_guess:"hourly"}, {role:"execute", name:"Weekly health report", instructions:"...", cadence_guess:"weekly", at:"09:00", day_of_week:1}]. Omit entirely for a routine with one job on one cadence and use the flat cadence_guess/at/day_of_week instead - simpler, and what most routines want.'
|
|
50844
|
+
),
|
|
50845
|
+
// ENG-11649: a managing agent setting up recurring work for a report.
|
|
50846
|
+
target_agent: external_exports.string().optional().describe(
|
|
50847
|
+
'Propose this routine FOR another agent you manage (its code_name, e.g. "watson"), instead of for yourself. You must be on its reports_to chain. The Accept card goes to ITS first human manager, not to whoever is chatting with you, and no fresh conversation is needed. On accept the routine is created on that agent and runs there; you get a notice on your own board with the outcome. Omit this to propose a routine for yourself.'
|
|
50844
50848
|
)
|
|
50845
50849
|
},
|
|
50846
|
-
async ({ name, description, cadence_guess, at, timezone, day_of_week, schedules }) => {
|
|
50850
|
+
async ({ name, description, cadence_guess, at, timezone, day_of_week, schedules, target_agent }) => {
|
|
50847
50851
|
let data;
|
|
50848
50852
|
try {
|
|
50849
50853
|
data = await apiPost("/host/routines/propose", {
|
|
@@ -50854,7 +50858,8 @@ server.tool(
|
|
|
50854
50858
|
...at ? { at } : {},
|
|
50855
50859
|
...timezone ? { timezone } : {},
|
|
50856
50860
|
...day_of_week !== void 0 ? { day_of_week } : {},
|
|
50857
|
-
...schedules ? { schedules } : {}
|
|
50861
|
+
...schedules ? { schedules } : {},
|
|
50862
|
+
...target_agent ? { target_agent } : {}
|
|
50858
50863
|
});
|
|
50859
50864
|
} catch (err) {
|
|
50860
50865
|
return { content: [{ type: "text", text: `Could not propose: ${err.message}` }] };
|
package/package.json
CHANGED
|
File without changes
|