@yylo/cli 0.2.1-rc.14

Automated @yylo/cli 0.2.1-rc.14 release.

Attached assets are the exact registry-published artifacts.

@yylo/cli 0.2.1-rc.13

Automated @yylo/cli 0.2.1-rc.13 release.

Attached assets are the exact registry-published artifacts.

@yylo/cli 0.2.1-rc.12

Automated @yylo/cli 0.2.1-rc.12 release.

Attached assets are the exact registry-published artifacts.

@yylo/cli 0.2.1-rc.11

Automated @yylo/cli 0.2.1-rc.11 release.

Attached assets are the exact registry-published artifacts.

@yylo/cli 0.2.1-rc.10

Automated @yylo/cli 0.2.1-rc.10 release.

Attached assets are the exact registry-published artifacts.

@yylo/cli 0.2.1-rc.1

Automated release for @yylo/cli 0.2.1-rc.1.

1.0.50 : Pi Agent

Supporting Claude's skill commands in Pi agent.
Now you can use !echo "Hello World" in skills for pi agent, it can use it in the exact same way as Claude Code.

1.0.42

fix: Change default backend from mcp to shell in startup-validation.ts

Fixed startup-validation.ts line 447 where backend default was hardcoded to 'mcp' instead of matching DEFAULT_CONFIG.defaultBackend ('shell'). This was causing the validation output to incorrectly show "Backend: mcp" even when no -b flag was provided.

Changes:
- startup-validation.ts line 447: Changed default from 'mcp' to 'shell' with clarifying comment
- startup-validation.ts lines 448-469: Refactored backend detection logic to use backendSetViaCliArg flag for clearer control flow (replaced hardcoded 'mcp' check with explicit flag)
- startup-validation.test.ts lines 417-424: Updated test to mock process.argv with -b mcp flag since shell backend doesn't require mcp.json

All 17 startup-validation tests now pass. CLI correctly shows "Backend: shell (skipping MCP configuration)" when no -b flag is provided.

Resolves task hQI4WX

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

1.0.40 : github sync, loop until completion and more

fix: Change default backend from mcp to shell in startup-validation.ts

Fixed startup-validation.ts line 447 where backend default was hardcoded to 'mcp' instead of matching DEFAULT_CONFIG.defaultBackend ('shell'). This was causing the validation output to incorrectly show "Backend: mcp" even when no -b flag was provided.

Changes:
- startup-validation.ts line 447: Changed default from 'mcp' to 'shell' with clarifying comment
- startup-validation.ts lines 448-469: Refactored backend detection logic to use backendSetViaCliArg flag for clearer control flow (replaced hardcoded 'mcp' check with explicit flag)
- startup-validation.test.ts lines 417-424: Updated test to mock process.argv with -b mcp flag since shell backend doesn't require mcp.json

All 17 startup-validation tests now pass. CLI correctly shows "Backend: shell (skipping MCP configuration)" when no -b flag is provided.

Resolves task hQI4WX

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

1.0.37

slack integration
and
run_until_completition.sh

more on this: askbudi.ai