cntx-ui 3.0.4 → 3.0.6

package/templates/TOOLS.md

@@ -33,9 +33,3 @@ This document maps the **Model Context Protocol (MCP)** tools to their **HTTP AP
 | `read_file` | `GET /api/files/:path` | `path: string` | Read file with injected semantic metadata. |
 | `write_file` | `POST /api/files` | `path, content` | Write file with automatic backup. |
 
-## Activities
-
-| MCP Tool | HTTP Endpoint | Parameters | Description |
-| :--- | :--- | :--- | :--- |
-| `list_activities` | `GET /api/activities` | *None* | List all ongoing agent missions. |
-| `get_reasoning` | `GET /api/activities/:id/reasoning` | `id: string` | Recall agent interaction history for a task. |

package/templates/agent-config.yaml

@@ -23,11 +23,6 @@ capabilities:
     required: true
     endpoint_check: "/api/bundles"
     
-  activities_system:
-    file: "capabilities/activities-system.md"
-    required: false
-    endpoint_check: "/api/activities"
-
 # Project-specific context
 project_context:
   - "project-specific/architecture.md"

package/templates/agent-instructions.md

@@ -9,18 +9,9 @@ This repository has been analyzed by cntx-ui and is ready for intelligent agent
 If you're an agent without MCP server access, use this prompt to get up to speed:
 
 ```
-I'm working in a project that uses cntx-ui for file organization and AI collaboration. Please read these files to understand the project structure and help me with activities:
+I'm working in a project that uses cntx-ui for file organization and AI collaboration. Please read this file to understand the project structure:
 
 @.cntx/agent-instructions.md
-@.cntx/activities/README.md
-@.cntx/activities/activities.json
-
-After reading those, please also examine:
-@.cntx/activities/lib/create-activity.mdc
-@.cntx/activities/lib/generate-tasks.mdc
-@.cntx/activities/lib/process-task-list.mdc
-
-These files contain the complete workflow for creating and managing activities with agent assistance.
 ```
 
 ## Your Role
@@ -98,7 +89,6 @@ _"Help me set up this project" or "Optimize my bundle organization"_
 - **Fresh Projects**: Detect project state → Generate semantic analysis → Plan bundles → Create bundles
 - **Established Projects**: Audit organization → Optimize bundles → Suggest improvements
 - **Maintenance**: Cleanup stale patterns → Validate health → Recommend optimizations
-- **Activities**: detect, analyze, bundle (plan), create (execute), optimize, audit, cleanup, validate
 
 ## Response Guidelines
 
@@ -144,10 +134,7 @@ Would you like me to [specific follow-up options]?
 2. **Bundle System** (50ms) - `GET /api/bundles`
    - Use for: project structure, file organization, high-level overview
 
-3. **Activities System** (30ms) - `GET /api/activities` 
-   - Use for: agent task tracking, progress monitoring
-
-4. **Traditional Search** (100ms+, high token cost) - `grep/rg/Read`
+3. **Traditional Search** (100ms+, high token cost) - `grep/rg/Read`
    - Use ONLY when: exact string matching needed, vector search fails
    - Examples: specific error messages, exact function names
 

package/templates/agent-rules/project-specific/architecture.md

@@ -59,7 +59,6 @@ cntx-ui/
 │   ├── src/lib/                  # Client-side utilities
 │   └── dist/                     # Built static assets
 ├── .cntx/                        # Configuration and cache
-│   ├── activities/               # Agent task definitions
 │   ├── agent-rules/              # Modular agent instructions
 │   ├── bundle-states.json       # Bundle configuration and metadata
 │   └── semantic-cache.json      # Analysis cache

package/templates/hidden-files.json

@@ -5,7 +5,6 @@
     "server": [],
     "frontend": [],
     "config": [],
-    "activities": [],
     "tests": [],
     "docs": []
   },