Skip to content

fix(alita): preserve generated tool results with stdout logs - #256

Open
bitkira wants to merge 1 commit into
ANative-Lab:mainfrom
bitkira:fix/alita-generated-tool-output
Open

fix(alita): preserve generated tool results with stdout logs#256
bitkira wants to merge 1 commit into
ANative-Lab:mainfrom
bitkira:fix/alita-generated-tool-output

Conversation

@bitkira

@bitkira bitkira commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add a unique result marker for Alita generated tools so user stdout logs do not break result parsing
  • preserve stdout/stderr logs separately while returning the structured generated tool result
  • keep legacy full-JSON output compatibility and avoid guessing JSON from unmarked mixed output
  • add regression coverage for noisy stdout, post-result output, marker collisions, legacy JSON output, and the real Python executor

Closes #255

Tests

  • .venv/bin/python -m pytest tests/src/tools/test_alita_generated_code_tool.py -q
  • .venv/bin/python -m pytest tests/src/tools/test_alita_generated_code_tool.py tests/src/core/test_dependency_extras.py -q
  • .venv/bin/python -m ruff check evoagentx/tools/alita_agent.py tests/src/tools/test_alita_generated_code_tool.py
  • git diff --check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Alita generated tools lose structured result when code prints extra stdout

1 participant