feat(agent/command): Add Create Command ability powered by Codex

[Swiftyos]

Background

This PR adds a demo of using Codex, AutoGPT's code generation system, to write new commands for AutoGPT. The purpose is to showcase the capability of generating custom commands and extending AutoGPT's functionality.

Changes 🏗️

• Added an CreateCommandComponent
• Integrated the CreateCommandComponent into AutoGPT's command system.
• TODO: Link it to codex
• TODO: Added the ability to add the generated code as a new component of autogpt
• TODO: Add a new env var for the base url of codex

PR Quality Scorecard ✨

• Have you used the PR description template?   +2 pts
• Is your pull request atomic, focusing on a single change?   +5 pts
• Have you linked the GitHub issue(s) that this PR addresses?   +5 pts
• Have you documented your changes clearly and comprehensively?   +5 pts
• Have you changed or added a feature?   -4 pts
  • Have you added/updated corresponding documentation?   +4 pts
  • Have you added/updated corresponding integration tests?   +5 pts
• Have you changed the behavior of AutoGPT?   -5 pts
  • Have you also run agbenchmark to verify that these changes do not regress performance?   +10 pts

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	5276623
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/6643789dc40e1f000842bb0f

[codecov]

Codecov Report

Attention: Patch coverage is 83.33333% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 44.79%. Comparing base (4f81246) to head (2c86ada).
Report is 1 commits behind head on master.

❗ Current head 2c86ada differs from pull request most recent head 5276623. Consider uploading reports for the commit 5276623 to get more accurate results

Files	Patch %	Lines
...utogpts/autogpt/autogpt/commands/create_command.py	81.25%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7141      +/-   ##
==========================================
+ Coverage   44.68%   44.79%   +0.10%     
==========================================
  Files         133      134       +1     
  Lines        6315     6333      +18     
  Branches      823      823              
==========================================
+ Hits         2822     2837      +15     
- Misses       3382     3385       +3     
  Partials      111      111              

Flag	Coverage Δ
Linux	44.71% <83.33%> (+0.11%)	⬆️
Windows	42.88% <83.33%> (+0.11%)	⬆️
autogpt-agent	44.76% <83.33%> (+0.10%)	⬆️
macOS	44.10% <83.33%> (+0.11%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[codiumai-pr-agent-pro]

CI Failure Feedback 🧐

(Checks updated until commit 5276623)

Action: test (3.10, windows)

Failed stage: Install Python dependencies [❌]

Failure summary: The action failed because the pyproject.toml file has changed significantly since the last time the poetry.lock file was generated. This discrepancy caused the dependency installation process to fail, requiring a regeneration of the lock file using the poetry lock [--no-update] command.

Relevant error logs: 1: ##[group]Operating System 2: Microsoft Windows Server 2022 ... 298: PKG_CONFIG_PATH: C:\hostedtoolcache\windows\Python\3.10.11\x64/lib/pkgconfig 299: Python_ROOT_DIR: C:\hostedtoolcache\windows\Python\3.10.11\x64 300: Python2_ROOT_DIR: C:\hostedtoolcache\windows\Python\3.10.11\x64 301: Python3_ROOT_DIR: C:\hostedtoolcache\windows\Python\3.10.11\x64 302: ##[endgroup] 303: Creating virtualenv agpt-bO72ey-r-py3.10 in C:\Users\runneradmin\AppData\Local\pypoetry\Cache\virtualenvs 304: Installing dependencies from lock file 305: pyproject.toml changed significantly since poetry.lock was last generated. Run `poetry lock [--no-update]` to fix the lock file. 306: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.