Skip to content
Film and getting started

Choose the context for a Giljo HQ project

Watch how Giljo HQ gives your agent the background it needs before planning a change, and where you control what is included. Product information, tech stack, architecture, testing and depth settings.

1 minute 36 seconds ยท Animated walkthrough

Give agents the right context in Giljo HQ, then decide how much of it they start with. This short film shows what Giljo HQ can tell your agent about the product before it plans a change, and where you control it.

Your coding tool and model do the thinking. Giljo HQ, a structured workspace for AI software builders, stores the background and hands it to the agent when a project is staged. You decide what is true about your product and how much of it to include.

What the film covers

The film follows one small feature in a hiking app, searching for trails by name. Before an agent can plan that, it needs to know who the app is for, how it is built and which rules already matter.

Giljo HQ keeps that background with the product:

  • Product information describes what you are building.
  • Tech stack names the tools and frameworks.
  • Architecture explains how the parts fit together.
  • Testing records how you expect changes to be checked.

Alongside those, 360 Memory holds recorded project experience, and Git history can supply recent code changes when Git integration is enabled.

Always on, and what you can switch off

During staging, this context helps the orchestrator prepare the mission and the work assignments. Context Settings shape that starting brief.

Product information and the project description are always included. Tech stack, architecture and testing are toggles. Turning one off does not delete its records; it only leaves them out of the brief for that project.

Depth settings

Three controls change how much arrives:

  • Vision documents at 33, 66 or 100 percent.
  • 360 Memory from the last 1, 3, 5 or 10 projects.
  • Git history from 5 to 100 commits, when Git integration is on.

A shorter brief is only useful if it still tells the agent what matters. If the agent needs more, it can ask for it.

Keep the product information current

The context is only as good as what you put in it. When the stored description drifts from the real code, the plan starts from something that is no longer true.

Giljo HQ helps with that. You can generate a tuning prompt from the product card, and the agent compares the context with the codebase and applies only the changes you approve. Every ten finished projects, a banner offers a review and shows how many projects have passed since the context was last updated.

Our guide to giving an agent the right context covers what belongs in that description, what does not, and how to spot it going stale.