Bumps the development-dependencies group with 3 updates in the /autogpt_platform/frontend directory: [@storybook/test-runner](https://github.com/storybookjs/test-runner), [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) and [msw](https://github.com/mswjs/msw). Updates `@storybook/test-runner` from 0.21.3 to 0.22.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/storybookjs/test-runner/releases"><code>@storybook/test-runner</code>'s releases</a>.</em></p> <blockquote> <h2>v0.22.0</h2> <h4>🚀 Enhancement</h4> <ul> <li>Release v0.22.0 <a href="https://redirect.github.com/storybookjs/test-runner/pull/553">#553</a> (<a href="https://github.com/ronakj"><code>@ronakj</code></a> <a href="https://github.com/ndelangen"><code>@ndelangen</code></a> <a href="https://github.com/kasperpeulen"><code>@kasperpeulen</code></a> <a href="https://github.com/yannbf"><code>@yannbf</code></a>)</li> <li>Dependencies: Add sb9 alpha compatibility <a href="https://redirect.github.com/storybookjs/test-runner/pull/551">#551</a> (<a href="https://github.com/ndelangen"><code>@ndelangen</code></a>)</li> </ul> <h4>🐛 Bug Fix</h4> <ul> <li>Exclude new server component error <a href="https://redirect.github.com/storybookjs/test-runner/pull/552">#552</a> (<a href="https://github.com/kasperpeulen"><code>@kasperpeulen</code></a>)</li> </ul> <h4>Authors: 4</h4> <ul> <li>Kasper Peulen (<a href="https://github.com/kasperpeulen"><code>@kasperpeulen</code></a>)</li> <li>Norbert de Langen (<a href="https://github.com/ndelangen"><code>@ndelangen</code></a>)</li> <li>Ronak Jain (<a href="https://github.com/ronakj"><code>@ronakj</code></a>)</li> <li>Yann Braga (<a href="https://github.com/yannbf"><code>@yannbf</code></a>)</li> </ul> <h2>v0.22.0-next.2</h2> <h4>🐛 Bug Fix</h4> <h4>Authors: 1</h4> <ul> <li>Ronak Jain (<a href="https://github.com/ronakj"><code>@ronakj</code></a>)</li> </ul> <h2>v0.22.0-next.0</h2> <h4>🚀 Enhancement</h4> <ul> <li>Dependencies: Add sb9 alpha compatibility <a href="https://redirect.github.com/storybookjs/test-runner/pull/551">#551</a> (<a href="https://github.com/ndelangen"><code>@ndelangen</code></a>)</li> </ul> <h4>Authors: 1</h4> <ul> <li>Norbert de Langen (<a href="https://github.com/ndelangen"><code>@ndelangen</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/storybookjs/test-runner/blob/v0.22.0/CHANGELOG.md"><code>@storybook/test-runner</code>'s changelog</a>.</em></p> <blockquote> <h1>v0.22.0 (Fri Feb 28 2025)</h1> <h4>🚀 Enhancement</h4> <ul> <li>Release v0.22.0 <a href="https://redirect.github.com/storybookjs/test-runner/pull/553">#553</a> (<a href="https://github.com/ronakj"><code>@ronakj</code></a> <a href="https://github.com/ndelangen"><code>@ndelangen</code></a> <a href="https://github.com/kasperpeulen"><code>@kasperpeulen</code></a> <a href="https://github.com/yannbf"><code>@yannbf</code></a>)</li> <li>Dependencies: Add sb9 alpha compatibility <a href="https://redirect.github.com/storybookjs/test-runner/pull/551">#551</a> (<a href="https://github.com/ndelangen"><code>@ndelangen</code></a>)</li> </ul> <h4>🐛 Bug Fix</h4> <ul> <li>Exclude new server component error <a href="https://redirect.github.com/storybookjs/test-runner/pull/552">#552</a> (<a href="https://github.com/kasperpeulen"><code>@kasperpeulen</code></a>)</li> </ul> <h4>Authors: 4</h4> <ul> <li>Kasper Peulen (<a href="https://github.com/kasperpeulen"><code>@kasperpeulen</code></a>)</li> <li>Norbert de Langen (<a href="https://github.com/ndelangen"><code>@ndelangen</code></a>)</li> <li>Ronak Jain (<a href="https://github.com/ronakj"><code>@ronakj</code></a>)</li> <li>Yann Braga (<a href="https://github.com/yannbf"><code>@yannbf</code></a>)</li> </ul> <hr /> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="d56dba2c40"><code>d56dba2</code></a> Bump version to: 0.22.0 [skip ci]</li> <li><a href="3b1a12284f"><code>3b1a122</code></a> Update CHANGELOG.md [skip ci]</li> <li><a href="a595bb8cf5"><code>a595bb8</code></a> Merge pull request <a href="https://redirect.github.com/storybookjs/test-runner/issues/553">#553</a> from storybookjs/release/v0.22.0</li> <li><a href="16a7aa8f02"><code>16a7aa8</code></a> Merge branch 'main' into release/v0.22.0</li> <li><a href="b24a54faa4"><code>b24a54f</code></a> Merge pull request <a href="https://redirect.github.com/storybookjs/test-runner/issues/539">#539</a> from ronakj/next</li> <li><a href="7b78185656"><code>7b78185</code></a> Merge pull request <a href="https://redirect.github.com/storybookjs/test-runner/issues/552">#552</a> from storybookjs/kasper/fix-next-error</li> <li><a href="91cf68d17c"><code>91cf68d</code></a> Exclude new server component error</li> <li><a href="2d485ce6bf"><code>2d485ce</code></a> Merge pull request <a href="https://redirect.github.com/storybookjs/test-runner/issues/551">#551</a> from storybookjs/norbert/sb-9-compatibility</li> <li><a href="dfe563067c"><code>dfe5630</code></a> dedupe</li> <li><a href="859c52b4df"><code>859c52b</code></a> upgrade playwright</li> <li>Additional commits viewable in <a href="https://github.com/storybookjs/test-runner/compare/v0.21.3...v0.22.0">compare view</a></li> </ul> </details> <br /> Updates `eslint-config-next` from 15.1.6 to 15.3.3 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">eslint-config-next's releases</a>.</em></p> <blockquote> <h2>v15.3.3</h2> <blockquote> <p>[!NOTE]<br /> This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>Reinstate <code>vary</code> (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/79939">#79939</a>)</li> <li>fix(next-swc): Fix interestingness detection for React Compiler (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/79558">#79558</a>)</li> <li>fix(next-swc): Fix react compiler usefulness detector (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/79480">#79480</a>)</li> <li>fix(dev-overlay): Better handle edge-case file paths in launchEditor (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/79526">#79526</a>)</li> <li>Client router should discard stale prefetch entries for static pages (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/79362">#79362</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/gaojude"><code>@gaojude</code></a>, <a href="https://github.com/kdy1"><code>@kdy1</code></a>, <a href="https://github.com/bgw"><code>@bgw</code></a>, and <a href="https://github.com/unstubbable"><code>@unstubbable</code></a> for helping!</p> <h2>v15.3.2</h2> <blockquote> <p>[!NOTE]<br /> This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>backport: fix(turbopack): Store persistence of wrapped task on RawVc::LocalOutput (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/78488">#78488</a>) (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/78883">#78883</a>)</li> <li><code>@next/mdx</code>: Use stable turbopack config options (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/78880">#78880</a>)</li> <li>Fix react-compiler: Fix detection of interest (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/78879">#78879</a>)</li> <li>Fix turbopack: Backport sourcemap bugfix (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/78881">#78881</a>)</li> <li>[next-server] preserve rsc query for rsc redirects (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/78876">#78876</a>)</li> <li>Update middleware public/static matching (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/78875">#78875</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/ijjk"><code>@ijjk</code></a>, <a href="https://github.com/huozhi"><code>@huozhi</code></a>, <a href="https://github.com/kdy1"><code>@kdy1</code></a>, <a href="https://github.com/wbinnssmith"><code>@wbinnssmith</code></a>, and <a href="https://github.com/bgw"><code>@bgw</code></a> for helping!</p> <h2>v15.3.1</h2> <blockquote> <p>[!NOTE]<br /> This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </blockquote> <h3>Core Changes</h3> <ul> <li>chore: Backport SWC-based RC optimization (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/78260">#78260</a>)</li> <li>fix: bump image-size@1.2.1 (<a href="https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next/issues/78164">#78164</a>)</li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/kdy1"><code>@kdy1</code></a> and <a href="https://github.com/styfle"><code>@styfle</code></a> for helping!</p> <h2>v15.3.1-canary.15</h2> <h3>Core Changes</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="3ab8db7383"><code>3ab8db7</code></a> v15.3.3</li> <li><a href="d9ec4a4b57"><code>d9ec4a4</code></a> v15.3.2</li> <li><a href="fa536cf2c9"><code>fa536cf</code></a> v15.3.1</li> <li><a href="b2ff04995b"><code>b2ff049</code></a> v15.3.0</li> <li><a href="60bfe64295"><code>60bfe64</code></a> v15.3.0-canary.46</li> <li><a href="f71c4a1582"><code>f71c4a1</code></a> v15.3.0-canary.45</li> <li><a href="4451bae75d"><code>4451bae</code></a> v15.3.0-canary.44</li> <li><a href="87d7d8eb7a"><code>87d7d8e</code></a> v15.3.0-canary.43</li> <li><a href="82ab39f801"><code>82ab39f</code></a> v15.3.0-canary.42</li> <li><a href="8f1409d6ce"><code>8f1409d</code></a> v15.3.0-canary.41</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/commits/v15.3.3/packages/eslint-config-next">compare view</a></li> </ul> </details> <br /> Updates `msw` from 2.8.7 to 2.9.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mswjs/msw/releases">msw's releases</a>.</em></p> <blockquote> <h2>v2.9.0 (2025-06-03)</h2> <h3>Features</h3> <ul> <li>send <code>request</code> reference within the <code>RESPONSE</code> event (<a href="https://redirect.github.com/mswjs/msw/issues/2510">#2510</a>) (425635161dddb3457eea37b996b41b7c731fc69f) <a href="https://github.com/kettanaito"><code>@kettanaito</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="4fbc90a5ef"><code>4fbc90a</code></a> chore(release): v2.9.0</li> <li><a href="425635161d"><code>4256351</code></a> feat: send <code>request</code> reference within the <code>RESPONSE</code> event (<a href="https://redirect.github.com/mswjs/msw/issues/2510">#2510</a>)</li> <li>See full diff in <a href="https://github.com/mswjs/msw/compare/v2.8.7...v2.9.0">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
AutoGPT Platform
Welcome to the AutoGPT Platform - a powerful system for creating and running AI agents to solve business problems. This platform enables you to harness the power of artificial intelligence to automate tasks, analyze data, and generate insights for your organization.
Getting Started
Prerequisites
- Docker
- Docker Compose V2 (comes with Docker Desktop, or can be installed separately)
- Node.js & NPM (for running the frontend application)
Running the System
To run the AutoGPT Platform, follow these steps:
-
Clone this repository to your local machine and navigate to the
autogpt_platformdirectory within the repository:git clone <https://github.com/Significant-Gravitas/AutoGPT.git | git@github.com:Significant-Gravitas/AutoGPT.git> cd AutoGPT/autogpt_platform -
Run the following command:
cp .env.example .envThis command will copy the
.env.examplefile to.env. You can modify the.envfile to add your own environment variables. -
Run the following command:
docker compose up -dThis command will start all the necessary backend services defined in the
docker-compose.ymlfile in detached mode. -
Navigate to
frontendwithin theautogpt_platformdirectory:cd frontendYou will need to run your frontend application separately on your local machine.
-
Run the following command:
cp .env.example .env.localThis command will copy the
.env.examplefile to.env.localin thefrontenddirectory. You can modify the.env.localwithin this folder to add your own environment variables for the frontend application. -
Run the following command:
Enable corepack and install dependencies by running:
corepack enable pnpm iThen start the frontend application in development mode:
pnpm dev -
Open your browser and navigate to
http://localhost:3000to access the AutoGPT Platform frontend.
Docker Compose Commands
Here are some useful Docker Compose commands for managing your AutoGPT Platform:
docker compose up -d: Start the services in detached mode.docker compose stop: Stop the running services without removing them.docker compose rm: Remove stopped service containers.docker compose build: Build or rebuild services.docker compose down: Stop and remove containers, networks, and volumes.docker compose watch: Watch for changes in your services and automatically update them.
Sample Scenarios
Here are some common scenarios where you might use multiple Docker Compose commands:
-
Updating and restarting a specific service:
docker compose build api_srv docker compose up -d --no-deps api_srvThis rebuilds the
api_srvservice and restarts it without affecting other services. -
Viewing logs for troubleshooting:
docker compose logs -f api_srv ws_srvThis shows and follows the logs for both
api_srvandws_srvservices. -
Scaling a service for increased load:
docker compose up -d --scale executor=3This scales the
executorservice to 3 instances to handle increased load. -
Stopping the entire system for maintenance:
docker compose stop docker compose rm -f docker compose pull docker compose up -dThis stops all services, removes containers, pulls the latest images, and restarts the system.
-
Developing with live updates:
docker compose watchThis watches for changes in your code and automatically updates the relevant services.
-
Checking the status of services:
docker compose psThis shows the current status of all services defined in your docker-compose.yml file.
These scenarios demonstrate how to use Docker Compose commands in combination to manage your AutoGPT Platform effectively.
Persisting Data
To persist data for PostgreSQL and Redis, you can modify the docker-compose.yml file to add volumes. Here's how:
-
Open the
docker-compose.ymlfile in a text editor. -
Add volume configurations for PostgreSQL and Redis services:
services: postgres: # ... other configurations ... volumes: - postgres_data:/var/lib/postgresql/data redis: # ... other configurations ... volumes: - redis_data:/data volumes: postgres_data: redis_data: -
Save the file and run
docker compose up -dto apply the changes.
This configuration will create named volumes for PostgreSQL and Redis, ensuring that your data persists across container restarts.