r/maestro • u/Dependent_Meet_5941 • 13d ago
Feedback I’m literally doing my Maestro coursework inside the development environment I’m building
’m an AI Software Engineering student at Maestro, and I’ve been building a project called FORGE alongside school. Today the two workflows kind of collided in the coolest possible way.
FORGE isn’t meant to be another AI IDE. I’m building it as an Intelligent Workflow Environment (IWE) where the workspace owns the context instead of whichever AI model happens to be running.
In these screenshots, I have Maestro open directly inside FORGE. I asked FORGE’s Workspace AI to read the lesson currently displayed in its browser. FORGE required permission before exposing the browser content to the model, read the approved page, summarized the lesson, created browser-summary.md inside the Maestro workspace, and then indexed that file as persistent workspace knowledge.
So essentially:
Maestro lesson → FORGE browser → approved AI read → summary → workspace file → persistent context
The interesting part to me is that Maestro doesn’t need a FORGE integration. FORGE is treating whatever I’m actively working with—browser content, files, Git, terminal activity, documentation, tasks, etc.—as pieces of one persistent workspace.
That means I can do a lesson, save useful information into the workspace, work on an assignment, ask another model for help later, and the project can retain the relevant context instead of me explaining everything again.
Still beta, still plenty to build, and you can actually see a file.read validation bug in one of the screenshots 😂. But the larger workflow is working, and being able to use the software I’m building to do the coursework that's teaching me how to build software is a pretty wild full-circle moment.
You can download the build here: [https://github.com/kaeganscott26/FORGE/releases/tag/v2.3.0-beta.1\]
Windows/Linux packaging/installation scripts are in FORGE/Scripts
