Giljo HQ workflow: the movie. Grab a snack.
This seven-and-a-half-minute film follows one change: adding search to an app. See how product background becomes a project, how your connected agents prepare the plan, and where you give the go-ahead. Then follow the work through to the changes and checks you review.
You have a piece of software to build, an AI coding tool, and a change you want to make. What needs to happen between asking for that change and reviewing the result?
This film follows the basic Giljo HQ workflow using one example: adding search to an app. It starts with the product's background, turns the request into a project, and follows the plan, agent assignments, your go-ahead, and the record left for review.
Bring your starting point
You might already have an app, a written proposal, or an idea you want to develop. The starting point changes what you give your connected agent to work from. The aim is the same: establish what the product is, what matters to it, and which guidelines the work should follow.
In Giljo HQ, the product is the home for that background. A project describes a particular piece of work within it. Your app is the product; adding search is the project.
Make the request specific
“Add search” sounds clear until you start asking questions. What should it search? How should results appear? What happens when nothing matches?
The film uses those questions to show what belongs in a project. Product context supplies the broader design and coding guidelines. The project supplies the expectations for this change, including how you will judge whether it is finished.
Review the plan before work starts
The lead agent in your coding tool takes the orchestrator role. It reads the request and relevant background, prepares an approach called the mission, and sets out jobs for the roles needed.
Getting that plan and those assignments ready is staging. It is not permission to start building. You can review the approach, ask for changes, and give the go-ahead when you are ready.
Your coding tools still do the engineering. Giljo HQ is an MCP server with a visual dashboard: a shared place those connected tools can read and update, not a replacement model running the work itself.
Follow the work and review the record
As agents report progress, you can follow their jobs, reported steps and questions in the dashboard. When they finish, compare the requested work with the changes and checks they report.
The work record provides somewhere to look through recorded messages, decisions and attached Git commits. Key outcomes and decisions are carried forward in 360 Memory; that summary is not the same as the complete project record.
You still decide whether the result meets your expectations. A reported test result is something to review, not a substitute for that decision.
What this film covers
This is an animated explanation of the workflow, not a recording of a live project or a click-by-click installation guide. The search feature is an illustrative example, not a claim about a completed customer project.
Use it to see how the pieces fit together: product background, a clear request, a staged plan, your go-ahead, and a record to review before the next piece of work.