workermill 0.1.9 → 0.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "workermill",
-  "version": "0.1.9",
+  "version": "0.2.0",
   "description": "AI coding agent with multi-expert orchestration. Works with any LLM provider.",
   "type": "module",
   "bin": {
@@ -21,12 +21,18 @@
     "ai": "^6.0.0",
     "chalk": "^5.3.0",
     "commander": "^12.0.0",
+    "ink": "^5.2.1",
+    "ink-text-input": "^6.0.0",
+    "marked": "^17.0.5",
+    "marked-terminal": "^7.3.0",
     "ollama-ai-provider-v2": "^3.5.0",
     "ora": "^8.0.0",
+    "react": "^18.3.1",
     "zod": "^3.23.0"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
+    "@types/react": "^18.3.28",
     "tsup": "^8.0.0",
     "tsx": "^4.0.0",
     "typescript": "^5.5.0"

package/personas/planner.md

@@ -2,7 +2,7 @@
 name: Planner
 slug: planner
 description: Creates detailed implementation plans by analyzing the codebase
-tools: [read_file, glob, grep, ls, web_search, sub_agent]
+tools: [read_file, glob, grep, ls, sub_agent]
 ---
 
 You are a meticulous implementation planner. Your job is to analyze the codebase and create a detailed, step-by-step implementation plan for a given task.

package/dist/chunk-2NTK7H4W.js

@@ -1,10 +0,0 @@
-// node_modules/tsup/assets/esm_shims.js
-import path from "path";
-import { fileURLToPath } from "url";
-var getFilename = () => fileURLToPath(import.meta.url);
-var getDirname = () => path.dirname(getFilename());
-var __dirname = /* @__PURE__ */ getDirname();
-
-export {
-  __dirname
-};

package/dist/chunk-LVCJZJJH.js

@@ -1,29 +0,0 @@
-// src/terminal.js
-var currentStatusBar = "";
-function initTerminal() {
-}
-function setStatusBar(text) {
-  currentStatusBar = text;
-}
-function showStatusBar() {
-  if (currentStatusBar) {
-    process.stdout.write("\n" + currentStatusBar + "\n");
-  }
-}
-function exitTerminal() {
-}
-function isManaged() {
-  return false;
-}
-function getStatusBarText() {
-  return currentStatusBar;
-}
-
-export {
-  initTerminal,
-  setStatusBar,
-  showStatusBar,
-  exitTerminal,
-  isManaged,
-  getStatusBarText
-};

package/dist/terminal-ILMO7Z3P.js

@@ -1,17 +0,0 @@
-import {
-  exitTerminal,
-  getStatusBarText,
-  initTerminal,
-  isManaged,
-  setStatusBar,
-  showStatusBar
-} from "./chunk-LVCJZJJH.js";
-import "./chunk-2NTK7H4W.js";
-export {
-  exitTerminal,
-  getStatusBarText,
-  initTerminal,
-  isManaged,
-  setStatusBar,
-  showStatusBar
-};

package/personas/ml_engineer.md

@@ -1,32 +0,0 @@
----
-name: Data & ML Engineer
-slug: data_ml_engineer
-description: Data & ML specialist - ETL, pipelines, machine learning, MLOps
-tools: [bash, read_file, write_file, edit_file, patch, glob, grep, ls, fetch, git, web_search, todo, sub_agent]
----
-
-You are a Data & ML Engineer. You specialize in data pipelines, ETL, machine learning, model training, and MLOps.
-
-Your specialties:
-- ETL/ELT pipeline development
-- Data modeling and warehousing
-- Machine learning model training and evaluation
-- TensorFlow and PyTorch
-- LLM integration and prompt engineering
-- MLOps, model deployment, and monitoring
-- Apache Kafka, Airflow/Dagster orchestration
-- SQL optimization and analytics
-
-Collaboration Rules:
-1. Check sibling decisions for data and ML requirements
-2. Post decisions about data models, pipeline architecture, and ML approach
-3. Answer questions about data availability, transformations, and ML capabilities
-4. Coordinate with backend on data source integration and model serving
-
-Work Style:
-- Start with data model design and problem formulation
-- Build idempotent, replayable pipelines
-- Build reproducible training pipelines
-- Implement proper data validation and model testing
-- Document data lineage, transformations, and model performance
-- Consider downstream consumers and inference latency