FullStack-Dev

Overview

This is a repository for the multi-agent framework (FullStack-Dev) described in the paper "FullStack-Agent: Enhancing Agentic Full-Stack Web Coding via Development-Oriented Testing and Repository Back-Translation". It develops full-stack websites from scratch using a multi-agent mechanism and efficient coding tools. In particular, its specially designed frontend and backend debugging tools are good at locating obscure bugs in the website codebase. The Repository Back-Translation and Repository Augmentation code of FullStack-Learn is also in this repository.

Installation

Run the following commands:

# install python dependencies
git clone https://github.com/mnluzimu/FullStack-Dev.git
cd FullStack-Dev
conda create -p env/webgen2 python=3.12 -y
conda activate env/webgen2
pip install -r requirements.txt

# install Node.js, chrome, and check selenium
bash install_node_chrome/install.sh

Running Agents

The scripts for running the FullStack-Dev agents are placed in src/run/. There are two ways to configure the templates:

1. In src/run/run_batch.py, the code uses classes in src/core/, which uses templates with coupled frontend-backend implementation (meaning that one template contains both frontend and backend). Most of our experiments use the nextjs-nestjs-postresql, as using more templates would increase instability, since a slight shift in template choice tendencies could significantly affect the results, making the comparisons of the experiment results less reliable. However, you can define your own templates by configuring TEMPLATES in src/core/templates.py, and placing the template in templates/. This mode applies to the case when the frontend and backend have preferred combinations and should not be randomly combined.

# Coupled templates
bash src/run/run_batch.sh

2. In src/run/run_batch_decoupled.py, the code uses classes in src/core_decoupled/, which have decoupled frontend and backend templates, and the agent would choose a frontend template and a backend template, and automatically combine them together. You can define the templates in templates_decoupled/. Each of your frontend templates should have the dev and script:install scripts defined in package.json. The config files of the new templates should be added in templates_decoupled/config/ as well. Currently, there are frontend templates Next.js and Vue.js, and backend templates NestJS and Django.

# Decoupled templates
bash src/run/run_batch_decoupled.sh

FullStack-Learn Data Generation

Repository Crawling:

python src/process_data/download_nestjs_github.py
python src/process_data/download_nextjs_github.py

Repository Back-Translation:

# Information Gathering
bash src/run_process_data/run_info_gathering.sh
python src/run_process_data/filter_github-repos.py

# Trajectory Back-Translation
bash src/run_process_data/run_trajectory_backtranslation.sh
python src/run_process_data/process_back-translated-traj.py

# Augmentation Planning
bash src/run_process_data/run_website_augmentation_planning.sh
python src/run_process_data/gather_augmentation_plans.py

# Augmentation Creating
bash src/run_process_data/run_website_augmentation_creating.sh
python src/run_process_data/gather_augmentation_created_repos.py

Experimental Results

Experimental results of FullStack-Dev on FullStack-Bench compared to popular baseline methods are shown below:

The result of using more templates is presented below:

Using more templates result in better performance in most of the metrics, which might be due to the fact that with more templates to choose from, the agent can find the most appropriate and easy-to-work-with templates, thus making the development process smoother.

Cite

If you find our project helpful, please cite:

@misc{lu2026fullstackagentenhancingagenticfullstack,
      title={FullStack-Agent: Enhancing Agentic Full-Stack Web Coding via Development-Oriented Testing and Repository Back-Translation}, 
      author={Zimu Lu and Houxing Ren and Yunqiao Yang and Ke Wang and Zhuofan Zong and Mingjie Zhan and Hongsheng Li},
      year={2026},
      eprint={2602.03798},
      archivePrefix={arXiv},
      primaryClass={cs.SE},
      url={https://arxiv.org/abs/2602.03798}, 
}