@askexenow/exe-os 0.9.3 → 0.9.5
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/cli.js +1020 -539
- package/dist/bin/exe-agent.js +4 -4
- package/dist/bin/exe-boot.js +4 -4
- package/dist/bin/exe-call.js +4 -4
- package/dist/bin/exe-launch-agent.js +4 -4
- package/dist/bin/setup.js +4 -4
- package/dist/lib/employee-templates.js +4 -4
- package/dist/mcp/server.js +14 -0
- package/dist/mcp/tools/create-task.js +14 -0
- package/dist/tui/App.js +4 -4
- package/package.json +1 -1
package/dist/bin/exe-agent.js
CHANGED
|
@@ -1463,10 +1463,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
|
|
|
1463
1463
|
Use store_memory to write a structured summary. Include: project name, what was done,
|
|
1464
1464
|
decisions made, tests status, open items or risks.
|
|
1465
1465
|
|
|
1466
|
-
6. AFTER committing changes to exe-os itself \u2014 REBUILD
|
|
1467
|
-
-
|
|
1468
|
-
-
|
|
1469
|
-
-
|
|
1466
|
+
6. AFTER committing changes to exe-os itself \u2014 REBUILD:
|
|
1467
|
+
- If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
|
|
1468
|
+
- If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
|
|
1469
|
+
- Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
|
|
1470
1470
|
- If the build fails, fix the error and retry before moving on.
|
|
1471
1471
|
|
|
1472
1472
|
7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
|
package/dist/bin/exe-boot.js
CHANGED
|
@@ -8285,10 +8285,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
|
|
|
8285
8285
|
Use store_memory to write a structured summary. Include: project name, what was done,
|
|
8286
8286
|
decisions made, tests status, open items or risks.
|
|
8287
8287
|
|
|
8288
|
-
6. AFTER committing changes to exe-os itself \u2014 REBUILD
|
|
8289
|
-
-
|
|
8290
|
-
-
|
|
8291
|
-
-
|
|
8288
|
+
6. AFTER committing changes to exe-os itself \u2014 REBUILD:
|
|
8289
|
+
- If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
|
|
8290
|
+
- If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
|
|
8291
|
+
- Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
|
|
8292
8292
|
- If the build fails, fix the error and retry before moving on.
|
|
8293
8293
|
|
|
8294
8294
|
7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
|
package/dist/bin/exe-call.js
CHANGED
|
@@ -596,10 +596,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
|
|
|
596
596
|
Use store_memory to write a structured summary. Include: project name, what was done,
|
|
597
597
|
decisions made, tests status, open items or risks.
|
|
598
598
|
|
|
599
|
-
6. AFTER committing changes to exe-os itself \u2014 REBUILD
|
|
600
|
-
-
|
|
601
|
-
-
|
|
602
|
-
-
|
|
599
|
+
6. AFTER committing changes to exe-os itself \u2014 REBUILD:
|
|
600
|
+
- If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
|
|
601
|
+
- If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
|
|
602
|
+
- Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
|
|
603
603
|
- If the build fails, fix the error and retry before moving on.
|
|
604
604
|
|
|
605
605
|
7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
|
|
@@ -2019,10 +2019,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
|
|
|
2019
2019
|
Use store_memory to write a structured summary. Include: project name, what was done,
|
|
2020
2020
|
decisions made, tests status, open items or risks.
|
|
2021
2021
|
|
|
2022
|
-
6. AFTER committing changes to exe-os itself \u2014 REBUILD
|
|
2023
|
-
-
|
|
2024
|
-
-
|
|
2025
|
-
-
|
|
2022
|
+
6. AFTER committing changes to exe-os itself \u2014 REBUILD:
|
|
2023
|
+
- If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
|
|
2024
|
+
- If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
|
|
2025
|
+
- Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
|
|
2026
2026
|
- If the build fails, fix the error and retry before moving on.
|
|
2027
2027
|
|
|
2028
2028
|
7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
|
package/dist/bin/setup.js
CHANGED
|
@@ -4400,10 +4400,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
|
|
|
4400
4400
|
Use store_memory to write a structured summary. Include: project name, what was done,
|
|
4401
4401
|
decisions made, tests status, open items or risks.
|
|
4402
4402
|
|
|
4403
|
-
6. AFTER committing changes to exe-os itself \u2014 REBUILD
|
|
4404
|
-
-
|
|
4405
|
-
-
|
|
4406
|
-
-
|
|
4403
|
+
6. AFTER committing changes to exe-os itself \u2014 REBUILD:
|
|
4404
|
+
- If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
|
|
4405
|
+
- If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
|
|
4406
|
+
- Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
|
|
4407
4407
|
- If the build fails, fix the error and retry before moving on.
|
|
4408
4408
|
|
|
4409
4409
|
7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
|
|
@@ -307,10 +307,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
|
|
|
307
307
|
Use store_memory to write a structured summary. Include: project name, what was done,
|
|
308
308
|
decisions made, tests status, open items or risks.
|
|
309
309
|
|
|
310
|
-
6. AFTER committing changes to exe-os itself \u2014 REBUILD
|
|
311
|
-
-
|
|
312
|
-
-
|
|
313
|
-
-
|
|
310
|
+
6. AFTER committing changes to exe-os itself \u2014 REBUILD:
|
|
311
|
+
- If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
|
|
312
|
+
- If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
|
|
313
|
+
- Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
|
|
314
314
|
- If the build fails, fix the error and retry before moving on.
|
|
315
315
|
|
|
316
316
|
7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
|
package/dist/mcp/server.js
CHANGED
|
@@ -11287,6 +11287,8 @@ ${typeBreakdown}`
|
|
|
11287
11287
|
init_tasks();
|
|
11288
11288
|
init_active_agent();
|
|
11289
11289
|
init_tmux_routing();
|
|
11290
|
+
init_employees();
|
|
11291
|
+
init_plan_limits();
|
|
11290
11292
|
import { z as z7 } from "zod";
|
|
11291
11293
|
function registerCreateTask(server2) {
|
|
11292
11294
|
server2.registerTool(
|
|
@@ -11309,6 +11311,18 @@ function registerCreateTask(server2) {
|
|
|
11309
11311
|
}
|
|
11310
11312
|
},
|
|
11311
11313
|
async ({ title, assigned_to, project_name, priority, complexity, context, blocked_by, parent_task_id, reviewer, budget_tokens, budget_fallback_model }) => {
|
|
11314
|
+
if (!isCoordinatorName(assigned_to)) {
|
|
11315
|
+
const license = getLicenseSync();
|
|
11316
|
+
if (license.plan === "free") {
|
|
11317
|
+
return {
|
|
11318
|
+
content: [{
|
|
11319
|
+
type: "text",
|
|
11320
|
+
text: "Upgrade to hire specialists. Free plan includes your COO only. Get a license at https://askexe.com"
|
|
11321
|
+
}],
|
|
11322
|
+
isError: true
|
|
11323
|
+
};
|
|
11324
|
+
}
|
|
11325
|
+
}
|
|
11312
11326
|
const { agentId: assignedBy } = getActiveAgent();
|
|
11313
11327
|
const task = await createTask({
|
|
11314
11328
|
title,
|
|
@@ -4618,6 +4618,8 @@ function getActiveAgent() {
|
|
|
4618
4618
|
|
|
4619
4619
|
// src/mcp/tools/create-task.ts
|
|
4620
4620
|
init_tmux_routing();
|
|
4621
|
+
init_employees();
|
|
4622
|
+
init_plan_limits();
|
|
4621
4623
|
function registerCreateTask(server) {
|
|
4622
4624
|
server.registerTool(
|
|
4623
4625
|
"create_task",
|
|
@@ -4639,6 +4641,18 @@ function registerCreateTask(server) {
|
|
|
4639
4641
|
}
|
|
4640
4642
|
},
|
|
4641
4643
|
async ({ title, assigned_to, project_name, priority, complexity, context, blocked_by, parent_task_id, reviewer, budget_tokens, budget_fallback_model }) => {
|
|
4644
|
+
if (!isCoordinatorName(assigned_to)) {
|
|
4645
|
+
const license = getLicenseSync();
|
|
4646
|
+
if (license.plan === "free") {
|
|
4647
|
+
return {
|
|
4648
|
+
content: [{
|
|
4649
|
+
type: "text",
|
|
4650
|
+
text: "Upgrade to hire specialists. Free plan includes your COO only. Get a license at https://askexe.com"
|
|
4651
|
+
}],
|
|
4652
|
+
isError: true
|
|
4653
|
+
};
|
|
4654
|
+
}
|
|
4655
|
+
}
|
|
4642
4656
|
const { agentId: assignedBy } = getActiveAgent();
|
|
4643
4657
|
const task = await createTask({
|
|
4644
4658
|
title,
|
package/dist/tui/App.js
CHANGED
|
@@ -16773,10 +16773,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
|
|
|
16773
16773
|
Use store_memory to write a structured summary. Include: project name, what was done,
|
|
16774
16774
|
decisions made, tests status, open items or risks.
|
|
16775
16775
|
|
|
16776
|
-
6. AFTER committing changes to exe-os itself \u2014 REBUILD
|
|
16777
|
-
-
|
|
16778
|
-
-
|
|
16779
|
-
-
|
|
16776
|
+
6. AFTER committing changes to exe-os itself \u2014 REBUILD:
|
|
16777
|
+
- If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
|
|
16778
|
+
- If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
|
|
16779
|
+
- Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
|
|
16780
16780
|
- If the build fails, fix the error and retry before moving on.
|
|
16781
16781
|
|
|
16782
16782
|
7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
|
package/package.json
CHANGED