dank-ai 1.0.32 → 1.0.34

package/README.md

@@ -208,7 +208,6 @@ const agent = createAgent('my-agent')
   })
   .setPrompt('Your system prompt here')
   .setPromptingServer({
-    protocol: 'http',
     port: 3000,
     authentication: false,
     maxConnections: 50
@@ -220,6 +219,45 @@ const agent = createAgent('my-agent')
   });
 ```
 
+### Adding HTTP Routes
+
+HTTP automatically enables when you add routes. Here's a simple "Hello World" POST endpoint:
+
+```javascript
+const agent = createAgent('hello-agent')
+  .setLLM('openai', {
+    apiKey: process.env.OPENAI_API_KEY,
+    model: 'gpt-3.5-turbo'
+  })
+  .setPromptingServer({
+    port: 3000
+  })
+  // Add a POST endpoint (HTTP auto-enables)
+  .post('/hello', (req, res) => {
+    res.json({ 
+      message: 'Hello, World!',
+      received: req.body,
+      timestamp: new Date().toISOString()
+    });
+  });
+```
+
+**Test it:**
+```bash
+curl -X POST http://localhost:3000/hello \
+  -H "Content-Type: application/json" \
+  -d '{"name": "User"}'
+```
+
+**Response:**
+```json
+{
+  "message": "Hello, World!",
+  "received": {"name": "User"},
+  "timestamp": "2024-01-15T10:30:00.000Z"
+}
+```
+
 ### Supported LLM Providers
 
 #### OpenAI
@@ -287,7 +325,7 @@ Dank provides a comprehensive event system with three main sources of events. Ea
 #### 🎯 **Event Handler Patterns**
 
 ##### **1. Direct Prompting Events** (`request_output`)
-Events triggered when agents receive and respond to direct prompts via WebSocket or HTTP:
+Events triggered when agents receive and respond to direct prompts via HTTP:
 
 ```javascript
 agent
@@ -405,35 +443,10 @@ Events triggered by tool usage, following the pattern `tool:<tool-name>:<action>
 
 ```javascript
 agent
