Mike Kelly Release Notes

All Mike Kelly Release Notes (9)

• Jan 28, 2026

  • Date parsed from source:
    Jan 28, 2026
  • First seen by Releasebot:
    Feb 23, 2026
  

  claude-sneakpeek by Mike Kelly

  v1.6.10

  1.6.10

  Original source Report a problem
• Jan 23, 2026

  • Date parsed from source:
    Jan 23, 2026
  • First seen by Releasebot:
    Feb 23, 2026
  

  claude-sneakpeek by Mike Kelly

  v1.6.8

  1.6.8

  Original source Report a problem
• All of your release notes in one feed

  Join Releasebot and get updates from Mike Kelly and hundreds of other software products.

  Create account

  Get updates with: RSS Email API CSV MCP Slack n8n Zapier
• Jan 23, 2026

  • Date parsed from source:
    Jan 23, 2026
  • First seen by Releasebot:
    Feb 23, 2026
  

  claude-sneakpeek by Mike Kelly

  v1.6.7

  1.6.7

  Original source Report a problem
• Jan 8, 2026

  • Date parsed from source:
    Jan 8, 2026
  • First seen by Releasebot:
    Feb 23, 2026
  

  claude-sneakpeek by Mike Kelly

  v1.6.1 - Enriched JSON output for orchestration integration

  New json flag enhancements for automation tasks expose computed blockers, readiness, and dependency graphs. See blocked, blockedBy, openBlockers, ready counts, and a structured graph with roots, leaves, and orphans for easier pipeline management.

  --json flag now returns computed fields for automation:

  • blocked: Computed boolean (true if any blocker is open)
  • blockedBy: Enhanced with status of each blocking task
  • openBlockers: Array of IDs of open blockers only
  • summary.ready: Count of open tasks that are not blocked
  • npx cc-mirror tasks --ready shows only ready tasks (open + not blocked)
  • Works with --json for programmatic filtering

  npx cc-mirror tasks graph --json returns structured dependency data:

  • nodes: All tasks with computed fields + depth
  • roots: Tasks with no blockedBy
  • leaves: Tasks with no blocks
  • orphans: Tasks with missing blockedBy references

  Original source Report a problem

  Show more
• Jan 6, 2026

  • Date parsed from source:
    Jan 6, 2026
  • First seen by Releasebot:
    Feb 23, 2026
  

  claude-sneakpeek by Mike Kelly

  v1.5.0

  v1.5.0 - Claude Code, Unshackled

  Original source Report a problem
• Jan 5, 2026

  • Date parsed from source:
    Jan 5, 2026
  • First seen by Releasebot:
    Feb 23, 2026
  

  claude-sneakpeek by Mike Kelly

  v1.4.0

  v1.4.0 - Tasks CLI for team mode management

  Original source Report a problem
• Jan 5, 2026

  • Date parsed from source:
    Jan 5, 2026
  • First seen by Releasebot:
    Feb 23, 2026
  

  claude-sneakpeek by Mike Kelly

  v1.3.0 - Fix cross-project task pollution

  Claude Code fixes a bug where settings.json overwrote dynamic team names; teams now follow folder structure using CLAUDE_CODE_TEAM_MODE. Breaking changes require migrating from TEAM_NAME to TEAM_MODE and renaming old task folders to project-based names.

  Bug Fix

  Claude Code loads settings.json env vars internally, overwriting wrapper's dynamic team name with the static value from settings.json. This caused all projects to share tasks under the same team name

  Solution

  Use CLAUDE_CODE_TEAM_MODE as a flag in settings.json (not TEAM_NAME)
  Wrapper checks TEAM_MODE and sets TEAM_NAME dynamically based on folder
  Claude Code doesn't overwrite because TEAM_NAME isn't in settings.json
  Team names are now purely directory-based:

  • mc from project-a → team: project-a
  • mc from project-b → team: project-b
  • TEAM=workers mc → team: -workers

  Breaking Change

  Existing variants need update to migrate from TEAM_NAME to TEAM_MODE
  Old task folders (e.g., mc-project-a) need manual rename to (project-a)

  Original source Report a problem

  Show more
• Jan 5, 2026

  • Date parsed from source:
    Jan 5, 2026
  • First seen by Releasebot:
    Feb 23, 2026
  

  claude-sneakpeek by Mike Kelly

  v1.2.1 - Fix orchestration skill update for existing team mode variants

  Bug fix

  Bug fix: TeamModeUpdateStep now properly updates the orchestration skill for variants that already have team mode enabled, not just when --enable-team-mode is passed or provider defaults to team mode.

  Original source Report a problem
• Jan 5, 2026

  • Date parsed from source:
    Jan 5, 2026
  • First seen by Releasebot:
    Feb 23, 2026
  

  claude-sneakpeek by Mike Kelly

  v1.2.0 - Dynamic team names and orchestration improvements

  Project folder scoping now auto-sets team names at runtime to fix cross‑project task pollution. Breaking change: existing tasks disappear from views after update as scopes migrate. References and orchestration now load required guides and offer quick index lookups for faster coordination.

  Team names are now automatically scoped by project folder at runtime:

  Command
  Team Name
  mc
  mc-<project-folder>
  TEAM=A mc
  mc-<project-folder>-A
  TEAM=backend mc
  mc-<project-folder>-backend
  

  This fixes the cross-project task pollution bug where tasks from different
  projects would appear in the same task list.

  Breaking change: Existing tasks will no longer appear after update
  (they're still on disk, just scoped to the old team name).

  References moved to top - Domain guides loaded before decomposition

  Read allowed for coordination - Orchestrator can read 1-2 files for:

  • Skill references (MANDATORY)
  • Domain guides
  • Quick index lookups (package.json, AGENTS.md)
  • Agent outputs for synthesis

  Clear delegation rules - 3+ files or comprehensive analysis → spawn agent

  Original source Report a problem

  Show more