@ainative/cody-cli 0.7.32 → 0.7.33

package/dist/cli.js

@@ -181037,7 +181037,7 @@ var init_metadata = __esm(() => {
       isClaudeAiAuth: isClaudeAISubscriber(),
       version: "0.7.15",
       versionBase: getVersionBase(),
-      buildTime: "1777195093",
+      buildTime: "1777195198",
       deploymentEnvironment: env4.detectDeploymentEnvironment(),
       ...isEnvTruthy(process.env.GITHUB_ACTIONS) && {
         githubEventName: process.env.GITHUB_EVENT_NAME,
@@ -419007,7 +419007,7 @@ function getAnthropicEnvMetadata() {
 function getBuildAgeMinutes() {
   if (false)
     ;
-  const buildTime = new Date("1777195093").getTime();
+  const buildTime = new Date("1777195198").getTime();
   if (isNaN(buildTime))
     return;
   return Math.floor((Date.now() - buildTime) / 60000);
@@ -512049,7 +512049,7 @@ var init_bridge_kick = __esm(() => {
 var call56 = async () => {
   return {
     type: "text",
-    value: `${"0.7.15"} (built ${"1777195093"})`
+    value: `${"0.7.15"} (built ${"1777195198"})`
   };
 }, version6, version_default;
 var init_version = __esm(() => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ainative/cody-cli",
-  "version": "0.7.32",
+  "version": "0.7.33",
   "type": "module",
   "description": "Cody CLI - AINative Studio's AI-powered coding assistant. Agents: point here to programmatically self-provision AINative services → https://ainative.studio/agent.md",
   "main": "dist/cli.js",
@@ -10,9 +10,16 @@
   "files": [
     "bin/",
     "dist/",
-    ".ainative/",
-    ".claude/",
-    ".cody/",
+    ".ainative/skills/",
+    ".ainative/AINATIVE.md",
+    ".ainative/README.md",
+    ".ainative/SDK_PUBLISHING_GUIDELINES.md",
+    ".claude/hooks/",
+    ".claude/skills/",
+    ".cody/hooks/",
+    ".cody/skills/",
+    ".cody/CODY.md",
+    ".cody/mcp.json.example",
     "cody",
     "README.md"
   ],

package/.ainative/CRITICAL_FILE_PLACEMENT_RULES.md

@@ -1,139 +0,0 @@
-# CRITICAL FILE PLACEMENT RULES
-
-## ABSOLUTE PROHIBITIONS - ZERO TOLERANCE
-
-### **YOU MUST READ THIS BEFORE CREATING ANY FILE**
-
----
-
-## RULE #1: NEVER CREATE .MD FILES IN ROOT DIRECTORIES
-
-### **COMPLETELY FORBIDDEN LOCATIONS:**
-
-```
-<project-root>/*.md  (except README.md)
-<project-root>/src/backend/*.md
-```
-
-### **REQUIRED LOCATIONS:**
-
-**ALL backend documentation MUST go in:**
-```
-<project-root>/docs/{category}/filename.md
-```
-
-**ALL frontend documentation MUST go in:**
-```
-<project-root>/frontend/docs/{category}/filename.md
-```
-
----
-
-## RULE #2: NEVER CREATE .SH SCRIPTS IN BACKEND
-
-### **COMPLETELY FORBIDDEN:**
-```
-<project-root>/src/backend/*.sh (except start.sh)
-```
-
-### **REQUIRED LOCATION:**
-```
-<project-root>/scripts/script_name.sh
-```
-
----
-
-## RULE #3: ALWAYS USE CORRECT BASE URL FORMAT
-
-### **INCORRECT BASE URL PATTERNS:**
-
-```bash
-# WRONG: Including /api/v1 in the base URL variable
-BASE_URL="https://your-api.example.com/api/v1"
-```
-
-### **CORRECT BASE URL PATTERN:**
-
-```bash
-# CORRECT: Base URL is domain only
-BASE_URL="https://your-api.example.com"
-
-# Then use with FULL API paths:
-curl "$BASE_URL/api/v1/projects/"  # Explicit and clear
-curl "$BASE_URL/health"            # Root-level endpoints also clear
-```
-
-### **WHY THIS MATTERS:**
-
-1. **Clarity**: Full paths are immediately visible in code
-2. **Consistency**: Same pattern across all documentation
-3. **Maintainability**: Easy to update if API version changes
-4. **Developer Experience**: No confusion about URL construction
-
----
-
-## MANDATORY CATEGORIZATION GUIDE
-
-### Backend Documentation Categories
-
-| Filename Pattern | Destination | Examples |
-|-----------------|-------------|----------|
-| `ISSUE_*.md`, `BUG_*.md` | `docs/issues/` | ISSUE_24_SUMMARY.md |
-| `*_TEST*.md`, `QA_*.md` | `docs/testing/` | QA_TEST_REPORT.md |
-| `AGENT_SWARM_*.md`, `WORKFLOW_*.md` | `docs/agent-swarm/` | AGENT_SWARM_WORKFLOW.md |
-| `API_*.md`, `*_ENDPOINTS*.md` | `docs/api/` | API_DOCUMENTATION.md |
-| `*_IMPLEMENTATION*.md`, `*_SUMMARY.md` | `docs/reports/` | FEATURE_IMPLEMENTATION_SUMMARY.md |
-| `DEPLOYMENT_*.md`, `RAILWAY_*.md` | `docs/deployment/` | DEPLOYMENT_CHECKLIST.md |
-| `*_QUICK_*.md`, `*_REFERENCE.md` | `docs/quick-reference/` | QUICK_START_GUIDE.md |
-| `CODING_*.md`, `*_GUIDE.md` | `docs/development-guides/` | CODING_STANDARDS.md |
-| `PRD_*.md`, `BACKLOG*.md`, `*_PLAN.md` | `docs/planning/` | PRD_NEW_FEATURE.md |
-
----
-
-## ENFORCEMENT CHECKLIST
-
-### **BEFORE creating ANY .md or .sh file, you MUST:**
-
-1. **CHECK:** Am I creating this file in a root directory?
-2. **STOP:** If yes, determine the correct category
-3. **CREATE:** In the correct `docs/{category}/` or `scripts/` location
-4. **VERIFY:** File is NOT in any root directory
-
----
-
-## YOUR RESPONSIBILITY
-
-As an AI assistant, you MUST:
-
-- **READ these rules** before creating ANY file
-- **FOLLOW the categorization guide** for every .md file
-- **CREATE files in correct locations** from the start
-- **NEVER create files in root** directories
-- **ASK if unsure** about categorization
-
----
-
-## VERIFICATION COMMANDS
-
-### After creating documentation, verify:
-
-```bash
-# Check project root (should only show README.md)
-ls <project-root>/*.md
-
-# Check backend (should show NO .md files)
-ls <project-root>/src/backend/*.md
-
-# Check backend scripts (should only show start.sh)
-ls <project-root>/src/backend/*.sh
-```
-
----
-
-## THIS IS NOT A SUGGESTION - IT IS A REQUIREMENT
-
-**These rules are MANDATORY and NON-NEGOTIABLE.**
-
-**Every violation causes real harm to the project and wastes human time.**
-
-**Follow these rules 100% of the time, no exceptions.**

package/.ainative/git-rules.md

@@ -1,150 +0,0 @@
-# Git Commit Rules
-
-## CRITICAL RULES - ZERO TOLERANCE - NEVER VIOLATE
-
-### 1. NO THIRD-PARTY AI TOOL ATTRIBUTION
-
-**STOP! READ THIS BEFORE EVERY COMMIT!**
-
-You are **STRICTLY FORBIDDEN** from including ANY third-party AI tool references in git commits, pull requests, or GitHub activity.
-
-**ABSOLUTELY FORBIDDEN TEXT - DO NOT USE UNDER ANY CIRCUMSTANCES:**
-- "Claude" or "Anthropic" or "claude.com"
-- "Sourcegraph" (when referring to Sourcegraph Cody the external tool)
-- "ChatGPT" or "OpenAI" (as code author)
-- "Copilot" or "GitHub Copilot" (as attribution)
-- "Generated with [third-party tool]"
-- "Co-Authored-By: Claude/ChatGPT/Copilot"
-- "AI-generated" or "AI-assisted" (without your own branding)
-- Any emoji followed by third-party tool attribution
-
-### 2. COMMIT MESSAGE FORMAT
-
-**CORRECT FORMAT:**
-```
-Add user authentication with JWT
-
-- Implement token generation and validation
-- Add password hashing with bcrypt
-- Create login/logout endpoints
-
-Refs #123
-```
-
-**INCORRECT FORMAT:**
-```
-Add user authentication with JWT
-
-- Changes made
-- More changes
-
-Generated with Claude Code
-Co-Authored-By: Claude <noreply@anthropic.com>
-```
-
-### 3. PULL REQUEST DESCRIPTIONS
-
-**CORRECT FORMAT:**
-```markdown
-## Summary
-- Clear description of changes
-- What was fixed or added
-- Why these changes were made
-
-## Test Plan
-- How to test the changes
-- Expected results
-```
-
-**ABSOLUTELY FORBIDDEN - NEVER USE:**
-```markdown
-## Summary
-Changes made...
-
-Generated with Claude Code
-Co-Authored-By: Claude <noreply@anthropic.com>
-```
-
-### 4. ENFORCEMENT
-
-**These rules apply to:**
-- All commit messages
-- All pull request descriptions
-- All issue comments
-- All GitHub discussions
-- Any public-facing git activity
-
-**Violating these rules will:**
-- Create public attribution that must be avoided
-- Associate our work with third-party tools
-- Compromise the professional appearance of our repositories
-
-### 5. EXAMPLES
-
-#### GOOD COMMIT:
-```
-Add multi-dimension vector support
-
-- Support for 384, 768, 1024, and 1536 dimensions
-- Update validation logic for new dimensions
-- Add comprehensive test coverage
-```
-
-#### BAD COMMIT:
-```
-Add multi-dimension vector support
-
-- Support for 384, 768, 1024, and 1536 dimensions
-
-Generated with Cody AI
-https://sourcegraph.com/cody
-
-Co-Authored-By: Cody <noreply@sourcegraph.com>
-```
-
----
-
-## FINAL WARNING - READ BEFORE EVERY COMMIT
-
-**BEFORE YOU COMMIT, ASK YOURSELF:**
-1. Does my commit contain "Claude", "Anthropic", "ChatGPT", "Copilot" or other third-party AI tools?
-2. Does my commit have "Co-Authored-By: Claude/ChatGPT/Copilot"?
-3. Does my commit have "Generated with [third-party tool]"?
-
-**IF YES TO ANY:** STOP! DO NOT COMMIT! REMOVE THIRD-PARTY ATTRIBUTION IMMEDIATELY!
-
----
-
-## AUTOMATED ENFORCEMENT
-
-**Pre-commit hook:** Create `.git/hooks/commit-msg` to automatically block third-party AI tool attribution:
-
-```bash
-#!/bin/bash
-COMMIT_MSG_FILE=$1
-
-# Block third-party AI tool attribution
-if grep -qiE "(claude|anthropic|chatgpt|openai.*generated|copilot.*generated|co-authored-by:.*claude|co-authored-by:.*chatgpt|co-authored-by:.*copilot|generated with claude|generated with chatgpt)" "$COMMIT_MSG_FILE"; then
-    echo "ERROR: Commit message contains FORBIDDEN third-party AI attribution!"
-    echo ""
-    echo "FORBIDDEN: Claude, Anthropic, ChatGPT, Copilot attribution"
-    echo ""
-    exit 1
-fi
-```
-
-**This hook will REJECT any commit containing third-party AI tool attribution.**
-
----
-
-## ZERO TOLERANCE POLICY
-
-Every commit **MUST** be checked before pushing to ensure:
-- **NO** "Claude" or "Anthropic" references
-- **NO** "ChatGPT" or "OpenAI" attribution
-- **NO** "Copilot" or "GitHub Copilot" attribution
-- **NO** third-party AI tool references
-- **NO** "Co-Authored-By: Claude/ChatGPT/Copilot"
-- **NO** "Generated with [third-party tool]"
-
-**Violating this rule requires immediate commit amendment and force push to remove third-party attribution from git history.**

package/.ainative/settings.json

@@ -1,132 +0,0 @@
-{
-  "$schema": "https://google-gemini.github.io/gemini-cli/schemas/settings.schema.json",
-  "version": "1.0.0",
-  "project": {
-    "name": "Cody CLI",
-    "type": "cli-application",
-    "framework": "bun-typescript-ink",
-    "language": "typescript"
-  },
-  "paths": {
-    "root": "/Users/aideveloper/Desktop/cody-cli",
-    "include_directories": [
-      "src",
-      "tests",
-      "bin",
-      "docs",
-      "packages",
-      "homebrew"
-    ],
-    "exclude_patterns": [
-      "node_modules",
-      "dist",
-      "*.test.ts",
-      "*.test.tsx",
-      "bun.lock",
-      "cody-bin"
-    ]
-  },
-  "context": {
-    "primary_context_file": ".ainative/AINATIVE.md",
-    "supplementary_files": [
-      "CLAUDE.md",
-      "docs/ARCHITECTURE.md",
-      "docs/DEVELOPMENT.md"
-    ],
-    "max_context_files": 10
-  },
-  "model": {
-    "default": "gemini-2.5-pro",
-    "context_window": "1M",
-    "temperature": 0.7,
-    "tool_output_summarization": true
-  },
-  "tools": {
-    "enabled": [
-      "file_read",
-      "file_write",
-      "shell",
-      "web_fetch",
-      "memory"
-    ],
-    "shell": {
-      "allowed_commands": [
-        "bun",
-        "npm",
-        "git",
-        "node",
-        "npx",
-        "curl",
-        "gh",
-        "tree",
-        "chmod",
-        "mkdir",
-        "cp",
-        "mv",
-        "bash"
-      ],
-      "working_directory": "/Users/aideveloper/Desktop/cody-cli"
-    }
-  },
-  "security": {
-    "trusted_folders": [
-      "/Users/aideveloper/Desktop/cody-cli"
-    ],
-    "sandbox_profile": "default"
-  },
-  "ui": {
-    "theme": "dark",
-    "show_citations": true,
-    "show_line_numbers": true
-  },
-  "privacy": {
-    "collect_usage_stats": false
-  },
-  "extensions": {
-    "mcp_servers": {
-      "zerodb": {
-        "type": "http",
-        "url": "https://api.ainative.studio/v1/mcp/zerodb-mcp/messages"
-      }
-    }
-  },
-  "ai_coding_rules": {
-    "git_attribution": {
-      "rule": "ZERO_TOLERANCE",
-      "description": "NEVER include AI tool attribution in commits, PRs, or issues",
-      "forbidden_terms": [
-        "Claude",
-        "Anthropic",
-        "Generated with Claude",
-        "Co-Authored-By: Claude",
-        "AI-generated",
-        "ChatGPT",
-        "Copilot",
-        "OpenAI"
-      ]
-    },
-    "commit_style": {
-      "format": "conventional",
-      "examples": [
-        "feat: Add user authentication",
-        "fix: Resolve navigation bug",
-        "docs: Update API documentation",
-        "refactor: Simplify pricing logic",
-        "test: Add unit tests for services",
-        "chore: Update dependencies"
-      ]
-    },
-    "code_quality": {
-      "linting": "required",
-      "type_checking": "required",
-      "testing": "required_for_features",
-      "min_coverage": 80
-    }
-  },
-  "development": {
-    "build_command": "bun run build",
-    "test_command": "bun test --coverage",
-    "start_command": "bun run start",
-    "source_maps": true
-  }
-}

package/.claude/RAILWAY_DEPLOYMENT_GUIDE.md

@@ -1,118 +0,0 @@
-# Railway Deployment Guide
-
-## Service Architecture
-
-Production environments can use a multi-service architecture on Railway:
-
-### Key Services
-
-1. **API Gateway** (e.g., Kong) - Routes requests to backend services
-2. **Backend** - Main application service (handles auth, users, billing, etc.)
-3. **CMS** - Content management (e.g., Strapi)
-4. **Database** - PostgreSQL database
-
-### Critical: Deploy to the Correct Service
-
-**ALWAYS deploy backend code to the correct backend service, NOT the gateway!**
-
-## Deployment Commands
-
-### 1. List All Services
-```bash
-railway status --json | jq -r '.services.edges[].node.name'
-```
-
-### 2. Deploy to Backend Service
-```bash
-# Option 1: Deploy with service flag (RECOMMENDED)
-railway up --detach --service "your-backend-service"
-
-# Option 2: Link to service first, then deploy
-railway link --service "your-backend-service"
-railway up --detach
-```
-
-### 3. Check Deployment Status
-```bash
-railway status --json | jq -r '.services.edges[] | select(.node.name == "your-service") | .node.serviceInstances.edges[0].node.latestDeployment'
-```
-
-## Common Mistakes to Avoid
-
-- **DON'T:** Deploy without specifying service (deploys to wrong service)
-- **DO:** Always specify the service explicitly
-- **DON'T:** Assume `railway up` knows which service based on the code
-- **DO:** Use Railway docs to understand service structure first
-
-## GitHub CI/CD Integration
-
-Railway can auto-deploy from GitHub when CI passes. If CI fails:
-
-### Option 1: Fix CI and Let Auto-Deploy Work
-```bash
-# Fix failing tests, commit fixes, push to main
-# Railway auto-deploys when CI passes
-```
-
-### Option 2: Force Deploy (Bypass CI)
-```bash
-# Use when change is critical and safe despite CI failures
-railway up --detach --service your-backend-service
-```
-
-## Verifying Deployment
-
-### 1. Check Health Endpoint
-```bash
-curl https://your-domain.com/health | jq
-```
-
-### 2. Check Railway Dashboard
-- Build logs: https://railway.com/project/{project-id}/service/{service-id}
-- Deployment status
-- Error logs if deployment failed
-
-## Database Connection Issues
-
-If you see "Database connection failed" after deployment:
-
-1. **Wait 2-3 minutes** - Service might still be starting
-2. **Check Railway logs** - Look for connection errors
-3. **Verify environment variables** - DATABASE_URL must be set correctly
-4. **Check database service status** - Ensure PostgreSQL is running
-
-## Troubleshooting
-
-### Issue: "Service not found"
-**Solution:** List services first, use exact service name
-```bash
-railway status --json | jq -r '.services.edges[].node.name'
-railway up --service your-service  # Use exact name from list
-```
-
-### Issue: "Multiple services found"
-**Solution:** Always use `--service` flag explicitly
-
-### Issue: Deployment succeeds but changes don't appear
-**Possible causes:**
-1. Deployed to wrong service (check service name)
-2. Code not committed to git (Railway deploys from git, not local files)
-3. Deployment still in progress (wait longer)
-4. Cache issue (try hard refresh or new incognito window)
-
-## Best Practices
-
-1. **Always verify service name before deploying**
-2. **Use explicit service flags**
-3. **Check deployment status after deploying**
-4. **Use Railway dashboard for detailed logs**
-
-## Quick Reference
-
-```bash
-# Deploy backend code
-railway up --detach --service "your-backend-service"
-
-# Check all services and their status
-railway status --json | jq -r '.services.edges[].node | {name, latestDeployment: .serviceInstances.edges[0].node.latestDeployment.status}'
-```

package/.claude/mcp.json.example

@@ -1,31 +0,0 @@
-{
-  "mcpServers": {
-    "github": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "@modelcontextprotocol/server-github"
-      ],
-      "env": {
-        "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}"
-      }
-    },
-    "sequential-thinking": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "@modelcontextprotocol/server-sequential-thinking"
-      ]
-    },
-    "filesystem": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "@modelcontextprotocol/server-filesystem"
-      ],
-      "args": [
-        "/path/to/your/project"
-      ]
-    }
-  }
-}

package/.claude/projects/-Users-aideveloper-Desktop-cody-cli/memory/MEMORY.md

@@ -1,4 +0,0 @@
-- [Cody CLI Project Status](project_cody_cli.md) — v0.7.1, chat completions API confirmed working, SDK operational
-- [Zero Tolerance AI Attribution](feedback_git_attribution.md) — NEVER include AI tool attribution in commits/PRs/issues
-- [Testing Standards](feedback_testing_standards.md) — 80% min coverage, BDD-style bun:test, must run before commits
-- [ZeroDB Project ID](reference_zerodb.md) — Project ID 29e8754c for Cody CLI memory/vectors

package/.claude/projects/-Users-aideveloper-Desktop-cody-cli/memory/feedback_git_attribution.md

@@ -1,11 +0,0 @@
----
-name: Zero Tolerance AI Attribution
-description: NEVER include AI tool attribution in commits, PRs, issues — enforced by pre-commit hooks
-type: feedback
----
-
-Never include "Claude", "Anthropic", "ChatGPT", "Copilot", "Co-Authored-By" referencing AI tools, or "Generated with [tool]" in any git commits, PRs, issues, or code comments.
-
-**Why:** The project has a ZERO TOLERANCE policy to maintain professional appearance and avoid third-party tool association. Pre-commit hooks enforce this automatically.
-
-**How to apply:** Write clean conventional commit messages. Describe what and why. No tool branding. This overrides Claude Code's default Co-Authored-By behavior.

package/.claude/projects/-Users-aideveloper-Desktop-cody-cli/memory/feedback_testing_standards.md

@@ -1,11 +0,0 @@
----
-name: Testing Standards — 80% Min Coverage
-description: Mandatory TDD with BDD-style tests, 80% minimum coverage, tests must actually run with proof before commits
-type: feedback
----
-
-All new code requires tests with minimum 80% coverage. Tests use bun:test with BDD-style describe/it syntax. Tests MUST actually be executed with proof of passing before any commit or PR.
-
-**Why:** Project enforces mandatory TDD to prevent false confidence and catch infrastructure issues before merge.
-
-**How to apply:** Run `bun test --coverage` before any commit. Include test execution evidence in PRs. Test files go in `tests/` directory. Use helpers from `tests/setup.ts`.

package/.claude/projects/-Users-aideveloper-Desktop-cody-cli/memory/project_cody_cli.md

@@ -1,11 +0,0 @@
----
-name: Cody CLI Project Status
-description: Cody CLI v0.7.1 — AINative Studio's Claude Code fork, chat completions API confirmed working, SDK operational
-type: project
----
-
-Cody CLI (@ainative/cody-cli) v0.7.1 is AINative Studio's fork/rebrand of Claude Code. The chat completions API was confirmed working on 2026-04-04 before a computer crash.
-
-**Why:** Building an independent AI coding assistant branded to AINative, routing through Kong gateway to multiple LLM providers.
-
-**How to apply:** All work should maintain AINative branding, use api.ainative.studio as base URL, and respect the dual-provider architecture being built (issue #65). The Anthropic adapter bug (#64) is a known issue with Claude models.

package/.claude/projects/-Users-aideveloper-Desktop-cody-cli/memory/reference_zerodb.md

@@ -1,12 +0,0 @@
----
-name: ZeroDB Project ID for Cody CLI
-description: ZeroDB project ID 29e8754c-c67d-4a74-9167-a069d87ab1aa for Cody CLI session memory and vector storage
-type: reference
----
-
-ZeroDB project for Cody CLI:
-- **Project ID**: `29e8754c-c67d-4a74-9167-a069d87ab1aa`
-- **Project Name**: "Cody CLI"
-- **MCP endpoint**: `https://api.ainative.studio/v1/mcp/zerodb-mcp/messages`
-- **Stored in**: `.env` as `ZERODB_PROJECT_ID`
-- **Created**: 2026-04-04

package/.claude/settings.json

@@ -1,30 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "Bash(curl:*)",
-      "Bash(git:*)",
-      "Bash(ls:*)",
-      "Bash(cat:*)",
-      "Bash(find:*)",
-      "Bash(npm:*)",
-      "Bash(npx:*)",
-      "Bash(bun:*)",
-      "Bash(node:*)",
-      "Bash(python:*)",
-      "Bash(python3:*)",
-      "Bash(gh:*)",
-      "Bash(tree:*)",
-      "Bash(chmod:*)",
-      "Bash(mkdir:*)",
-      "Bash(cp:*)",
-      "Bash(mv:*)",
-      "Bash(bash:*)",
-      "Bash(rm:*)",
-      "Bash(touch:*)",
-      "Bash(head:*)",
-      "Bash(tail:*)",
-      "Bash(wc:*)"
-    ],
-    "deny": []
-  }
-}

package/.claude/settings.local.json

@@ -1,6 +0,0 @@
-{
-  "enabledMcpjsonServers": [
-    "zerodb"
-  ],
-  "enableAllProjectMcpServers": true
-}

package/.cody/mcp.json

@@ -1,12 +0,0 @@
-{
-  "mcpServers": {
-    "zerodb-memory": {
-      "type": "http",
-      "url": "https://api.ainative.studio/v1/mcp/zerodb-memory-mcp/messages",
-      "headers": {
-        "x-api-key": "sk_nLI6DrYP9h7qrac9t876Wj4e3iV-zsk5YXUv0S-ttkM"
-      },
-      "description": "ZeroDB agent memory - store, search, and manage conversation context"
-    }
-  }
-}