FAQ¶
What Tasks Work Well?¶
Focused tasks with clear success criteria work best: fixing a bug, adding a small feature, updating tests, reviewing a pull request, or investigating a well-described failure. Name the repository, relevant ticket, constraints, and the checks that should pass.
Split broad projects into reviewable steps. Agentic Unit can use multiple repositories, but the prompt should explain their relationship and which repository should receive changes.
Do I Need To Review The Result?¶
Yes. Review the diff, test the result, and follow your normal pull request and approval process before merging or deploying it. Agentic Unit does not replace code ownership, security review, or change-management controls.
Can Agentic Unit Run Tests And Commands?¶
Yes. Agentic Unit can run repository commands in its isolated workspace without asking for approval for each command. Whether a test succeeds depends on the tools, dependencies, network access, and secrets available to the job.
Include setup and verification instructions in the repository. Never put credentials in those instructions or in a prompt.
Does Agentic Unit Open A Pull Request Automatically?¶
The standard coding workflow clones the repository, creates a branch, commits the result, and pushes the branch. It does not guarantee that a pull request is opened. Open and review the pull request using your team's normal process.
The CLI local workflow is different: it can return a patch and apply it to your local checkout instead of pushing a remote branch.
Can Agentic Unit Review A Pull Request?¶
Yes. Add a new pull request comment with the mention configured for your environment and describe what to review. Agentic Unit posts one summary comment; it does not add inline comments, approve, or merge the pull request.
See GitHub Pull Request Reviews.
Can Agentic Unit Update Jira?¶
An agent with the Jira skill can read issues and, when the technical user's Jira permissions allow it, add comments, transition status, or update fields. The available actions depend on the selected agent's skills and the Jira project's permissions.
Can I Continue An Existing Job?¶
Yes. Resume the job from chat or the CLI when it needs more direction. Use the same job when the follow-up depends on its existing conversation and workspace; start a new job for unrelated work.
Can Agentic Unit Use Secrets?¶
Only through approved secret integrations configured by administrators. Agentic Unit resolves those secrets for the isolated runtime. Do not paste passwords, tokens, private keys, or other credentials into prompts, tickets, pull request comments, or chat.
Where Do I Report A Problem?¶
Use your existing Agentic Unit platform-team contact route and include the environment, team, request or job ID, affected repository or ticket, approximate time, and sanitised error output. The dedicated Service Desk request type is not yet live.