Blaze Engineer is a developer-focused automation platform that automates the steps between the Coding Task Is Defined And Ready To Be Started step to the Coding Task Is Pushed And Ready For Code Review step.

Automate code tasks by triggering AI code jobs.

Automate triggering CI/CD operations after coding jobs finish via Webhook.

All through simple API calls.

Integrate with any Git provider. Run from anywhere.
Simple API. Secure. Flexible. Fast.
What Is Blaze Engineer? Overview and core features of Blaze Engineer Getting Started Guide Step-by-step guide to your first Blaze Engineer job API Documentation All endpoints, requests, and response details API Playground Test the Blaze Engineer API directly from your browser Writing Good Tasks Guide How to write effective tasks for Blaze Engineer Jobs 2 Week Roadmap Upcoming improvements and features (15 Aug → 30 Aug) Node.js Client Library (GitHub) Source code & usage for Node.js integration Node.js Client Library (NPM) Installable NPM package for Node.js apps Interactive Node.js CLI Tool (GitHub) Source code & usage for the interactive CLI tool Interactive Node.js CLI Tool (NPM) Installable NPM package for the Blaze Engineer CLI tool

What is Blaze Engineer?

Blaze Engineer is an automated coding API designed to handle code changes using simple task definitions.

Blaze Engineer excels at:
  1. Creating brand-new projects from scratch.
  2. Adding new features to an existing codebase.
  3. Modifying existing features for enhancements or bug fixes.
  4. Refactoring entire repositories for style, structure, or technology upgrades.
It can: How it works:
  1. Clones the repository and branch the task is targeting.
  2. Analyzes the entire cloned codebase.
  3. Analyzes the provided task definition to understand your intent.
  4. Determines the required context needed to execute the task based on its review.
  5. Generates or updates files, copies, moves, or deletes files as needed to accomplish the requested change.
  6. Generates a commit message summarizing all changes.
  7. Commits and pushes the changes with the generated commit message.
Blaze Engineer can handle the following file operations:
Give Blaze Engineer a precise mission—whether starting a new project, adding features, or a full repository refactor—and it will handle the heavy lifting: project scaffolding, file generation, and even large-scale codebase changes. Everything is driven by your task definition.
Example (Task Defined -> Task Deployed) Automation Flow Chart:

(Go To Top Of Page)

2 Week Roadmap

Upcoming improvements and features (15 Aug → 30 Aug)
  1. Improve jobs/run API Endpoint Phases. Completed DEPLOYED
    1. Make all phases even smarter from using gathered test results from tons of testing.
    2. Add review and maybe rerun check step for certain job phase actions to catch and resolve inner job issues and self-correct. Increasing the already high success rate of a job.
  2. Add Job Types. Completed DEPLOYED
    Right now jobs/run only has one job type. Which is the Coding type. It will now also have the Question type. The Coding type will be the default if the type field is excluded.

    A Question type job will run all the job phases required to give a very detailed answer using the context of the code base. Then will attach the answer to the job document, then trigger the Webhook with the status being completed.
  3. Add Code Review Phase for jobs/run API Endpoint. Completed DEPLOYED
    1. Add Code Review flag on the jobs/run Endpoint. Allow the job to pause, attach the changes to the job document, and trigger the Webhook with the status being codeReview. This gives the user the chance to request to review the changes before they are applied.
    2. Add jobs/codeReview Endpoint that the user can send the jobID and isApproved field values to. If approved it will apply the code changes, commit and push, and trigger the Webhook with the status being completed. If disapproved it will mark the status failedCodeReview and trigger the Webhook with the status being failedCodeReview.
  4. Add Job Runner Web Client UI. Implementing IMPLEMENTING
    This will provide users a quick way to run jobs with the code review flag enabled so they get a chance to review changes before applying the changes for each job.

    It will display the new/modified/removed files in a Beautiful Code Viewer/Diff Checker UI.

    The user will select an already defined repository and branch, then they can type messages in a chat style UI and each message will be a new job. The user will only be able to have one active job at a time. The user must approve/disapprove the code review for a previous Coding Type Job before they can run another job.

    Imagine Vibe Coding using an AI Chat Application but without having to copy and paste the generated new file/modified file content over yourself, and without having to run other file operations yourself like rename, move, and remove. That is what the Blaze Engineer - Job Runner Web Client UI will provide.
(Go To Top Of Page)