fruxon 2.2.6__tar.gz → 2.2.8__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {fruxon-2.2.6 → fruxon-2.2.8}/HISTORY.md +196 -0
- fruxon-2.2.6/README.md → fruxon-2.2.8/PKG-INFO +57 -10
- fruxon-2.2.6/PKG-INFO → fruxon-2.2.8/README.md +23 -45
- {fruxon-2.2.6 → fruxon-2.2.8}/pyproject.toml +9 -3
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/__init__.py +4 -0
- fruxon-2.2.8/src/fruxon/_request_id.py +75 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/_version.py +2 -2
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/checks/agent.py +100 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/__init__.py +84 -14
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/_crash.py +65 -27
- fruxon-2.2.8/src/fruxon/cli/_last_failure.py +124 -0
- fruxon-2.2.8/src/fruxon/cli/_ledger_passes.py +88 -0
- fruxon-2.2.8/src/fruxon/cli/_plugin_hint.py +65 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents.py +1 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_draft.py +20 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_improvements.py +251 -56
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_revisions.py +52 -5
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_sandbox.py +322 -49
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_topics.py +1 -1
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/auth.py +51 -21
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/escalations.py +169 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/examples.py +29 -8
- fruxon-2.2.8/src/fruxon/cli/feedback.py +447 -0
- fruxon-2.2.8/src/fruxon/cli/integrations_sandbox.py +418 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/knowledge_documents.py +139 -15
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/knowledge_sources.py +21 -3
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/llm_providers.py +15 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/triggers_ledger.py +32 -4
- fruxon-2.2.8/src/fruxon/cli/working_hours.py +352 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/device_auth.py +5 -1
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/exceptions.py +26 -2
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/fruxon.py +300 -28
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/models.py +56 -1
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/sandbox_scenario.py +50 -2
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/skills/fruxon-agent-mode/SKILL.md +104 -13
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/skills/fruxon-build-agent/SKILL.md +94 -18
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/skills/fruxon-debug-trace/SKILL.md +10 -2
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/skills/fruxon-meet/SKILL.md +5 -1
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/skills/fruxon-use-integrations/SKILL.md +4 -1
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/ui.py +118 -8
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/conftest.py +1 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_agents_check_cli.py +99 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_agents_revisions_cli.py +68 -1
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_agents_sandbox.py +273 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_cli.py +67 -26
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_cli_crash.py +118 -3
- fruxon-2.2.8/tests/test_cli_feedback.py +502 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_draft_validate_cli.py +71 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_improvements.py +187 -2
- fruxon-2.2.8/tests/test_integration_sandbox_cli.py +204 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_knowledge_documents.py +76 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_knowledge_sources.py +46 -0
- fruxon-2.2.8/tests/test_llm_providers_list_cli.py +65 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_plugin_hint.py +27 -0
- fruxon-2.2.8/tests/test_project_urls.py +25 -0
- fruxon-2.2.8/tests/test_request_id.py +346 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_sandbox_scenario.py +64 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_triggers_ledger.py +129 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_ui.py +5 -2
- fruxon-2.2.8/tests/test_working_hours_cli.py +281 -0
- fruxon-2.2.6/src/fruxon/cli/_plugin_hint.py +0 -25
- {fruxon-2.2.6 → fruxon-2.2.8}/.gitignore +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/LICENSE +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/__main__.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/_ssl.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/checks/__init__.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/checks/ledger.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/checks/references.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/_schema.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/_shared.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/_stream.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_approvals.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_budget.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_channels.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_evaluations.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_executions.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_lifecycle.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_memory.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_reply_style.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_sandbox_test.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_slots.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_system_blocks.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_tests.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/agents_voice_calls.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/applications.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/applications_entry_points.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/assets.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/capabilities.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/completion.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/config.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/consult_pins.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/conversation_imports.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/dash.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/describe.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/doctor.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/environments.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/guides.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/integrations.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/keys.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/knowledge_bases.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/knowledge_notices.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/messages.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/metrics.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/participants.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/pipelines.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/secrets.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/skills.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/storage.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/tools.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/triggers.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/triggers_budget.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/triggers_check.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/triggers_ledger_stage_tests.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/triggers_questions.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/triggers_shape.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/cli/workspaces.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/credentials.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/doctor.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/flow_validation.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/output.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/params.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/skills/__init__.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/skills/fruxon-create-integration/SKILL.md +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/telemetry.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/__init__.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/app.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/demo.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/links.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/screens/__init__.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/screens/agent.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/screens/base.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/screens/home.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/screens/ledger.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/screens/loader.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/screens/pickers.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/screens/trace.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/source.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/theme.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/views.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/tui/widgets.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/update_check.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/src/fruxon/validation.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/.test_durations.json +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/__init__.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_actor.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_agent_lifecycle.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_agent_revisions_list.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_agent_slots.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_applications.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_approvals.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_assets.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_budgets.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_capabilities.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_channels.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_checks_agent.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_checks_ledger.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_cli_base_url_routing.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_cli_root_flags.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_client.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_connect_nudge.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_consult.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_conversation_imports.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_credentials.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_dash_app.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_dash_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_dash_client.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_dash_links.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_dash_source.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_describe.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_device_auth.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_docs_commands_exist.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_doctor.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_draft_bootstrap.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_draft_evaluate_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_draft_pull_shape.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_draft_run_replay.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_drafts.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_entry_points.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_environments.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_escalations.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_evaluations.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_execution_records.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_flow_validation.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_fruxon.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_guides.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_integration_configs_write_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_integration_triggers_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_integrations_authorize_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_integrations_connect_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_kb_trial_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_knowledge_bases.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_knowledge_notices.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_llm_provider_configs_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_llm_providers_connect_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_managed_by.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_memory.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_messages.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_metrics.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_online_llm_config_refs.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_online_prefetch_refs.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_online_secret_refs.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_output.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_params.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_participants.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_participants_write.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_pipelines.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_reply_style.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_schema.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_schema_fetch.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_secrets.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_skills.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_ssl.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_storage.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_system_blocks.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_system_blocks_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_telemetry.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_test_chats.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_topics.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_trigger_budgets.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_triggers.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_triggers_check_cli.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_triggers_ledger_batch_views.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_triggers_ledger_stage_tests.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_triggers_questions.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_triggers_shape.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_triggers_write.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_tui_boundary.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_update_check.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_validation.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_voice_calls.py +0 -0
- {fruxon-2.2.6 → fruxon-2.2.8}/tests/test_workspaces_cli.py +0 -0
|
@@ -1,5 +1,201 @@
|
|
|
1
1
|
# History
|
|
2
2
|
|
|
3
|
+
## Unreleased — Improvements reviews on Fruxon's reviewer model, for credits
|
|
4
|
+
|
|
5
|
+
- **`fruxon agents improvements settings`** chooses where reviews run:
|
|
6
|
+
- **`--run-on fruxon`** uses Fruxon's reviewer model, at a fixed number of credits per reviewed
|
|
7
|
+
conversation under a daily limit, `--daily-credits` (1–10,000).
|
|
8
|
+
- **`--run-on own`** uses a model of your own, as before.
|
|
9
|
+
- **Left out:** the agent keeps where it runs, and `--daily-credits` keeps the stored limit.
|
|
10
|
+
Neither is sent, so a save never changes who pays.
|
|
11
|
+
- **On Fruxon's model:** `--on` needs no model. `--provider`, `--model`, `--llm-config`,
|
|
12
|
+
`--param` and `--daily-budget` are refused, with a hint to add `--run-on own`.
|
|
13
|
+
- **Agent mode:** `--run-on` needs `--yes`, like `--on`.
|
|
14
|
+
- **Output:** it shows where reviews run, today's credits against the limit, and why Fruxon's
|
|
15
|
+
model can't run the agent's reviews when it can't.
|
|
16
|
+
- **Older servers:** against a server that doesn't offer Fruxon's model yet, `--run-on` and
|
|
17
|
+
`--daily-credits` are refused rather than silently dropped.
|
|
18
|
+
- **`review` and `revise`** name the credits they cost on Fruxon's model when they refuse in agent
|
|
19
|
+
mode without `--yes`. Only then do they read the settings; a confirmed run makes no extra call.
|
|
20
|
+
- **`status`** says why a conversation was let go: `SKIPPED_BUDGET` (the daily limit ran out) or
|
|
21
|
+
the new `SKIPPED_NO_CREDITS` (the workspace had no credits left).
|
|
22
|
+
- **`FruxonClient.update_review_settings(..., run_on=, daily_credit_limit=)`**: both keyword-only
|
|
23
|
+
and sent only when given. **`get_review_settings`** documents `runOn`, `dailyCreditLimit`,
|
|
24
|
+
`spentTodayCredits`, `creditsPerReview`, `creditsPerRevise` and `laneUnavailableReason`.
|
|
25
|
+
- Needs fruxon-backend #1832 on the server.
|
|
26
|
+
|
|
27
|
+
## Unreleased — `fruxon feedback`: report a problem from the CLI
|
|
28
|
+
|
|
29
|
+
- **`fruxon feedback "<what happened>"`** files a report with Fruxon support:
|
|
30
|
+
the message, `--kind bug|idea|docs|other`, where the CLI ran, and the last
|
|
31
|
+
failed command with its request id. The failure is attached only if it's
|
|
32
|
+
under an hour old and from this workspace, and never with its arguments.
|
|
33
|
+
- **A person** sees everything first and confirms (`--yes` skips the
|
|
34
|
+
prompt). With no message, it opens `$EDITOR`.
|
|
35
|
+
- **An agent** files without a prompt and gets
|
|
36
|
+
`{"id", "reference", "receivedAt"}` back. Agent reports are off when
|
|
37
|
+
telemetry is off (exit 16).
|
|
38
|
+
- **`--crash-log`** takes only a `crash-*.log` the CLI wrote, up to 64 KB.
|
|
39
|
+
- **`--dry-run`** prints the body and sends nothing.
|
|
40
|
+
- **When it can't send** (signed out, a refused key, a server without the
|
|
41
|
+
endpoint), it says it didn't send and prints the report to email instead.
|
|
42
|
+
- Needs fruxon-backend #1828 on the server. Before that it answers exit 11.
|
|
43
|
+
- **Crashes point at it.** The crash message, the crash log and the agent
|
|
44
|
+
envelope's `report` now say
|
|
45
|
+
`fruxon feedback --crash-log <file> "<what you were doing>"`. The support
|
|
46
|
+
address stays as the fallback.
|
|
47
|
+
- **Server errors suggest it.** Under a 5xx (exit 14) people see
|
|
48
|
+
`Report it: fruxon feedback "<what you were doing>"`, and the agent error
|
|
49
|
+
envelope carries it in a new `feedback` field.
|
|
50
|
+
- **`FruxonClient.submit_cli_feedback(...)`**, and
|
|
51
|
+
**`FruxonAPIError.retry_after`**: a 429's `Retry-After`, in seconds.
|
|
52
|
+
|
|
53
|
+
## Unreleased — CLI friction fixes from building a clinic front-desk agent
|
|
54
|
+
|
|
55
|
+
- **A closed pipe exits 141**, not 1: `fruxon llm-providers list | head -c 2500`
|
|
56
|
+
ends the way any Unix tool killed by SIGPIPE does (128 + 13), so a driver
|
|
57
|
+
checking exit codes does not read the reader leaving as a failed command.
|
|
58
|
+
- **`fruxon login` works in agent mode.** It used to exit 16
|
|
59
|
+
(`interactive_required`). It now prints the approval link and user code as a
|
|
60
|
+
JSON line on stdout (`"event":"device_authorization"`) for the driver to
|
|
61
|
+
relay to its human, keeps polling, and prints `"event":"signed_in"` once they
|
|
62
|
+
approve. No browser is opened and the key never appears on stdout or a
|
|
63
|
+
command line.
|
|
64
|
+
- **`llm-providers list` marks hosted providers** (surface `FRUXON_HOSTED`,
|
|
65
|
+
e.g. `fruxon_managed_gemini`) *hosted — no config needed*, and the
|
|
66
|
+
build-agent skill no longer says `provider.tenantConfigId` is required for
|
|
67
|
+
them: the server synthesises their config, and `connect` refuses them.
|
|
68
|
+
- **`agents revisions create --deploy` skips the deploy when the new revision
|
|
69
|
+
is already live** — an agent's first revision goes live on create, and the
|
|
70
|
+
redundant deploy call was refused with a bare `403 Error:` on the default
|
|
71
|
+
developer key. A 403 from the deploy step (here and in `revisions deploy`)
|
|
72
|
+
now names the missing `revisions:deploy` scope and `fruxon login --preset
|
|
73
|
+
maintainer`.
|
|
74
|
+
- **`knowledge-bases add-document --markdown <file.md>`** adds a Markdown file
|
|
75
|
+
as an article without hand-building a JSON body: the title is `--title` or
|
|
76
|
+
the file's first `# ` heading (else its name), with `--status` and
|
|
77
|
+
`--locale`. A directory adds every `.md` in it, one article each.
|
|
78
|
+
- **`fruxon working-hours list/get/create/update/delete`** over the workspace's
|
|
79
|
+
working-hours schedules (`--hours "sun-thu 08:00-20:00"`, `--closed`,
|
|
80
|
+
or `--file`).
|
|
81
|
+
- **`fruxon escalations set-policy <agent>`** changes the escalation desk the
|
|
82
|
+
agent's hand-off goes to: `--operator` (the ladder), `--working-hours`,
|
|
83
|
+
`--default-reason`, `--entry-point` for a channel's desk. `escalations
|
|
84
|
+
policy` now names the desk too.
|
|
85
|
+
- **`agents check` gains an Escalation row**, and `draft validate --online` an
|
|
86
|
+
`escalation_unreachable` warning: an agent with escalation on whose desk has
|
|
87
|
+
no operators (or whose channel has no desk) told customers it handed them
|
|
88
|
+
off while it reached nobody.
|
|
89
|
+
- **`integrations configs create <integration> --simulated`** creates a
|
|
90
|
+
`SIMULATED` config with no credentials and publishes it — what took
|
|
91
|
+
`connect`, `configs update` and `configs publish`. **`integrations configs
|
|
92
|
+
sandbox status/entities/generate/import/reset/snapshot/restore`** read and
|
|
93
|
+
seed its store, and scenario files take a `seed` setup step. The
|
|
94
|
+
build-agent skill gains a "Simulate first" section.
|
|
95
|
+
- **The Claude Code plugin hint is printed at most once a day per machine**
|
|
96
|
+
(marker: `<config dir>/plugin-hint-shown`), not on every command. It went to
|
|
97
|
+
stderr on every invocation under Claude Code, so `fruxon … 2>&1 | json.load`
|
|
98
|
+
failed every time.
|
|
99
|
+
|
|
100
|
+
## Unreleased — every request carries an id support can find; the last failure is kept
|
|
101
|
+
|
|
102
|
+
- **Every API request now sends `X-Correlation-ID`** (`cli-<32 hex>`, or
|
|
103
|
+
`sdk-…` from the Python client). The server already keeps a caller's id,
|
|
104
|
+
returns it, and writes it on every log line for the request
|
|
105
|
+
(`labels.correlation_id`), including in the workers it hands work to.
|
|
106
|
+
- **Errors carry it.** `FruxonError.request_id` is set on any SDK error that
|
|
107
|
+
came from a request. On an HTTP error it is the id the server echoed; on a
|
|
108
|
+
connection error or timeout, the id that was sent.
|
|
109
|
+
- **The CLI shows it** as `Request: cli-…` under a 5xx or a network failure,
|
|
110
|
+
and as `request_id` in the agent-mode error envelope (any failure from a
|
|
111
|
+
request, 4xx included).
|
|
112
|
+
- **`<config dir>/last-failure.json`** (mode 0600) keeps the last failed
|
|
113
|
+
command: its name, exit code, error code and class, the message the CLI
|
|
114
|
+
printed, HTTP status, server code, request id, and for a crash the
|
|
115
|
+
fingerprint and crash log. Never arguments or option values. A parse error,
|
|
116
|
+
Ctrl-C, a declined prompt or a closed pipe doesn't replace it.
|
|
117
|
+
- `FRUXON_CORRELATION_ID` sends one id of your choosing on every request, to
|
|
118
|
+
tie a script's commands together (1–64 letters, digits and hyphens;
|
|
119
|
+
anything else is ignored).
|
|
120
|
+
- **Why:** a failure could not be matched to the request the server logged,
|
|
121
|
+
so neither a support email nor a crash report could point at what
|
|
122
|
+
happened. This is the first step toward `fruxon feedback`.
|
|
123
|
+
|
|
124
|
+
## Unreleased — piping into `head` is not a crash; crash reports go to support
|
|
125
|
+
|
|
126
|
+
- **`fruxon describe | head` no longer reports a crash.** When the program
|
|
127
|
+
reading the CLI's output exits early, the CLI now exits 1 quietly, as Click
|
|
128
|
+
intends. Before, it said "The Fruxon CLI hit a bug", wrote a crash log, and in
|
|
129
|
+
agent mode printed an `internal_error` envelope. A short output (under the
|
|
130
|
+
pipe buffer) printed Python's own "Exception ignored … BrokenPipeError" and
|
|
131
|
+
exited 120 instead.
|
|
132
|
+
- **Why:** this was the only crash the CLI reported between 2026-10-18 and
|
|
133
|
+
2026-11-16, ten times across both cells. Telemetry now files it as
|
|
134
|
+
`user_input` with no fingerprint, not `network`.
|
|
135
|
+
- **A crash report now says to email support@fruxon.com** with the crash log
|
|
136
|
+
attached. The log carries the subject line to use. In agent mode the
|
|
137
|
+
envelope's `report` is `mailto:support@fruxon.com`.
|
|
138
|
+
- **Why:** the report linked to the SDK's GitHub issues, and that repository is
|
|
139
|
+
private, so the link was a 404 for every customer. No issue was ever filed.
|
|
140
|
+
- The PyPI project links no longer point into the private repository:
|
|
141
|
+
homepage is fruxon.com, documentation is the CLI guide, and bugs is the
|
|
142
|
+
support address.
|
|
143
|
+
|
|
144
|
+
## Unreleased — `--wait` follows a sandbox turn from the start
|
|
145
|
+
|
|
146
|
+
- **`fruxon agents sandbox turn` / `fire` / `fork --send` and `fruxon agents
|
|
147
|
+
improvements test --send` take `--wait`**: the command opens the session's
|
|
148
|
+
stream before it sends the turn, then follows the turn until it ends —
|
|
149
|
+
replied, silent, parked or failed. With `-o json` (the default in agent mode)
|
|
150
|
+
it prints NDJSON: `start`, a `sent` record carrying what the command prints
|
|
151
|
+
today, the frames `stream` prints, then `stopped`. `--wait` with `fork -o id`
|
|
152
|
+
is refused.
|
|
153
|
+
- `--wait` exits 0 only when it saw the turn end. When the stream closes first,
|
|
154
|
+
or `--timeout` seconds pass (default 300), it exits 1 and says where the run
|
|
155
|
+
can be read. A turn the server accepts without starting a run never sends
|
|
156
|
+
`turn_complete`, so without the timeout `--wait` would wait forever.
|
|
157
|
+
`--timeout` without `--wait` is refused.
|
|
158
|
+
- `agents sandbox stream` flushes each NDJSON record as it prints it. Before,
|
|
159
|
+
records written to a file or pipe sat in the buffer until the process ended.
|
|
160
|
+
- **Why:** the stream replays nothing and `turn_complete` is never stored. The
|
|
161
|
+
old recipe — send, then run `sandbox stream` — missed any turn that ended
|
|
162
|
+
before the stream connected, and `stream` then waited forever. A turn that
|
|
163
|
+
stayed silent left no trace at all, so it looked as if it had never run.
|
|
164
|
+
- Without `--wait`, `fork --send` now says where the turn's run can be read
|
|
165
|
+
(`agents executions list <agent> --origin TEST --session <ts_…>`), and the
|
|
166
|
+
text view of a silent `turn_complete` says the agent sent no reply.
|
|
167
|
+
- The turn goes out once the stream's response headers are in, which is when
|
|
168
|
+
the server has registered the subscriber, so `--wait` never sends a turn it
|
|
169
|
+
isn't watching. With fruxon-backend#1822 the headers come at once. An older
|
|
170
|
+
server holds them until its first frame, a heartbeat up to 20 s away on a
|
|
171
|
+
quiet session, and the turn waits that long. If the stream does not open,
|
|
172
|
+
nothing is sent.
|
|
173
|
+
|
|
174
|
+
## Unreleased — passes list the work claimed between them
|
|
175
|
+
|
|
176
|
+
- **`fruxon triggers ledger passes`** and **`fruxon knowledge-bases source
|
|
177
|
+
passes`** show what an automation claimed *between* passes on a row of its
|
|
178
|
+
own: a person answering a question, a finished run moving its item on, a
|
|
179
|
+
re-drive. The row sits just above the pass it followed and says why the
|
|
180
|
+
work was ready ("after an answer"), its runs and its cost. The totals
|
|
181
|
+
include it. In `-o json` each pass gains `betweenPasses` (`null` when
|
|
182
|
+
nothing was claimed; `firstClaimedAt`, `lastClaimedAt`, `dispatched`,
|
|
183
|
+
`completed`, `runs`, `cost`, `causes`).
|
|
184
|
+
- `LedgerPass.between_passes` (`LedgerBetweenPasses`, with
|
|
185
|
+
`LedgerBetweenPassesCause`) carries it in the client.
|
|
186
|
+
- Needs fruxon-backend with the split (fruxon-backend#1818). Before it, a pass
|
|
187
|
+
is credited with everything claimed since the previous pass, so a pass that
|
|
188
|
+
found nothing could show the runs an answer started; an older server sends
|
|
189
|
+
no `betweenPasses` and the listing reads as before.
|
|
190
|
+
|
|
191
|
+
## Unreleased — the developer preset says what it can ship
|
|
192
|
+
|
|
193
|
+
- **`fruxon login --help`** said the default `developer` preset builds, tests
|
|
194
|
+
and runs agents "without deploying live". That wasn't true: publishing a
|
|
195
|
+
new agent's first revision makes it live, and `developer` may publish. The
|
|
196
|
+
help now says so; switching a live agent to another revision still needs
|
|
197
|
+
`maintainer`. Nothing about what the preset grants changed.
|
|
198
|
+
|
|
3
199
|
## Unreleased — `integrations authorize` saves the connection it hands out
|
|
4
200
|
|
|
5
201
|
- **`fruxon integrations authorize`** printed the provider's consent URL from
|
|
@@ -1,8 +1,42 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: fruxon
|
|
3
|
+
Version: 2.2.8
|
|
4
|
+
Summary: The Fruxon SDK is a lightweight Python client for integrating with the Fruxon platform.
|
|
5
|
+
Project-URL: homepage, https://fruxon.com
|
|
6
|
+
Project-URL: documentation, https://docs.fruxon.com/guides/cli
|
|
7
|
+
Author-email: Hagai Cohen <hagai@fruxon.com>
|
|
8
|
+
Maintainer-email: Hagai Cohen <hagai@fruxon.com>
|
|
9
|
+
License: MIT
|
|
10
|
+
License-File: LICENSE
|
|
11
|
+
Classifier: Development Status :: 3 - Alpha
|
|
12
|
+
Classifier: Intended Audience :: Developers
|
|
13
|
+
Classifier: License :: OSI Approved :: MIT License
|
|
14
|
+
Classifier: Programming Language :: Python :: 3
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
18
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
19
|
+
Requires-Python: >=3.10
|
|
20
|
+
Requires-Dist: certifi>=2024.2.2
|
|
21
|
+
Requires-Dist: click>=8.2
|
|
22
|
+
Requires-Dist: keyring>=24.0
|
|
23
|
+
Requires-Dist: typer>=0.13
|
|
24
|
+
Provides-Extra: test
|
|
25
|
+
Requires-Dist: coverage; extra == 'test'
|
|
26
|
+
Requires-Dist: ipdb; extra == 'test'
|
|
27
|
+
Requires-Dist: pre-commit; extra == 'test'
|
|
28
|
+
Requires-Dist: pytest; extra == 'test'
|
|
29
|
+
Requires-Dist: ruff; extra == 'test'
|
|
30
|
+
Requires-Dist: ty; extra == 'test'
|
|
31
|
+
Provides-Extra: tui
|
|
32
|
+
Requires-Dist: textual>=8.2; extra == 'tui'
|
|
33
|
+
Description-Content-Type: text/markdown
|
|
34
|
+
|
|
1
35
|
# fruxon
|
|
2
36
|
|
|
3
37
|
[](https://pypi.org/project/fruxon/)
|
|
4
38
|
[](https://pypi.org/project/fruxon/)
|
|
5
|
-
[](https://
|
|
39
|
+
[](https://pypi.org/project/fruxon/)
|
|
6
40
|
|
|
7
41
|
Run, build, and orchestrate AI agents from your terminal — the official Python SDK and CLI for the [Fruxon](https://fruxon.com) platform.
|
|
8
42
|
|
|
@@ -42,6 +76,7 @@ Top-level discovery commands — useful whether you're a human or an AI agent dr
|
|
|
42
76
|
| `fruxon completion {bash\|zsh\|fish}` | Print a shell-completion script. `eval "$(fruxon completion zsh)"` to install. |
|
|
43
77
|
| `fruxon guides list / show <id>` | Bundled CLI playbooks. Start with `fruxon-meet`; `fruxon-agent-mode` covers the exit codes, error envelope, and output shapes a program driving the CLI relies on. |
|
|
44
78
|
| `fruxon doctor` | Diagnose local setup (interpreter, SDK version, credentials, API reachability, auth). |
|
|
79
|
+
| `fruxon feedback "<what happened>"` | Report a problem (or an idea) to Fruxon support. Attaches the last failed command and its request id; you see it all and confirm first. `--crash-log <file>` sends a crash log, `--dry-run` shows the body without sending. |
|
|
45
80
|
|
|
46
81
|
Auth:
|
|
47
82
|
|
|
@@ -66,12 +101,13 @@ Execution:
|
|
|
66
101
|
| `fruxon agents approvals list/get/respond/cancel <agent>` | Operate human-in-the-loop approval gates — see what a run is blocked on and answer it. `respond`/`cancel` confirm first and refuse without `--yes` in agent mode (an LLM must not silently auto-approve). |
|
|
67
102
|
| `fruxon agents memory list/subjects/get/forget-subject <agent>` | Inspect and prune what an agent remembers. `list` filters server-side by `--subject`/`--query`/`--scope`; `forget-subject` is a GDPR-style delete (confirms; refuses without `--yes` in agent mode). |
|
|
68
103
|
| `fruxon agents topics list/search/get/messages/sessions <agent>` + `fruxon agents inbox <agent>` | Read the conversation spine — the agent's topics (threads), one topic's transcript, its episodes, and its inbox (what it's focused on). `list`/`search` filter server-side by `--state`/`--participant`/`--query`. Read-only. Each message carries `author` — a human colleague's turn is stored as `ASSISTANT` on purpose, so `role` alone cannot tell their reply from the agent's; `HUMAN_OPERATOR` can. A message the runtime *withheld* is in no transcript at all — see `fruxon messages list`. `sessions` explains a fresh, blind session: a topic outlives its sessions, and `endCause` on the previous one (`CONSOLE_ALREADY_RESOLVED` — a human closed it in the provider's console) is why the next started with no history. |
|
|
69
|
-
| `fruxon escalations list/history/unhandled/policy/ack` | What happened when an agent handed a conversation to a person. `list` is the queue (live takeovers + degraded escalations nobody was reachable for); `unhandled` is the append-only ledger under it. **`history` is the record of closed console-routed takeovers** — those leave the queue, so `list --status ALL` answers `[]` about a conversation a human worked for half an hour. Read `humanObservedAt` before believing a `RESOLVED`: null means nobody was ever seen picking it up. `policy <agent>` resolves who the *next* escalation would reach — an empty ladder under `NATIVE_HANDOFF` is correct, the console supplies the human. |
|
|
104
|
+
| `fruxon escalations list/history/unhandled/policy/ack` | What happened when an agent handed a conversation to a person. `list` is the queue (live takeovers + degraded escalations nobody was reachable for); `unhandled` is the append-only ledger under it. **`history` is the record of closed console-routed takeovers** — those leave the queue, so `list --status ALL` answers `[]` about a conversation a human worked for half an hour. Read `humanObservedAt` before believing a `RESOLVED`: null means nobody was ever seen picking it up. `policy <agent>` resolves who the *next* escalation would reach — an empty ladder under `NATIVE_HANDOFF` is correct, the console supplies the human — and names the desk it went through. `set-policy <agent>` changes that desk: `--operator` (repeatable, one tier; `--strategy`), `--working-hours <schedule|none>`, `--default-reason`, `--entry-point` for a channel's desk. It reads the desk and PUTs it back with only those changed, for every agent on the desk (`participants:write`). |
|
|
105
|
+
| `fruxon working-hours list/get/create/update/delete` | Working-hours schedules: a time zone, a week (`--hours "sun-thu 08:00-20:00"`, repeatable; a day not named is closed), dated closures (`--closed 2026-12-25`), or `--file` with the full body. A schedule governs the escalation hand-off once a desk uses it (`escalations set-policy --working-hours`); what the agent says about opening hours stays in its prompt. `participants:read` / `participants:write`. |
|
|
70
106
|
| `fruxon messages list` | The channel ledger — including inbound an agent was never shown. A **withheld** message (a human owns the chat in the source console, or admission refused the sender) never becomes a conversation turn, so it is in no transcript and the thread reads as a customer being ignored. `--delivery WITHHELD_PENDING` lists the ones nothing has ever acted on; nothing drains them. |
|
|
71
|
-
| `fruxon agents sandbox open/turn/fire/resolve-input/stream/answer/close <session>` | Drive an agent-network sandbox end-to-end without real channels — send turns as participants, test-fire triggers, and watch the run (`stream
|
|
107
|
+
| `fruxon agents sandbox open/turn/fire/resolve-input/stream/answer/close <session>` | Drive an agent-network sandbox end-to-end without real channels — send turns as participants, test-fire triggers, and watch the run (`--wait` on `turn` / `fire` follows it to the end; `stream` shows only what happens after it connects; NDJSON in agent mode). Sandbox **captures the reply and hard-blocks every real send**; `--await` makes consult/approval gates suspend so they can be resolved (`answer` for consults, `approvals respond` for approvals). `--draft` runs your unpublished draft instead of the deployed revision (`sandbox draft <session>` says which); `--confirm-writes` holds every create/update/delete tool call for approval, because sandbox does **not** block integration writes; a write that did not run (rejected, expired, or one the run could not pause for) shows on `stream` as `refused`. |
|
|
72
108
|
| `fruxon agents voice-calls list/get <agent>` | Read back the Test lab's Talk calls. `list` gives calls newest first (status, end reason, turns, length). `get <agent> <call-id>` gives the call turn by turn: the caller's transcript, the reply, what was heard of it (`delivery`; `spokenText` when the caller cut in), and each reply's `executionRecordId` for `agents executions trace`. Read-only; needs `executions:read`. |
|
|
73
|
-
| `fruxon agents sandbox fork <agent> <message-id>` | Fork a real conversation at a transcript row (an `id` from `agents topics messages`) into a sandbox session already holding the history the agent had when it produced that reply. `--send` re-sends the customer's message against it — with `--draft` to test an edit before publishing — and holds writes for approval unless `--no-confirm-writes`. |
|
|
74
|
-
| `fruxon agents sandbox test <file-or-dir>` | Run scenario-based e2e tests of an agent's network behavior. A scenario (YAML/JSON) declares `steps` (turns / trigger fires), `responders` (scripted consult/approval answers), and `expect` assertions (reply / routing / tools called or refused / no-leak / outcome); the runner drives a sandbox session and returns one verdict — exit 0 (pass) / 1 (fail) / 12 (bad file), with `--junit` for CI. An optional `setup` block provisions real resources first — an `asset` (uploaded + ingestion-waited), `participant`, or `agent` — templated as `${asset.catalog.id}` and **torn down afterwards even on failure** (`--keep` to inspect). Assertions are deterministic by default; `reply_judge: {metric, min_score}` adds an opt-in **semantic** check that scores the reply against a tenant eval metric. The thing an agent runs to prove the agent it built works. |
|
|
109
|
+
| `fruxon agents sandbox fork <agent> <message-id>` | Fork a real conversation at a transcript row (an `id` from `agents topics messages`) into a sandbox session already holding the history the agent had when it produced that reply. `--send` re-sends the customer's message against it — with `--draft` to test an edit before publishing, and `--wait` to follow the turn until it ends — and holds writes for approval unless `--no-confirm-writes`. |
|
|
110
|
+
| `fruxon agents sandbox test <file-or-dir>` | Run scenario-based e2e tests of an agent's network behavior. A scenario (YAML/JSON) declares `steps` (turns / trigger fires), `responders` (scripted consult/approval answers), and `expect` assertions (reply / routing / tools called or refused / no-leak / outcome); the runner drives a sandbox session and returns one verdict — exit 0 (pass) / 1 (fail) / 12 (bad file), with `--junit` for CI. An optional `setup` block provisions real resources first — an `asset` (uploaded + ingestion-waited), `participant`, or `agent` — templated as `${asset.catalog.id}` and **torn down afterwards even on failure** (`--keep` to inspect) — or a `seed` step that resets, imports into and/or generates a SIMULATED integration config's sandbox store (not torn down; only sandbox runs read it). Assertions are deterministic by default; `reply_judge: {metric, min_score}` adds an opt-in **semantic** check that scores the reply against a tenant eval metric. The thing an agent runs to prove the agent it built works. |
|
|
75
111
|
|
|
76
112
|
Invoking a *deployed* agent in production goes through the [Python client](#the-python-client) (`FruxonClient.stream` / `execute`), not the CLI.
|
|
77
113
|
|
|
@@ -89,7 +125,7 @@ Agent authoring + management:
|
|
|
89
125
|
| `fruxon agents draft validate <id> [--online]` | Lint a draft body locally (no network): a missing `definition`, slot ids, tool→slot wiring, provider config, misplaced `parametersMetadata`. `--online` also resolves references against the live catalog (unknown/unpublished config, unreal model, bad tool id). `{valid, errors, warnings}` envelope (the same `errors` as `agents validate`); exits 12 on any error. `warnings[]` are advisory wiring gaps (`consult_unwired`, `approver_slot_undeclared`) that never flip `valid` or the exit code. |
|
|
90
126
|
| `fruxon agents draft run <id> --file <def.json> [--restore]` | Run a draft definition against an existing agent without publishing it. A CI gate for agent changes. The body goes into the agent's server draft (what `revisions create` publishes); for a file other than the pulled one, `--restore` puts the previous draft back after the run, `--yes` keeps it. |
|
|
91
127
|
| `fruxon agents draft run <id> --replay <run> [--stages <file>]` | Re-run a real execution of the agent on its draft. A run a ledger stage dispatched is replayed as a stage test — on exactly the data it was handed, under the stage's output contract, with no ledger transition or item change; `--stages` swaps in edited stage definitions (the `set-stages` file). Any other run re-runs with the parameters it was recorded with (`-p` overlays them). |
|
|
92
|
-
| `fruxon agents revisions create/get/deploy` | Mint and deploy immutable revisions. `create --deploy` does both in one step. `get --as-draft` converts a stored revision back into a postable body. |
|
|
128
|
+
| `fruxon agents revisions create/get/deploy` | Mint and deploy immutable revisions. `create --deploy` does both in one step, and skips the deploy when the new revision is already live (an agent's first revision goes live on create). Deploying needs `revisions:deploy` (`fruxon login --preset maintainer`); a 403 says so. `get --as-draft` converts a stored revision back into a postable body. |
|
|
93
129
|
| `fruxon agents revisions list/deploys <id>` | `list` shows revisions newest first (20 unless `--all` or `-n`): number, ★ on the live one, who created it and its comment. After a rollback the ★ is not the top row. `-o json` adds `lastDeployedAt`. Bodies are not listed; `get <id> <n>` fetches one. `deploys` is the deploy history: each attempt, failed ones too, `from → to` with ↩ on a rollback, who made it and why. A backend without the list endpoint gets a warning and the same list built from the older history endpoint. |
|
|
94
130
|
| `fruxon agents slots list/bind/unbind <id>` | An agent's contacts — the humans `notify` / `ask` / `escalate` reach. The definition declares them; the binding says who receives (`--participant`, `--role`, or `--queue`). Declared but unbound means the reach-out dead-ends at run time, so `list` calls that out and `unbind` is `--yes`-gated. `bind --role` warns first when nobody holds the role — advisory, since binding ahead of staffing is legitimate. |
|
|
95
131
|
| `fruxon agents check <id>` | Audit whether a **deployed** agent is wired to run end-to-end, beyond the definition: a deployed revision, an inbound path (bound trigger / channel binding / active entry point), a consult roster if the agent enables consult, declared **and bound** contacts, every bound trigger populating the agent's required params, and that the revision's references resolve. `{overall, checks[]}` (doctor-style); exits non-zero only on a hard fail (no deployed revision) — advisory `warn` rows stay exit 0. |
|
|
@@ -109,12 +145,14 @@ Integrations + tools:
|
|
|
109
145
|
| `fruxon integrations list/get/create/update/verify/open` | Manage external integrations — the connections agents draw tools from. `create`/`update`/`verify` take a `--file` JSON body; `open` opens the dashboard. |
|
|
110
146
|
| `fruxon integrations configs list/get/update/publish` | The per-integration auth/config records. `update --file` patches a config's draft (only the fields sent; `{"egressCountry": ""}` clears an egress pin) and prints it with secrets masked; `publish` makes the draft the revision tool calls resolve, asks first (`--yes` in agent mode), and prints the new revision's `id` and `version`, never the credentials. |
|
|
111
147
|
| `fruxon integrations authorize <integration>` | `connect` for an OAuth integration (Gmail, Google Sheets, Outlook…): creates a config for its OAuth2 method (auto-detected; `--auth-method` to pick, `--scope` for what to ask, `--config-param` for connection settings, `--config <id>` for an existing config) and prints a credential link. A human opens it, signs in to Fruxon and then to the provider, and the account is connected and the config published, ready for a slot to pin. |
|
|
148
|
+
| `fruxon integrations configs create <integration> --simulated` | A config with `sandboxMode: SIMULATED` and no credentials, published in one step: every tool call a sandbox run makes through it is answered from its simulated store. `--file` creates an unpublished draft from a full body instead. |
|
|
149
|
+
| `fruxon integrations configs sandbox status/entities/generate/import/reset/snapshot/restore <integration> <config>` | Read and seed a simulated config's store. `generate --type event --prompt … --count N` has a model write entities (the server snapshots first); `import --file` inserts them as written (`payload` may be an object); `snapshot --name` saves a state (no `--name` lists them), `restore` / `reset` are `--yes`-gated. |
|
|
112
150
|
| `fruxon integrations connect <integration>` | Create a config for an integration and print a **credential link**: a human opens it and signs in to Fruxon, then types the API key, token or password (Stripe, most REST APIs), and the page tests it and publishes the config; or, for an OAuth integration, signs in to the provider (`--scope` picks what they grant) and the account is connected and the config published. The secret never passes through the terminal or an agent driving the CLI. `--config <id>` fills an existing config, `--param name=value` sets a connection setting, `--no-sign-in` mints a link anyone holding it can fill (for a client without a Fruxon login), `--expires-in-hours` 1–720. Needs `integrations:write` (the default login preset); `--no-sign-in` also needs `workspace:write` (Admin or Owner). |
|
|
113
151
|
| `fruxon integrations triggers <integration>` | List the event types an integration can fire an agent on — each descriptor's `id` is the `eventType` a trigger listens for, plus the `payloadFields` (dotted paths) a binding's `parameterMappings` can read. Discovery for wiring an inbound-event trigger without guessing. |
|
|
114
152
|
| `fruxon integrations mcp …` | Inspect and enable the MCP server for an integration. |
|
|
115
153
|
| `fruxon tools list/get/create/update/delete/run` | Manage the tools inside an integration. Integration-scoped. `get` and `run` select the tool with `--tool`; `run` executes it outside any agent — real credentials, real result — with `-p key=value`, and `-c` naming the config that supplies credentials. The tenant list API hides internal `knowledge_base` / `assets` tools; `tools list` recovers them by ID and lists them like any other (`--no-include-internal` for the raw server answer). |
|
|
116
154
|
| `fruxon keys list/mint/revoke/delete/history/scopes` | Audit and revoke scoped tokens. Minting opens the dashboard so the secret never enters the CLI process. |
|
|
117
|
-
| `fruxon llm-providers list/get/models` | Browse LLM providers and models supported at the tenant level. |
|
|
155
|
+
| `fruxon llm-providers list/get/models` | Browse LLM providers and models supported at the tenant level. `list` marks a Fruxon-hosted provider (`fruxon_managed_gemini`) *hosted — no config needed*: an agent on it omits `provider.tenantConfigId`. |
|
|
118
156
|
| `fruxon llm-providers connect <provider>` / `link-status` | Create a config for an LLM provider and print a **credential link**: a human opens it, signs in to Fruxon, types the API key (or access keys, or service account key), and the page tests it with the provider and publishes the config an agent pins as `provider.tenantConfigId`. The key never passes through the terminal or an agent driving the CLI. `--config <id>` fills an existing config, `--param name=value` sets a non-secret setting such as Bedrock's `region`, `--no-sign-in` mints a link anyone holding it can fill (Admin or Owner). `link-status <provider> <config> <request> [--wait]` says when it was filled. |
|
|
119
157
|
| `fruxon llm-providers configs list/get/test/publish` | The workspace's saved LLM credentials — the `provider.tenantConfigId` an agent pins. `get` shows the draft (secrets masked), the published revision and last known health. `test` probes the draft on every provider surface that shares the credential (or just one, given that surface's provider id), one line per failing surface, exit 12 on failure (`llm_providers:test`). `publish` ships the draft as a new revision that every agent on the config switches to — it confirms, needs `--yes` in agent mode, and does not wait on a passing test (`llm_providers:write`). |
|
|
120
158
|
| `fruxon llm-providers configs complete <provider> <config> --model M` | One completion on a saved config's published revision, with no agent, session or execution — to see whether a model follows a prompt or a system block's instruction. `--system` (text, `@file`, `-`; repeatable), `-m [user:\|assistant:]TEXT` (repeatable) or `--messages chat.json`, `--temperature`, `--max-tokens` (server cap 8192), `--param k=v`. The reply goes to stdout, the model, finish reason, tokens and latency to stderr (`llm_providers:test`). Fruxon-hosted providers are refused. |
|
|
@@ -122,7 +160,7 @@ Integrations + tools:
|
|
|
122
160
|
| `fruxon knowledge-bases list/get/create/update/publish/archive/delete` | The authored, reviewable corpus behind a `manual_knowledge` asset — **not** the asset itself, which is what gets searched (`get` prints the asset id as `backingAssetId`). **`publish` is the step that makes any of it findable**: only `PUBLISHED` documents travel in a snapshot, and only publishing the *base* moves one, so a base full of finished articles answers nothing until it runs. It returns on *acceptance*, not searchability — RAG ingests afterwards, so a pending publish state is normal. `list` hides archived bases, which keep answering for agents already attached to them; `delete` is refused while an agent revision still attaches one, and `archive` is the reversible path. |
|
|
123
161
|
| `fruxon knowledge-bases usage <kb>` | Whether agents actually use the base: searches per hour, day or week (`--interval`), the passage tokens each search handed the agent, how many found nothing (split from searches that **could not fully search** it — index missing or still building, a phrasing failed), and which agents searched (up to 20 you can open, the rest counted together). `--origin test` counts test runs instead of production. Retrieved tokens are counted by the search index, so what the model read can be less when a large result is trimmed or offloaded. Searches are recorded from 15 October 2026 and kept 90 days at most, so a window reaching further back says where counting began rather than showing empty days. A 404 is a wrong id or a backend that predates the read. |
|
|
124
162
|
| `fruxon knowledge-bases notices/notice/post-notice/edit-notice/extend-notice/withdraw-notice` | Time-boxed notices on a base — an outage being fixed, a known bug, a closure. **Not documents**: never indexed or published, so every agent attaching the base is given each active notice whole from its next turn. `post-notice --valid-for 4h` (or `--until`) — every notice ends, at most 30 days after it was posted, and a base holds ten active ones (409 `notice_limit` / `notice_too_long`, each with its remedy). The body is Markdown, at most 1,200 characters, best as four headings: *What is happening*, *Applies when*, *Tell the customer*, *Do not*. A time without an offset is read in the notice's zone (`--time-zone`, else this machine's), which is also the zone agents tell customers the end in. `withdraw-notice` tells each conversation that was given it, on its next turn, that it ended; it confirms, and needs `--yes` in agent mode. An ended notice is not extended: `post-notice --from <id>` posts it again as a new one. |
|
|
125
|
-
| `fruxon knowledge-bases documents/document/add-document/edit-document/delete-document` | The articles. `--query` matches the title, `--status` narrows to DRAFT / PUBLISHED / ARCHIVED — and `--status DRAFT` is usually the answer to "why can't search see this". `--unpublished` lists only what the next publish changes (new or edited since the last publish, or archived / moved back to draft while agents still get them). `document` prints the Markdown body **unrendered to stdout**: that is the exact text which gets embedded, so it has to be pipeable and byte-faithful. Deleting one leaves the indexed snapshot alone until the base is published again. |
|
|
163
|
+
| `fruxon knowledge-bases documents/document/add-document/edit-document/delete-document` | The articles. `--query` matches the title, `--status` narrows to DRAFT / PUBLISHED / ARCHIVED — and `--status DRAFT` is usually the answer to "why can't search see this". `--unpublished` lists only what the next publish changes (new or edited since the last publish, or archived / moved back to draft while agents still get them). `add-document --markdown <file.md|dir>` adds a Markdown file as an article (title from `--title` or its first `# ` heading; `--status`, `--locale`), or every `.md` in a directory, one article each; `--file` takes the full JSON body. `document` prints the Markdown body **unrendered to stdout**: that is the exact text which gets embedded, so it has to be pipeable and byte-faithful. Deleting one leaves the indexed snapshot alone until the base is published again. |
|
|
126
164
|
| `fruxon knowledge-bases review-queue/revisions/evidence/correct` | `review-queue` carries each draft's newest revision *and the one before it*, so the change is readable without a request per row; a row with no previous revision is a new article, not an edit, and `--order PRIORITY` puts personal-data risks ahead of the routine edits `NEWEST` buries them under; a `Close to:` line names a waiting draft that reads close to the row (the same question drafted twice). `revisions` is the base-wide timeline (or one document's) holding whole bodies rather than diffs, with person, agent and run attribution kept apart. `evidence` returns the source **keys, never the items** — resolving one is the source system's call, so reading an article does not hand you the transcript; an `agent-review:` row names the topic and run it came from and whether the team (`OPERATOR`), a tool or nobody answered it. `correct` runs the base's editor agent over your instruction; it **may decline** (the instruction needs a fact it was not given, or is about a claim the article does not make), which writes nothing and exits non-zero, and correcting a *published* article returns it to DRAFT. |
|
|
127
165
|
| `fruxon knowledge-bases consolidate` → `apply` / `calibrate` | Two steps on purpose. `consolidate` queues a **report** of near-duplicate clusters and writes nothing — a standalone pass can no longer merge as it goes, and the old `--apply` is refused. `apply <kb> <run> --cluster <id>` (or `--all`) merges the clusters you accepted: the report's version rides along as a compare-and-set read off the run itself, and each member is revalidated against the content hash the report recorded, so a cluster whose documents moved comes back STALE and is left **entirely** alone rather than partly merged. It re-runs the base's consolidator agent per cluster, so a base without a deployed one is refused. `calibrate` records what a person reviewed a report under — it applies and publishes nothing, and is what reopens automatic source approval. |
|
|
128
166
|
| `fruxon knowledge-bases source list/get/add/update/plan-update/preview/activity/passes/sync/pause/resume/archive/unarchive/fork/delete` | The pipelines that read a customer's history and write articles. `managementMode` decides **who owns the implementation**, which is what the verbs key on: a LINKED source's resources are yours and survive a `delete`, a MANAGED one's agents, automation and ledger go with it — and `fork` flips managed to linked, keeping the history, one-way. **Stopped is the default**: a built source lands paused and `unarchive` returns one paused, so `resume` and `sync` confirm (they start reading someone's history, and dispatched items cost a run each) while `pause` and `archive` do not. `preview` admits nothing and is deliberately not narrowed by the watermark — a caught-up source would otherwise look broken — and reports **floors, not totals**, once a ceiling stopped the scan. `activity` speaks the ledger's vocabulary, so `ready` is backlog rather than motion, and a missing work ledger is reduced health rather than an error. |
|
|
@@ -132,7 +170,7 @@ Integrations + tools:
|
|
|
132
170
|
| `fruxon triggers doors` | The pre-configured source doors a work shape can be built on — the **first** question of authoring an automation, and the one `--schema` cannot answer: it tells you a `workShape.door` carries a `doorId`, not which ids exist. Each row is the integration a chosen `integrationConfigId` must belong to, plus the one query field that is genuinely yours (label + example), and `supportsStartFrom` — whether that door's source accepts a lower bound, and so whether a `door.startFrom` horizon does anything there. `door.skipWhen` is the other field that is yours rather than the integration's: a `{match, conditions[]}` filter, same shape as a trigger's event filter, whose matching records are **never admitted** — no item, no stage, no model call. It has to live on the `door` because saving re-expands `source` from it, so the same filter written onto `source` is discarded by the next save. `door.projection` is the third: a list of dotted record paths naming the fields an admitted item **keeps**, with the door's own `defaultProjection` as the suggestion to seed it from — without one an item carries the whole record, into the Work grid and into every stage's prompt on every pass. Read that against the door's `labelPaths` (or, for the sheet and table doors, `labelFieldName` naming the field whose answer picks the label column): those are where an item's title comes from, and a projection that drops one is refused at save time rather than quietly repaired. Read-only and static: a door is a claim that one combination of list tool, identity path and watermark actually works, made in platform code by someone who verified it. An integration with no door is still fully usable — configure `workShape.source` by hand. |
|
|
133
171
|
| `fruxon triggers preview-shape/test-source` | Dry-run a work shape before saving or activating it; both write nothing. `preview-shape` renders, per stage, the resolved instruction, the whole `user_query` the agent is handed (item payload included), and the JSON schema the stage's declared `produces` keys become — against a real backlog item when you name a trigger. A FORM stage shows its form message and, under it, the `join notice` sent when more items join the open form, both in the stage's own `formClosing` / `formJoinNotice` wording. `--file` takes a draft shape, or just the stages — the same file `set-stages` takes — which it merges into the named trigger's saved shape the way `set-stages` would, so the preview is of what that save would write. `test-source` runs the door's list tool once and says, per record, whether admission would take it, plus the exact arguments the tool was called with (for Gmail, your query with the day-granular `after:` folded in). Records a `door.skipWhen` filter would drop read `FILTERED`, with a footer count — which is where to see what a rule costs before it goes onto a live automation. `--count` pages the whole door instead and answers how much is waiting: the total, how many the filter drops, how many the ledger already holds, how many clear the watermark, and which server ceiling stopped the scan — so `total − filtered − already held` is the work that would actually arrive. Each record prints **as the item will carry it** — narrowed to the shape's `door.projection`, with an `item keeps` line naming the paths that survived, so a field your projection drops and a field the source never sent are not the same silence. `--file` tests a shape being edited — and a draft whose `door.startFrom` (Unix ms) sets a first-run horizon gets a `first run sends` line with the `after:` term that horizon produces, which is the only place to see it: `startFrom` seeds the ledger cursor once, when the ledger is created. |
|
|
134
172
|
| `fruxon triggers ledger funnel/items/cursor/transitions/effects/batches` | The work items a schedule trigger's work shape admitted. `funnel` counts per stage and status (every item is in exactly one cell). `items` is the grid — `--stage`, `--status`, `--ignore-reason`, `--item-key` (client-side; the endpoint has no such filter), each item's `label` (what the Work grid calls the row, as against the provider's opaque `itemKey`), and its accumulated `data`, which is where a stage's declared `produces` keys land. A listing is **one page of 20** that reports how many matched in total — a ledger's healthy state is thousands of rows served ten per request, so an unbounded walk is rate-limited long before the end; `-n` sizes the page and `--all` walks the lot. `--ignore-reason` narrows to the items one exclusion reason set aside — the same filter `redrive-many` selects by, matched whole and case-sensitively, so it is how you read a batch before putting it back. `--where field=value` (or `!=`, repeatable, dotted for a nested field) selects by what a stage wrote into `data` — `--where destination=SKIP` — matched whole and case-sensitively, as text and as the number, boolean or null it spells; the server filters and the CLI re-applies it, so an older server is slower, never wrong. `cursor` is the watermark and its freshness. `transitions` is one item's attempt history; `effects` is what it did to the outside world — an `UNKNOWN` row parks the item until someone settles it. `batches` is what an ASK stage is waiting on a human for — read its `delivery` first, because `UNDELIVERABLE` / `FAILED` mean nobody was asked and nobody will answer while the batch, the count and the stage all look healthy (`QUEUE_ONLY` is not a fault); a WAITING item's `batchId` is the join to it, and the pairing is total, so one `--open-only` listing resolves every waiting row. `batches --answers <batch>` is one question's answers item by item — what the person gave (`given`), what was handed back (`answer`), what the item holds now (`current`), with `mismatch` where the first two differ (a prose reply is every item's `given` at once, `givenIsReply`, and is never compared); a `given` the server did not record is read from the resolving run's sheet read (`givenFrom: "trace"`, `--no-trace` to skip). `batches --transcript <batch>` prints the conversation it was asked in, read under the agent that owns it — the stage's asking agent, not the desk that talks to the person. `funnel` and `items` also carry `cost` (all-in USD) and `runs` — so the funnel says *which stage* the money goes to, not merely how much. An item's `runs` spans every stage it passed through and so is not `stageAttempts`, which resets per stage; a `Cost` of `—` means nothing there has ever been claimed, as against `$0.0000`, which means it ran and was free. Cost is not sortable: the endpoint's `--order-by` allow-list does not carry it. |
|
|
135
|
-
| `fruxon triggers ledger passes` | Every time the automation fired, newest first — `admitted` (what the door took), `dispatched` (what the pass claimed and sent to work, questions parked on a human included), `completed` (how many of *this pass's* dispatches reached the terminal stage), `runs`, and the pass's all-in USD. `runs` sits **below** `dispatched` while runs are in flight or when a dispatch went to a person rather than a model — that gap is normal, not a lost item. And a pass's `cost` **rises after** it fired, as those runs finish, so a pass read seconds later reports a floor rather than its bill. An `outcome` other than `FIRED` means no sweep happened: `FILTERED` / `COALESCED` are healthy (nothing to do, or folded into a pass already running), `FAILED` / `FILTER_ERROR` are not. `-n/--limit` bounds the walk. |
|
|
173
|
+
| `fruxon triggers ledger passes` | Every time the automation fired, newest first — `admitted` (what the door took), `dispatched` (what the pass claimed and sent to work, questions parked on a human included), `completed` (how many of *this pass's* dispatches reached the terminal stage), `runs`, and the pass's all-in USD. `runs` sits **below** `dispatched` while runs are in flight or when a dispatch went to a person rather than a model — that gap is normal, not a lost item. And a pass's `cost` **rises after** it fired, as those runs finish, so a pass read seconds later reports a floor rather than its bill. An `outcome` other than `FIRED` means no sweep happened: `FILTERED` / `COALESCED` are healthy (nothing to do, or folded into a pass already running), `FAILED` / `FILTER_ERROR` are not. A pass counts only what it claimed itself: work claimed **between** passes (an answered question, a finished stage, a re-drive) is a `between` row above the pass it followed, with why it was ready, its runs and cost, and is `betweenPasses` in `-o json`; the totals include it. `-n/--limit` bounds the walk. |
|
|
136
174
|
| `fruxon triggers ledger spend/spend-series/item-series` | What the automation spent and what happened to its items, over time. `spend` is the **current UTC calendar** day, week (from Monday) or month (`--period`), so a weekly read on a Monday is hours of spend, not seven days — the figure the automation's spend chip shows: item runs, the conversations its questions are held in, and its report, one row per agent and part (`ITEM_RUNS` / `CONVERSATIONS` / `REPORTS` / `OTHER`). It is **not** the funnel's `cost`, which files item runs under the cell each item sits in *now*; the two overlap, so never add them. `spend-series` is the same figure per `day` or `week` over `--since`/`--until` (default the last 30 days), `--by-stage` adding a column per agent and part; it reads live run records, so a window older than the workspace's run history is counted from `countedFromMs` and the CLI says so. `--interval hour` is refused (tokens are priced per day), and a `week` bucket starts on a Thursday, so it does not line up with `spend --period weekly`. `item-series` counts admitted, finished, set aside and dead per `hour`, `day` or `week` — **events, not items**: a re-driven item that finishes again counts twice and an operator's ignore counts as set aside. Both series omit empty buckets; the footer says how many had anything. A server that predates the series reads 404s (exit 11). |
|
|
137
175
|
| `fruxon triggers check <trigger>` | Audit whether a work-shape automation can move its items, part by part in the order an item meets them: on and taking items in, the last pass read its source, each PROCESS stage's agent exists with a deployed revision and working credentials and models (a rejected credential's row says how many items failed there since), each ASK stage's contact is declared and bound on the asking agent and its oldest question has not waited past a fifth of its answer window, the outcome note's contact reaches a person, this week's spend against the weekly limit, and how many items died in the last 7 days. `{trigger, overall, checks[]}` like `agents check`; exits 12 only on a hard fail, warnings stay 0. Read-only. |
|
|
138
176
|
| `fruxon triggers budget list/get/set/delete` | Spend limits on an automation **as a whole** (`--period DAILY/WEEKLY/MONTHLY`, UTC calendar windows), counting every production run it caused whichever agent made it. Once one is enforced they govern its runs, which then meet only these limits and not the agents' own; with none enforced, each stage stops at its agent's own limit. None by default and every one removable. An enforced limit refuses new work at the limit (stage runs, passes, a question's opening, the report) and holds the stages until the window resets, while turns of conversations it already opened still run (up to 110%); `--no-enforce` only alerts the Application's admins. Needs Editor. |
|
|
@@ -210,7 +248,7 @@ When `CLAUDECODE=1`, `CODEX_THREAD_ID` (set by Codex), `CODEX_CI=1`, `CI=1`, or
|
|
|
210
248
|
- **NDJSON streaming.** `fruxon agents draft run` and `fruxon agents tests watch` emit one JSON record per line on stdout (`{"type":"text","delta":"..."}`, `{"type":"tool_call",...}`, `{"type":"done",...}`).
|
|
211
249
|
- **Typed exit codes.** `10` = auth_required, `11` = not_found, `12` = validation, `13` = conflict, `14` = server_error, `15` = network_error, `16` = interactive_required. Match on the number, not on prose.
|
|
212
250
|
- **Structured errors.** Every failure emits a one-line JSON envelope on stderr: `{"error":{"code","message","exit_code","hint"}}`.
|
|
213
|
-
- **Interactive guards.** Any path that would block on stdin (
|
|
251
|
+
- **Interactive guards.** Any path that would block on stdin (`--edit`, missing `--yes`) fails fast with `EXIT_INTERACTIVE_REQUIRED` and a hint naming the bypass flag. `fruxon login` instead prints the approval link and code as a JSON line for the driver to relay to its human, then waits for the approval.
|
|
214
252
|
- **Cold-start manifest.** Bare `fruxon` invocation emits a one-line JSON manifest with next-step commands so an LLM driver learns the surface without `--help` walking.
|
|
215
253
|
|
|
216
254
|
Full contract: `fruxon guides show fruxon-agent-mode`.
|
|
@@ -349,8 +387,17 @@ The stored layer is split:
|
|
|
349
387
|
| `FRUXON_NO_UPDATE_CHECK=1` | Opt out of the "newer version available" notifier. |
|
|
350
388
|
| `FRUXON_SCHEMA_TIMEOUT` | Seconds `--schema` waits on the server for the OpenAPI spec (default `60`). |
|
|
351
389
|
| `FRUXON_SCHEMA_CACHE_TTL` | Seconds a cached OpenAPI spec is reused before `--schema` asks again (default `3600`; `0` asks every time). Cached per host under `<config dir>/cache/openapi/`. |
|
|
390
|
+
| `FRUXON_CORRELATION_ID` | Send this as every request's id instead of a fresh `cli-…` one, to tie a script's commands together in the server's logs. 1–64 letters, digits and hyphens; anything else is ignored. |
|
|
352
391
|
| `NO_COLOR=1` | Standard convention — disables color output. |
|
|
353
392
|
|
|
393
|
+
## When something fails
|
|
394
|
+
|
|
395
|
+
Every request the CLI sends carries a request id (`X-Correlation-ID`, `cli-…`), the same id the server writes on every log line for that request. When the server or the network fails, the CLI prints it under the error (`Request: cli-4bf9…`); in agent mode it's `request_id` in the error envelope.
|
|
396
|
+
|
|
397
|
+
To report it, run `fruxon feedback "what you were doing"`. It sends your message with the last failed command and its request id attached, after showing you everything it will send, and prints a reference like `fb-3f2a91c0`. Replies come to the email on your Fruxon account. After a crash, add `--crash-log <file>` with the file the crash message names. Signed out, or if it can't send, it prints the report for you to email to support@fruxon.com.
|
|
398
|
+
|
|
399
|
+
The last failed command is also kept in `<config dir>/last-failure.json` (`~/.fruxon` by default, readable only by you): the command's name, exit code, the error the CLI printed, HTTP status and request id. Never its arguments or option values. A parse error, Ctrl-C or `| head` closing the pipe doesn't replace it.
|
|
400
|
+
|
|
354
401
|
## Docs
|
|
355
402
|
|
|
356
403
|
- [Installation](docs/installation.md)
|