drivecore · Mar 21, 2025 · Mar 22, 2025 · Mar 22, 2025 · Mar 22, 2025 · Mar 22, 2025
diff --git a/.github/workflows/deploy-docs.yml b/.github/workflows/deploy-docs.yml
@@ -1,4 +1,4 @@
-name: Deploy Documentation to Cloud Run
+name: Deploy Docs
 
 on:
   push:

diff --git a/.github/workflows/release.yml → .github/workflows/deploy-npm.yml b/.github/workflows/release.yml → .github/workflows/deploy-npm.yml
@@ -1,4 +1,4 @@
-name: Release
+name: Deploy NPM
 
 on:
   push:

diff --git a/.github/workflows/issue-comment.yml → .github/workflows/mycoder-comment.yml b/.github/workflows/issue-comment.yml → .github/workflows/mycoder-comment.yml
@@ -1,4 +1,4 @@
-name: MyCoder Issue Comment Action
+name: MyCoder Comment Action
 
 # This workflow is triggered on all issue comments, but only runs the job
 # if the comment contains '/mycoder' and is from the authorized user.
@@ -46,4 +46,4 @@ jobs:
       - run: |
           echo "${{ secrets.GH_PAT }}" | gh auth login --with-token
           gh auth status
-      - run: mycoder --upgradeCheck false --githubMode true --userPrompt false "On issue #${{ github.event.issue.number }} in comment ${{ steps.extract-prompt.outputs.comment_url }} the user invoked the mycoder CLI via /mycoder.  Can you try to do what they requested or if it is unclear, respond with a comment to that affect to encourage them to be more clear."
+      - run: mycoder --upgradeCheck false --githubMode true --userPrompt false "On issue ${{ github.event.issue.number }} in comment ${{ steps.extract-prompt.outputs.comment_url }} the user invoked the mycoder CLI via /mycoder.  Can you try to do what they requested or if it is unclear, respond with a comment to that affect to encourage them to be more clear."
diff --git a/.github/workflows/mycoder-issue-triage.yml b/.github/workflows/mycoder-issue-triage.yml
@@ -0,0 +1,39 @@
+name: MyCoder Issue Triage
+
+# This workflow is triggered when new issues are created
+on:
+  issues:
+    types: [opened]
+
+# Top-level permissions apply to all jobs
+permissions:
+  contents: read # Required for checkout
+  issues: write # Required for issue comments and labels
+  pull-requests: read # For context if needed
+  discussions: read # Added for more context if needed
+
+env:
+  ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+
+jobs:
+  triage-issue:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version-file: .nvmrc
+      - uses: pnpm/action-setup@v4
+        with:
+          version: ${{ vars.PNPM_VERSION }}
+      - run: pnpm install
+      - run: cd packages/agent && pnpm exec playwright install --with-deps chromium
+      - run: |
+          git config --global user.name "Ben Houston (via MyCoder)"
+          git config --global user.email "neuralsoft@gmail.com"
+      - run: pnpm install -g mycoder
+      - run: |
+          echo "${{ secrets.GH_PAT }}" | gh auth login --with-token
+          gh auth status
+      - run: |
+          mycoder --upgradeCheck false --githubMode true --userPrompt false "You are an issue triage assistant. Please analyze GitHub issue ${{ github.event.issue.number }} according to the guidelines in .mycoder/ISSUE_TRIAGE.md"
diff --git a/.github/workflows/mycoder-pr-review.yml b/.github/workflows/mycoder-pr-review.yml
@@ -0,0 +1,49 @@
+name: MyCoder PR Review
+
+# This workflow is triggered when a PR is opened or updated with new commits
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+# Top-level permissions apply to all jobs
+permissions:
+  contents: read # Required for checkout
+  issues: read # Required for reading linked issues
+  pull-requests: write # Required for commenting on PRs
+  discussions: read # For reading discussions
+  statuses: write # For creating commit statuses
+  checks: write # For creating check runs
+  actions: read # For inspecting workflow runs
+
+env:
+  ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+
+jobs:
+  review-pr:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version-file: .nvmrc
+      - uses: pnpm/action-setup@v4
+        with:
+          version: ${{ vars.PNPM_VERSION }}
+      - run: pnpm install
+      - run: cd packages/agent && pnpm exec playwright install --with-deps chromium
+      - run: |
+          git config --global user.name "Ben Houston (via MyCoder)"
+          git config --global user.email "neuralsoft@gmail.com"
+      - run: pnpm install -g mycoder
+      - run: |
+          echo "${{ secrets.GH_PAT }}" | gh auth login --with-token
+          gh auth status
+      - name: Get previous reviews
+        id: get-reviews
+        run: |
+          PR_REVIEWS=$(gh pr view ${{ github.event.pull_request.number }} --json reviews --jq '.reviews')
+          PR_COMMENTS=$(gh pr view ${{ github.event.pull_request.number }} --json comments --jq '.comments')
+          echo "reviews=$PR_REVIEWS" >> $GITHUB_OUTPUT
+          echo "comments=$PR_COMMENTS" >> $GITHUB_OUTPUT
+      - run: |
+          mycoder --upgradeCheck false --githubMode true --userPrompt false "Please review PR ${{ github.event.pull_request.number }} according to the guidelines in .mycoder/PR_REVIEW.md. Previous reviews and comments: ${{ steps.get-reviews.outputs.reviews }} ${{ steps.get-reviews.outputs.comments }}"
diff --git a/.mycoder/ISSUE_TRIAGE.md b/.mycoder/ISSUE_TRIAGE.md
@@ -0,0 +1,93 @@
+# Issue Triage Guidelines
+
+## Issue Classification
+
+When triaging a new issue, categorize it by type and apply appropriate labels:
+
+### Issue Types
+
+- **Bug**: An error, flaw, or unexpected behavior in the code
+- **Feature**: A request for new functionality or capability
+- **Request**: A general request that doesn't fit into bug or feature categories
+
+### Issue Labels
+
+- **bug**: For issues reporting bugs or unexpected behavior
+- **documentation**: For issues related to documentation improvements
+- **question**: For issues asking questions about usage or implementation
+- **duplicate**: For issues that have been reported before (link to the original issue)
+- **enhancement**: For feature requests or improvement suggestions
+- **help wanted**: For issues that need additional community input or assistance
+
+## Triage Process
+
+### Step 1: Initial Assessment
+
+1. Read the issue description thoroughly
+2. Determine if the issue provides sufficient information
+   - If too vague, ask for more details (reproduction steps, expected vs. actual behavior)
+   - Check for screenshots, error messages, or logs if applicable
+
+### Step 2: Categorization
+
+1. Assign the appropriate issue type (Bug, Feature, Request)
+2. Apply relevant labels based on the issue content
+
+### Step 3: Duplication Check
+
+1. Search for similar existing issues
+2. If a duplicate is found:
+   - Apply the "duplicate" label
+   - Comment with a link to the original issue
+   - Suggest closing the duplicate issue
+
+### Step 4: Issue Investigation
+
+#### For Bug Reports:
+
+1. Attempt to reproduce the issue if possible
+2. Investigate the codebase to identify potential causes
+3. Provide initial feedback on:
+   - Potential root causes
+   - Affected components
+   - Possible solutions or workarounds
+   - Estimation of complexity
+
+#### For Feature Requests:
+
+1. Evaluate if the request aligns with the project's goals
+2. Investigate feasibility and implementation approaches
+3. Provide feedback on:
+   - Implementation possibilities
+   - Potential challenges
+   - Similar existing functionality
+   - Estimation of work required
+
+#### For Questions:
+
+1. Research the code and documentation to find answers
+2. Provide clear and helpful responses
+3. Suggest documentation improvements if the question reveals gaps
+
+### Step 5: Follow-up
+
+1. Provide a constructive and helpful comment
+2. Ask clarifying questions if needed
+3. Suggest next steps or potential contributors
+4. Set appropriate expectations for resolution timeframes
+
+## Communication Guidelines
+
+- Be respectful and constructive in all communications
+- Acknowledge the issue reporter's contribution
+- Use clear and specific language
+- Provide context for technical suggestions
+- Link to relevant documentation when applicable
+- Encourage community participation when appropriate
+
+## Special Considerations
+
+- For security vulnerabilities, suggest proper disclosure channels
+- For major feature requests, suggest discussion in appropriate forums first
+- For issues affecting performance, request benchmark data if not provided
+- For platform-specific issues, request environment details
diff --git a/.mycoder/PR_REVIEW.md b/.mycoder/PR_REVIEW.md
@@ -0,0 +1,73 @@
+# MyCoder PR Review Guidelines
+
+This document outlines the criteria and guidelines that MyCoder uses when reviewing pull requests. These guidelines help ensure that contributions maintain high quality and consistency with the project's standards.
+
+## Issue Alignment
+
+- Does the PR directly address the requirements specified in the linked issue?
+- Are all the requirements from the original issue satisfied?
+- Does the PR consider points raised in the issue discussion?
+- Is there any scope creep (changes not related to the original issue)?
+
+## Code Quality
+
+- **Clean Design**: Is the code design clear and not overly complex?
+- **Terseness**: Is the code concise without sacrificing readability?
+- **Duplication**: Does the code avoid duplication? Are there opportunities to reuse existing code?
+- **Consistency**: Does the code follow the same patterns and organization as the rest of the project?
+- **Naming**: Are variables, functions, and classes named clearly and consistently?
+- **Comments**: Are complex sections adequately commented? Are there unnecessary comments?
+
+## Function and Component Design
+
+- **Single Responsibility**: Does each function or component have a clear, single purpose?
+- **Parameter Count**: Do functions have a reasonable number of parameters?
+- **Return Values**: Are return values consistent and well-documented?
+- **Error Handling**: Is error handling comprehensive and consistent?
+- **Side Effects**: Are side effects minimized and documented where necessary?
+
+## Testing
+
+- Are there appropriate tests for new functionality?
+- Do the tests cover edge cases and potential failure scenarios?
+- Are the tests readable and maintainable?
+
+## Documentation
+
+- Is new functionality properly documented?
+- Are changes to existing APIs documented?
+- Are README or other documentation files updated if necessary?
+
+## Performance Considerations
+
+- Are there any potential performance issues?
+- For computationally intensive operations, have alternatives been considered?
+
+## Security Considerations
+
+- Does the code introduce any security vulnerabilities?
+- Is user input properly validated and sanitized?
+- Are credentials and sensitive data handled securely?
+
+## Accessibility
+
+- Do UI changes maintain or improve accessibility?
+- Are there appropriate ARIA attributes where needed?
+
+## Browser/Environment Compatibility
+
+- Will the changes work across all supported browsers/environments?
+- Are there any platform-specific considerations that need addressing?
+
+## Follow-up Review Guidelines
+
+When reviewing updates to a PR:
+
+- Focus on whether previous feedback has been addressed
+- Acknowledge improvements and progress
+- Provide constructive guidance for any remaining issues
+- Be encouraging and solution-oriented
+- Avoid repeating previous feedback unless clarification is needed
+- Help move the PR towards completion rather than finding new issues
+
+Remember that the goal is to help improve the code while maintaining a positive and constructive environment for all contributors.
diff --git a/.vscode/settings.json b/.vscode/settings.json
@@ -44,6 +44,7 @@
     "threeify",
     "transpiling",
     "triggerdef",
