Build AI methods with your coding agent, then run them anywhere: as an MCP for chatbots, as a webapp for people, or via API for your software.
fix Init ref reset. Fix name of Pipe sequence result
Louis Choquel6cee6615e224
diff --git a/docs/home/7-configuration/index.md b/docs/home/7-configuration/index.mdindex 706d6ddb6..c33b9cad5 100644--- a/docs/home/7-configuration/index.md+++ b/docs/home/7-configuration/index.md@@ -15,7 +15,7 @@ pipelex init config!!! important "Configuration Setup Notes"1. `pipelex init config` creates a **template** configuration file with sample settings. It does not include all possible configuration options - it's meant as a starting point.- 2. Using `pipelex init config --reset` will **overwrite** your existing `pipelex.toml` file without warning. Make sure to backup your configuration before using this flag.+ 2. Running `pipelex init config` will **overwrite** your existing `pipelex.toml` file without warning. Make sure to backup your configuration before running this command.For a complete list of all possible configuration options, refer to the configuration group documentation below.diff --git a/pipelex/cli/agent_cli/commands/doctor_cmd.py b/pipelex/cli/agent_cli/commands/doctor_cmd.pyindex 2675d6635..5f8c8b39f 100644--- a/pipelex/cli/agent_cli/commands/doctor_cmd.py+++ b/pipelex/cli/agent_cli/commands/doctor_cmd.py@@ -78,7 +78,7 @@ def agent_doctor_cmd(if not config_healthy and config_missing_count > 0:recommended_actions.append("Run 'pipelex init config' to install missing configuration files")if not config_healthy and config_missing_count == 0:- recommended_actions.append("Fix validation errors in .pipelex/pipelex.toml or run 'pipelex init config --reset'")+ recommended_actions.append("Fix validation errors in .pipelex/pipelex.toml or run 'pipelex init config'")if not telemetry_healthy:recommended_actions.append(f"Run 'pipelex init telemetry' to fix telemetry: {telemetry_message}")if not backends_healthy:diff --git a/pipelex/cli/commands/doctor_cmd.py b/pipelex/cli/commands/doctor_cmd.pyindex 859dd420c..0d3b333e9 100644--- a/pipelex/cli/commands/doctor_cmd.py+++ b/pipelex/cli/commands/doctor_cmd.py@@ -121,7 +121,7 @@ def check_telemetry_config(config_dir: str | None = None) -> tuple[bool, str]:# Check if this looks like the old config format (has telemetry_mode at root level)if "custom_posthog" not in toml_doc and ("telemetry_mode" in toml_doc or "project_api_key" in toml_doc):return False, "Config format has changed - run 'pipelex init telemetry' to update"- return False, "Invalid configuration - run 'pipelex init telemetry --reset' to fix"+ return False, "Invalid configuration - run 'pipelex init telemetry' to fix"def check_backend_credentials(config_dir: str | None = None) -> tuple[bool, dict[str, BackendCredentialsReport], str]:@@ -527,18 +527,18 @@ def display_health_report(if has_telemetry_validation_error and "pipelex init telemetry" not in telemetry_message:console.print(" • Fix validation errors in [cyan].pipelex/telemetry.toml[/cyan]")- console.print(" or run [cyan]pipelex init telemetry --reset[/cyan] to regenerate")+ console.print(" or run [cyan]pipelex init telemetry[/cyan] to regenerate")# Backend file issuesif can_auto_fix_backends:if fix_mode:# We're in fix mode, show what's happening next and the alternativeconsole.print(" • Interactive fixes for outdated backend configurations will be offered below")- console.print(" • Alternatively, run [cyan]pipelex init config --reset[/cyan] to reset all configuration files")+ console.print(" • Alternatively, run [cyan]pipelex init config[/cyan] to reset all configuration files")else:# Not in fix mode, suggest running --fixconsole.print(" • Run [cyan]pipelex doctor --fix[/cyan] to replace outdated backend configurations")- console.print(" [dim]or run[/dim] [cyan]pipelex init config --reset[/cyan] [dim]to reset all configuration files[/dim]")+ console.print(" [dim]or run[/dim] [cyan]pipelex init config[/cyan] [dim]to reset all configuration files[/dim]")if has_custom_backend_issues:invalid_custom = [name for name, report in backend_file_reports.items() if not report.is_valid and not report.has_kit_template]@@ -810,7 +810,7 @@ def do_doctor_cmd(console.print(f" {config_message}")console.print()console.print("You can fix this manually by editing [cyan].pipelex/pipelex.toml[/cyan]")- console.print("or run [cyan]pipelex init config --reset[/cyan] to regenerate from template.")+ console.print("or run [cyan]pipelex init config[/cyan] to regenerate from template.")console.print()# Telemetry validation errors (skip if message already contains the fix command)@@ -819,7 +819,7 @@ def do_doctor_cmd(console.print(f" {telemetry_message}")console.print()console.print("You can fix this manually by editing [cyan].pipelex/telemetry.toml[/cyan]")- console.print("or run [cyan]pipelex init telemetry --reset[/cyan] to regenerate from template.")+ console.print("or run [cyan]pipelex init telemetry[/cyan] to regenerate from template.")console.print()# Backend credentialsdiff --git a/pipelex/pipe_controllers/batch/pipe_batch.py b/pipelex/pipe_controllers/batch/pipe_batch.pyindex 3f728a8ce..b9a0c2896 100644--- a/pipelex/pipe_controllers/batch/pipe_batch.py+++ b/pipelex/pipe_controllers/batch/pipe_batch.py@@ -159,7 +159,7 @@ class PipeBatch(PipeController):task = sub_pipe.run_pipe(job_metadata=job_metadata,working_memory=branch_memory,- output_name=output_name,+ output_name=None,pipe_run_params=branch_pipe_run_params,)tasks.append(task)diff --git a/pipelex/pipelex.py b/pipelex/pipelex.pyindex 6f20d5862..76f3f24be 100644--- a/pipelex/pipelex.py+++ b/pipelex/pipelex.py@@ -148,7 +148,7 @@ class Pipelex(metaclass=MetaSingleton):{report}Config files are invalid for the {component_name}.-You can fix them manually, or run `pipelex init config --reset` to regenerate them.+You can fix them manually, or run `pipelex init config` to regenerate them.Note that this command resets all config files to their default values.If you need help, drop by our Discord: we're happy to assist: {URLs.discord}."""diff --git a/tests/acceptance/init_command.md b/tests/acceptance/init_command.mddeleted file mode 100644index c0719457c..000000000--- a/tests/acceptance/init_command.md+++ /dev/null@@ -1,477 +0,0 @@-# Init Command - Acceptance Test Checklist--This document provides a comprehensive checklist for manually testing all scenarios of the `pipelex init` command.--## Pre-Test Setup--Before each test scenario, ensure:--- [ ] You have a clean test environment (consider using a temporary directory)-- [ ] No `.pipelex/` directory exists in your test location-- [ ] You have write permissions in the test directory--## Test Scenarios--### 1. First-Time Full Initialization (`pipelex init`)--**Test Case 1.1: Complete initialization with default selections**--- [ ] Run: `pipelex init`-- [ ] Verify welcome panel is displayed with list of actions-- [ ] Press Enter to confirm initialization-- [ ] Verify config files are copied successfully-- [ ] Verify backend selection panel is displayed with numbered options-- [ ] Select option `1` (pipelex_gateway) and press Enter-- [ ] Verify confirmation message shows 1 backend configured-- [ ] Verify routing profile is set to "all_pipelex_gateway"-- [ ] Verify telemetry selection panel is displayed-- [ ] Select option `1` (OFF) and press Enter-- [ ] Verify telemetry mode is set successfully-- [ ] Verify `.pipelex/` directory exists with all config files-- [ ] Verify `.pipelex/inference/backends.toml` has pipelex_gateway enabled-- [ ] Verify `.pipelex/inference/routing_profiles.toml` has active = "all_pipelex_gateway"-- [ ] Verify `.pipelex/telemetry.toml` has telemetry_mode = "off"--**Test Case 1.2: Initialization with multiple backends**--- [ ] Run: `pipelex init`-- [ ] Confirm initialization-- [ ] Note the displayed backend numbers, then select 3 backends (e.g., openai, anthropic, mistral) using their indices-- [ ] Verify confirmation shows 3 backends configured-- [ ] Verify "Setting up routing for multiple backends" message-- [ ] Verify primary backend selection panel is displayed-- [ ] Select primary backend (e.g., `1` for the first in your selection)-- [ ] Verify fallback order panel is displayed-- [ ] Press Enter to keep default order or enter custom order (e.g., `2,1`)-- [ ] Verify "custom_routing" profile is created and set as active-- [ ] Verify `.pipelex/inference/routing_profiles.toml` contains custom_routing profile-- [ ] Verify fallback_order is set correctly--**Test Case 1.3: Initialization with all backends**--- [ ] Run: `pipelex init`-- [ ] Confirm initialization-- [ ] Enter `a` or `all` for backend selection-- [ ] Verify all backends (except internal) are enabled-- [ ] Follow through routing and telemetry setup-- [ ] Verify all backends are enabled in backends.toml--**Test Case 1.4: Cancel at backend selection**--- [ ] Run: `pipelex init`-- [ ] Confirm initialization-- [ ] Enter `q` or `quit` at backend selection-- [ ] Verify graceful exit with message-- [ ] Verify config files were created but backends.toml remains in template state--**Test Case 1.5: Cancel at initialization confirmation**--- [ ] Run: `pipelex init`-- [ ] Enter `n` when asked to continue-- [ ] Verify cancellation message-- [ ] Verify suggestion to run `pipelex init` later-- [ ] Verify no files were created-------### 2. Focused Initialization - Config Only--**Test Case 2.1: Initialize config files only**--- [ ] Run: `pipelex init config`-- [ ] Confirm initialization-- [ ] Verify config files are copied-- [ ] Verify NO backend selection prompt appears-- [ ] Verify NO telemetry prompt appears-- [ ] Verify `.pipelex/` directory exists with config files-- [ ] Verify `.pipelex/inference/backends.toml` exists in template state--**Test Case 2.2: Config already initialized**--- [ ] Run: `pipelex init config` (after already initialized)-- [ ] Verify message: "Configuration files are already in place!"-- [ ] Verify tip about using `--reset`-- [ ] Verify no changes made-------### 3. Focused Initialization - Inference Only--**Test Case 3.1: Initialize inference with existing config**--- [ ] Ensure `.pipelex/` exists (run `pipelex init config` first)-- [ ] Run: `pipelex init inference`-- [ ] Verify backend selection panel is displayed-- [ ] Note the displayed backend numbers, then select 2 backends (e.g., openai, anthropic) using their indices-- [ ] Verify backends are enabled in backends.toml-- [ ] Verify routing is configured automatically-- [ ] Verify NO telemetry prompt appears--**Test Case 3.2: Initialize inference without config files**--- [ ] Remove `.pipelex/` directory-- [ ] Run: `pipelex init inference`-- [ ] Verify warning about missing backends.toml-- [ ] Verify command handles gracefully--**Test Case 3.3: Inference already configured**--- [ ] Run: `pipelex init inference` (after already configured)-- [ ] Verify message: "Inference backends are already configured!"-- [ ] Verify question: "Would you like to reconfigure inference backends?"-- [ ] Enter `y` to reconfigure-- [ ] Verify backend selection panel appears with current selection shown-- [ ] Verify you can change backends-- [ ] Verify routing is updated based on new selection--**Test Case 3.4: Decline reconfiguration**--- [ ] Run: `pipelex init inference` (after already configured)-- [ ] Enter `n` when asked to reconfigure-- [ ] Verify "No changes made" message-- [ ] Verify no changes to backends.toml-------### 4. Focused Initialization - Routing Only--**Test Case 4.1: Configure routing with multiple backends enabled**--- [ ] Ensure `.pipelex/` exists with multiple backends enabled-- [ ] Run: `pipelex init routing`-- [ ] Verify primary backend selection panel-- [ ] Select primary backend-- [ ] Verify fallback order configuration-- [ ] Configure order and confirm-- [ ] Verify routing_profiles.toml is updated with custom_routing--**Test Case 4.2: Configure routing with single backend**--- [ ] Ensure only one backend is enabled-- [ ] Run: `pipelex init routing`-- [ ] Verify profile is set to `all_{backend_key}`-- [ ] Verify no primary/fallback prompts--**Test Case 4.3: Configure routing with no backends enabled**--- [ ] Disable all backends in backends.toml-- [ ] Run: `pipelex init routing`-- [ ] Verify warning: "No backends enabled. Please run 'pipelex init inference' first."-- [ ] Verify no changes to routing_profiles.toml--**Test Case 4.4: Routing already configured**--- [ ] Run: `pipelex init routing` (after already configured)-- [ ] Verify message: "Routing profile is already configured!"-- [ ] Verify question about reconfiguration-- [ ] Test both accepting and declining reconfiguration-------### 5. Focused Initialization - Telemetry Only--**Test Case 5.1: Initialize telemetry only**--- [ ] Ensure `.pipelex/` exists without telemetry.toml-- [ ] Run: `pipelex init telemetry`-- [ ] Verify telemetry selection panel-- [ ] Select option `2` (ANONYMOUS)-- [ ] Verify telemetry.toml is created with mode = "anonymous"-- [ ] Verify NO backend or routing prompts--**Test Case 5.2: Telemetry already configured**--- [ ] Run: `pipelex init telemetry` (after already configured)-- [ ] Verify message: "Telemetry preferences are already configured!"-- [ ] Verify question about reconfiguration-- [ ] Enter `y` to reconfigure-- [ ] Select different mode-- [ ] Verify telemetry.toml is updated--**Test Case 5.3: Cancel telemetry selection**--- [ ] Run: `pipelex init telemetry`-- [ ] Enter `q` at telemetry prompt-- [ ] Verify graceful exit-- [ ] Verify telemetry.toml is not created-------### 6. Reset Operations--**Test Case 6.1: Reset all with --reset**--- [ ] Ensure `.pipelex/` fully configured-- [ ] Run: `pipelex init --reset`-- [ ] Verify panel shows "Resetting Configuration" (yellow)-- [ ] Verify all items listed for reset-- [ ] Confirm reset-- [ ] Go through all selections again-- [ ] Verify all files are overwritten-- [ ] Verify new selections are applied--**Test Case 6.2: Reset config only**--- [ ] Run: `pipelex init config --reset`-- [ ] Verify config files are overwritten-- [ ] Verify backend selection prompt appears-- [ ] Complete configuration-- [ ] Verify backends.toml and routing are updated--**Test Case 6.3: Reset inference only**--- [ ] Run: `pipelex init inference --reset`-- [ ] Verify backend selection appears-- [ ] Change backend selection-- [ ] Verify backends.toml is updated-- [ ] Verify routing is reconfigured--**Test Case 6.4: Reset routing only**--- [ ] Run: `pipelex init routing --reset`-- [ ] Verify routing configuration prompts-- [ ] Change routing configuration-- [ ] Verify routing_profiles.toml is updated--**Test Case 6.5: Reset telemetry only**--- [ ] Run: `pipelex init telemetry --reset`-- [ ] Verify telemetry prompt-- [ ] Change telemetry mode-- [ ] Verify telemetry.toml is updated-------### 7. All Already Configured--**Test Case 7.1: Everything configured**--- [ ] Ensure complete initialization-- [ ] Run: `pipelex init`-- [ ] Verify message: "Pipelex is already fully initialized!"-- [ ] Verify tip about `--reset`-- [ ] Verify no prompts appear-- [ ] Verify no changes made-------### 8. Input Validation--**Test Case 8.1: Invalid backend selection - out of range**--- [ ] Run: `pipelex init`-- [ ] Enter invalid index like `99`-- [ ] Verify error message with valid range-- [ ] Verify prompt repeats-- [ ] Enter valid selection-- [ ] Verify successful continuation--**Test Case 8.2: Invalid backend selection - non-numeric**--- [ ] Run: `pipelex init`-- [ ] Enter invalid input like `abc`-- [ ] Verify error message-- [ ] Verify prompt repeats-- [ ] Enter valid selection--**Test Case 8.3: Space-separated backend indices**--- [ ] Run: `pipelex init`-- [ ] Note the displayed backend numbers, then enter 3 backend indices with spaces (e.g., for openai, anthropic, mistral)-- [ ] Verify backends are parsed correctly-- [ ] Verify all selected backends are enabled--**Test Case 8.4: Default selection (press Enter)**--- [ ] Run: `pipelex init`-- [ ] Press Enter at backend selection (accept default)-- [ ] Verify default backend (1 - pipelex_inference) is selected--**Test Case 8.5: Keep current selection**--- [ ] Run: `pipelex init inference` (with existing selection)-- [ ] Agree to reconfigure-- [ ] Press Enter at backend selection-- [ ] Verify current selection is kept--**Test Case 8.6: Invalid telemetry selection**--- [ ] Run: `pipelex init`-- [ ] Complete to telemetry prompt-- [ ] Enter invalid option like `5`-- [ ] Verify error message-- [ ] Enter valid option-- [ ] Verify successful completion--**Test Case 8.7: Invalid fallback order - wrong count**--- [ ] Select 3+ backends-- [ ] At fallback order prompt, enter only 2 indices-- [ ] Verify error: "You must specify all X backends"-- [ ] Enter correct count of indices-- [ ] Verify successful ordering--**Test Case 8.8: Invalid fallback order - duplicates**--- [ ] Select 3+ backends-- [ ] At fallback order prompt, enter `1 1 2`-- [ ] Verify error: "Duplicate indices not allowed"-- [ ] Enter valid unique indices-- [ ] Verify successful ordering-------### 9. Edge Cases--**Test Case 9.1: pipelex_gateway always sets all_pipelex_gateway**--- [ ] Run: `pipelex init`-- [ ] Select pipelex_gateway as one of multiple backends-- [ ] Verify routing is set to "all_pipelex_gateway" automatically-- [ ] Verify NO primary/fallback prompts--**Test Case 9.2: Single non-pipelex backend**--- [ ] Run: `pipelex init`-- [ ] Note the displayed backend numbers, then select only one backend (e.g., openai) using its index-- [ ] Verify routing is set to "all_{backend_key}" (e.g., "all_openai")-- [ ] Verify profile is created if it doesn't exist-- [ ] Verify NO primary/fallback prompts--**Test Case 9.3: Profile creation confirmation**--- [ ] Select a single obscure backend-- [ ] If profile doesn't exist in template, verify prompt to create-- [ ] Accept profile creation-- [ ] Verify profile is created in routing_profiles.toml--**Test Case 9.4: Decline profile creation**--- [ ] Select a backend without existing profile-- [ ] Decline profile creation when prompted-- [ ] Verify message: "Keeping current routing profile configuration"-- [ ] Verify no changes to routing_profiles.toml--**Test Case 9.5: Two backends (automatic fallback)**--- [ ] Select exactly 2 backends-- [ ] Select primary backend-- [ ] Verify fallback_order is set automatically with both backends-- [ ] Verify NO fallback ordering prompt (only 1 remaining)-------### 10. Files and Directory Structure--**Test Case 10.1: Verify directory structure**--After complete initialization, verify:--- [ ] `.pipelex/` directory exists-- [ ] `.pipelex/pipelex.toml` exists-- [ ] `.pipelex/inference/` directory exists-- [ ] `.pipelex/inference/backends.toml` exists-- [ ] `.pipelex/inference/routing_profiles.toml` exists-- [ ] `.pipelex/telemetry.toml` exists-- [ ] All other expected config files from template are present--**Test Case 10.2: Verify file contents - backends.toml**--- [ ] Open `.pipelex/inference/backends.toml`-- [ ] Verify selected backends have `enabled = true`-- [ ] Verify non-selected backends have `enabled = false`-- [ ] Verify `internal` backend is always enabled--**Test Case 10.3: Verify file contents - routing_profiles.toml**--- [ ] Open `.pipelex/inference/routing_profiles.toml`-- [ ] Verify `active` field matches expected profile-- [ ] If custom_routing: verify `default` and `fallback_order` fields-- [ ] Verify `routes` section exists--**Test Case 10.4: Verify file contents - telemetry.toml**--- [ ] Open `.pipelex/telemetry.toml`-- [ ] Verify `telemetry_mode` matches selection-- [ ] Verify valid values: "off", "anonymous", or "identified"--**Test Case 10.5: Existing files not overwritten (without reset)**--- [ ] Modify `.pipelex/pipelex.toml` (add a comment)-- [ ] Run: `pipelex init config`-- [ ] Verify your comment is preserved-- [ ] Verify message about skipped existing files-------### 11. Doctor Integration--**Test Case 11.1: Doctor command suggests init**--- [ ] Remove `.pipelex/` directory-- [ ] Run: `pipelex doctor`-- [ ] Verify doctor detects missing configuration-- [ ] Follow suggestion to run init-- [ ] Verify successful configuration-------### 12. Performance and UX--**Test Case 12.1: Responsive feedback**--- [ ] Run: `pipelex init`-- [ ] Verify all prompts appear immediately-- [ ] Verify success messages appear after actions-- [ ] Verify progress is clear at each step--**Test Case 12.2: Clear instructions**--- [ ] Run through full initialization-- [ ] Verify all panels have clear titles-- [ ] Verify all prompts have clear instructions-- [ ] Verify examples are provided (e.g., "1,5,6 or 1 5 6")-- [ ] Verify default values are clearly indicated--**Test Case 12.3: Error recovery**--- [ ] Make intentional errors at each prompt-- [ ] Verify error messages are helpful-- [ ] Verify you can recover and continue-- [ ] Verify no need to restart from beginning-------## Test Environment Cleanup--After completing tests:--- [ ] Remove test `.pipelex/` directories-- [ ] Document any issues found-- [ ] Note any unclear UX or confusing prompts-- [ ] Record any unexpected behavior-------## Sign-Off--**Tester Name:** _________________________--**Date:** _________________________--**Test Environment:**--- OS: _________________________-- Python Version: _________________________-- Pipelex Version: _________________________--**Overall Result:** [ ] PASS [ ] FAIL--**Notes:**--_____________________________________________________________________________--_____________________________________________________________________________--_____________________________________________________________________________-diff --git a/tests/e2e/pipelex/cli/test_init_cmd_edge_cases.py b/tests/e2e/pipelex/cli/test_init_cmd_edge_cases.pyindex a782fc6ea..3aaab1094 100644--- a/tests/e2e/pipelex/cli/test_init_cmd_edge_cases.py+++ b/tests/e2e/pipelex/cli/test_init_cmd_edge_cases.py@@ -88,7 +88,7 @@ class TestEdgeCases:env.verify_routing("custom_routing", expected_default="anthropic", expected_fallback_order=["anthropic", "openai"])def test_reset_all_with_flag(self, tmp_path: Path, mocker: MockerFixture) -> None:- """Test Case 6.1: Reset all with --reset flag."""+ """Test Case 6.1: Reset all (init always resets)."""# Setup environment with existing configenv = MockedInitEnvironment(tmp_path, mocker)env.setup_with_configs(include_backends=True, include_routing=True, include_telemetry=True)