@quantish/agent 0.1.34 → 0.1.36

package/dist/index.js

@@ -35,12 +35,13 @@ var schema = {
     default: DEFAULT_MCP_URL
   },
   model: {
-    type: "string",
-    default: "claude-sonnet-4-5-20250929"
+    type: "string"
+    // No default here - getModel() returns provider-specific default
   },
   provider: {
     type: "string",
-    default: "anthropic"
+    default: "openrouter"
+    // OpenRouter is recommended for new users
   }
 };
 var ConfigManager = class {
@@ -3571,35 +3572,37 @@ function extractTokenInfo(token) {
 }
 var DEFAULT_SYSTEM_PROMPT = `You are Quantish, an AI coding and trading agent.
 
-## Trading Tools (via MCP)
-- Check wallet balances and positions
-- Place, cancel, and manage orders  
-- Get market prices and orderbook data
-- Search markets on Polymarket, Kalshi, Limitless
+## MCP Architecture (3 servers)
+
+**Discovery MCP** - ALWAYS use for searching/finding markets:
+- search_markets(query) - Search across Polymarket, Kalshi, Limitless
+- get_trending_markets() - Find hot markets
+- get_market_details(platform, marketId) - Get details for any market
+- find_arbitrage() - Find arbitrage opportunities
+
+**Polymarket MCP** - Use for Polymarket trading:
+- place_order, cancel_order, get_orders
+- get_balances, get_positions
+- get_wallet_status, setup_wallet
+
+**Kalshi MCP** - Use for Kalshi trading via DFlow on Solana:
+- kalshi_buy_yes, kalshi_buy_no, kalshi_sell_position
+- kalshi_get_balances, kalshi_get_positions
+- kalshi_search_markets (backup if Discovery unavailable)
+
+## Workflow for trading:
+1. Use Discovery MCP to find markets (search_markets)
+2. From results, get the platform (polymarket/kalshi) and market ID
+3. Use the appropriate trading MCP to execute trades
 
 ## Coding Tools (local)
 - read_file, write_file, edit_file, list_dir
 - grep (search), find_files
 - run_command (blocking), start_background_process (non-blocking)
-- git operations
-
-## IMPORTANT: Background vs Blocking Commands
-
-Use \`start_background_process\` for:
-- Dev servers: npm start, npm run dev, yarn dev, vite, next dev
-- Watch mode: npm run watch, tsc --watch
-- Any server or long-running process
-- Returns immediately with a process ID
-
-Use \`run_command\` for:
-- Quick commands: ls, cat, npm install, npm run build
-- One-time operations that complete quickly
-- Blocks until command finishes
 
-After starting a background process:
-1. Use \`get_process_output(process_id)\` to check if it started correctly
-2. Use \`list_processes()\` to see all running processes
-3. Use \`stop_process(process_id)\` to stop when done
+## Background vs Blocking Commands
+Use \`start_background_process\` for dev servers, watch mode, long-running processes.
+Use \`run_command\` for quick commands that complete immediately.
 
 ## Guidelines
 - Be concise
@@ -5424,7 +5427,7 @@ Stopped ${count} background process${count > 1 ? "es" : ""}.`);
 }
 
 // src/index.ts
-var VERSION = "0.1.34";
+var VERSION = "0.1.36";
 function cleanup() {
   if (processManager.hasRunning()) {
     const count = processManager.runningCount();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quantish/agent",
-  "version": "0.1.34",
+  "version": "0.1.36",
   "description": "AI-powered agent for trading on Polymarket and Kalshi",
   "type": "module",
   "bin": {