+    "uuidv",
     "vinxi"
   ],
 

diff --git a/README.md b/README.md
@@ -44,9 +44,6 @@ mycoder --userPrompt false "Generate a basic Express.js server"
 
 # Disable user consent warning and version upgrade check for automated environments
 mycoder --upgradeCheck false "Generate a basic Express.js server"
-
-# Enable GitHub mode via CLI option (overrides config file)
-mycoder --githubMode true "Work with GitHub issues and PRs"
 ```
 
 ## Configuration
@@ -80,7 +77,6 @@ export default {
   // Browser settings
   headless: true,
   userSession: false,
-  pageFilter: 'none', // 'simple', 'none', or 'readability'
 
   // System browser detection settings
   browser: {
@@ -110,7 +106,6 @@ export default {
   //   'Custom instruction line 3',
   // ],
   profile: false,
-  tokenCache: true,
 
   // Base URL configuration (for providers that need it)
   baseUrl: 'http://localhost:11434', // Example for Ollama

diff --git a/docs/features/message-compaction.md b/docs/features/message-compaction.md
@@ -7,6 +7,7 @@ When agents run for extended periods, they accumulate a large history of message
 ### 1. Token Usage Tracking
 
 The LLM abstraction now tracks and returns:
+
 - Total tokens used in the current completion request
 - Maximum allowed tokens for the model/provider
 
@@ -15,17 +16,20 @@ This information is used to monitor context window usage and trigger appropriate
 ### 2. Status Updates
 
 Agents receive status updates with information about:
+
 - Current token usage and percentage of the maximum
 - Cost so far
 - Active sub-agents and their status
 - Active shell processes and their status
 - Active browser sessions and their status
 
 Status updates are sent:
+
 1. Every 5 agent interactions (periodic updates)
 2. Whenever token usage exceeds 50% of the maximum (threshold-based updates)
 
 Example status update:
+
 ```
 --- STATUS UPDATE ---
 Token Usage: 45,235/100,000 (45%)