-  // HTTP Server Tool Events
-  .addHandler('tool:http-server:*', (data) => {
-    // Listen to ALL HTTP server events
-    console.log('HTTP Activity:', data.type, data.method, data.path);
-  })
-  
-  .addHandler('tool:http-server:call', (data) => {
-    // All incoming HTTP requests
-    console.log('Request:', data.method, data.path, data.body);
-  })
-  
-  .addHandler('tool:http-server:response', (data) => {
-    // All HTTP responses
-    console.log('Response:', data.statusCode, data.processingTime);
-  })
-  
-  .addHandler('tool:http-server:call:post', (data) => {
-    // Only POST requests
-    console.log('POST Request:', data.path, data.body);
-  })
-  
-  .addHandler('tool:http-server:response:get', (data) => {
-    // Only GET responses
-    console.log('GET Response:', data.path, data.responseData);
-  })
-  
-  .addHandler('tool:http-server:error', (data) => {
-    // HTTP server errors
-    console.error('HTTP Error:', data.error);
+  // Example: Tool events for built-in tools
+  .addHandler('tool:httpRequest:*', (data) => {
+    // Listen to ALL HTTP request tool events
+    console.log('HTTP Request Tool:', data);
   });
 ```
 
@@ -441,10 +454,10 @@ agent
 - `tool:<tool-name>:*` - All events for a specific tool
 - `tool:<tool-name>:call` - Tool invocation/input events
 - `tool:<tool-name>:response` - Tool output/result events
-- `tool:<tool-name>:call:<method>` - Specific method calls (e.g., POST, GET)
-- `tool:<tool-name>:response:<method>` - Specific method responses
 - `tool:<tool-name>:error` - Tool-specific errors
 
+**Note:** HTTP API routes (added via `.get()`, `.post()`, etc.) are part of the main HTTP server, not a separate tool. They don't emit tool events.
+
 ##### **3. System Events** (Legacy/System)
 Traditional system-level events:
 
@@ -480,10 +493,6 @@ agent
   console.log('Any tool activity:', data);
 })
 
-// Listen to all HTTP responses
-.addHandler('tool:http-server:response:*', (data) => {
-  console.log('Any HTTP response:', data);
-})
 
 // Listen to all request outputs
 .addHandler('request_output:*', (data) => {
@@ -517,7 +526,6 @@ agent
   prompt: "User's input prompt",
   response: "LLM's response",
   conversationId: "unique-conversation-id",
-  context: { protocol: "websocket", clientId: "..." },
   usage: { total_tokens: 150, prompt_tokens: 50, completion_tokens: 100 },
   model: "gpt-3.5-turbo",
   processingTime: 1250,
@@ -550,27 +558,20 @@ Each communication method can be enabled/disabled independently:
 createAgent('flexible-agent')
   // Configure direct prompting with specific settings
   .setPromptingServer({ 
-    protocol: 'websocket',
     port: 3000,
     authentication: false,
     maxConnections: 50
   })
   .disableDirectPrompting() // Disable if needed
   
-  // Enable HTTP API
-  .enableHttp({ port: 3001 })
-  
   // Listen to direct prompting events only
   .addHandler('request_output', (data) => {
-    console.log('WebSocket response:', data.response);
+    console.log('HTTP response:', data.response);
   })
   
-  // HTTP events will fire when routes are added
+  // Add HTTP API routes (HTTP auto-enables)
   .get('/api/status', (req, res) => {
     res.json({ status: 'ok' });
-  })
-  .addHandler('tool:http-server:*', (data) => {
-    console.log('HTTP activity:', data);
   });
 ```
 
@@ -629,7 +630,6 @@ module.exports = {
       })
       .setPrompt('You are a professional customer service representative.')
       .setPromptingServer({
-        protocol: 'http',
         port: 3000,
         authentication: true,
         maxConnections: 100
@@ -659,7 +659,6 @@ module.exports = {
       })
       .setPrompt('You are a data analysis expert.')
       .setPromptingServer({
-        protocol: 'http',
         port: 3001,
         authentication: false,
         maxConnections: 50
@@ -737,7 +736,7 @@ dank build:prod --config production.config.js --output-metadata deployment.json
 
 The `--output-metadata` option generates a JSON file containing all deployment information needed for your backend infrastructure:
 - **Base image** used (`setBaseImage()` value)
-- **Prompting server** configuration (protocol, port, authentication, maxConnections)
+- **Prompting server** configuration (port, authentication, maxConnections)
 - **Resource limits** (memory, CPU, timeout)
 - **Ports** that need to be opened
 - **Features enabled** (direct prompting, HTTP API, event handlers)
@@ -763,7 +762,6 @@ This metadata file is perfect for CI/CD pipelines to automatically configure you
         "tag": "nodejs-20"
       },
       "promptingServer": {
-        "protocol": "http",
         "port": 3000,
         "authentication": false,
         "maxConnections": 50,
@@ -777,7 +775,6 @@ This metadata file is perfect for CI/CD pipelines to automatically configure you
       "ports": [
         {
           "port": 3000,
-          "protocol": "http",
           "description": "Direct prompting server"
         }
       ],

package/bin/dank

@@ -90,6 +90,7 @@ program
   .option('--registry <registry>', 'Docker registry URL (e.g., docker.io, ghcr.io)')
   .option('--namespace <namespace>', 'Docker namespace/organization')
   .option('--tag-by-agent', 'Use agent name as the image tag (common image name)')
+  .option('--base-image-override <image>', 'Override base image for all agents (production builds only)')
   .option('--json', 'Output machine-readable JSON summary to stdout')
   .option('--output-metadata <file>', 'Output deployment metadata JSON file')
   .option('--force', 'Force rebuild without cache')