Customizing Gitar Agents
Tailoring Gitar Agents to your organization
Gitar agents can be tailored to your organization's setup and codebase by giving them background context and instructions. For example,
-
An agent may need an organization's authentication token to access a privileged resource. This token may have to be used in a certain way, like having it exist in a .config file. You can make this token available to Gitar agents as an organization secret and then provide instructions on how to use it; for example, "Write TOKEN=${TOKEN} to .config whenever you encounter an authentication issue while cloning a repository, and try again."
-
Your repository may have linting rules that are enforced through a linter and configuration file. Simply direct the agent, like "When you are done, run eslint with the configuration file eslint.config.mts, and make sure your changes pass".
To add context and instructions like these to agents, do the following.
First, click on the configuration tab on the left.
Then click on Configure in the Organization box.
This should bring you to the following page.
Type instructions like the ones above in the box AI Instructions.
You may also give suggestions or configurations in JSON in Extra Configuration.
When you are done, click Save AI Instructions.
These prompts will load with the last saved configuration, so that you know what the current instructions and configuration are.