@@ -72,6 +76,7 @@ Agents are instructed to monitor their token usage through status updates and us
 ## Configuration
 
 The message compaction feature is enabled by default with reasonable defaults:
+
 - Status updates every 5 agent interactions
 - Recommendation to compact at 70% token usage
 - Default preservation of 10 recent messages when compacting
@@ -81,17 +86,20 @@ The message compaction feature is enabled by default with reasonable defaults:
 The system includes token limits for various models:
 
 ### Anthropic Models
+
 - claude-3-opus-20240229: 200,000 tokens
 - claude-3-sonnet-20240229: 200,000 tokens
 - claude-3-haiku-20240307: 200,000 tokens
 - claude-2.1: 100,000 tokens
 
 ### OpenAI Models
+
 - gpt-4o: 128,000 tokens
 - gpt-4-turbo: 128,000 tokens
 - gpt-3.5-turbo: 16,385 tokens
 
 ### Ollama Models
+
 - llama2: 4,096 tokens
 - mistral: 8,192 tokens
 - mixtral: 32,768 tokens
@@ -102,4 +110,4 @@ The system includes token limits for various models:
 - Maintains important context for agent operation
 - Enables longer-running agent sessions
 - Makes the system more robust for complex tasks
-- Gives agents self-awareness of resource usage
+- Gives agents self-awareness of resource usage