Launch Agents | GitKraken Workflows
Step 1: Start From An Idea, Issue, Or PR
Start with the work already in front of you: an idea, assigned issue, or pull request. Create a Task from scratch or fire an Action from Todo, then attach the repositories, issues, pull requests, folders, files, and links that matter.
Kepler keeps the Task and its supporting context connected as the work develops, so the agent starts with a clearer picture of what needs to happen and why. When you launch from Todo, Kepler can create the Task, attach the work, prepare the worktree, and start the agent for you.
Trigger
- You have an idea, issue, or PR ready to move forward.
Step 2: Choose How The Work Gets Done
Choose the Action that matches what the Task needs next: Plan, Implement, Review, Address Feedback, or one of your own workflows. Actions give you reusable prompts for common development tasks and can inherit your default agent configuration or use a complete override. When you need more control, you can still choose the agent and session settings explicitly before the work begins.
Trigger
- The right agent starts with the right workflow and context.
Step 3: Track The Agents
Start multiple agent sessions inside the same Task when the work can move forward in parallel.
Sessions can share a worktree, run in separate worktrees or folders, or start across every attached location. Each session can access the Task's shared resources, while separate worktrees isolate code changes when agents need room to work independently. That gives you flexibility to parallelize the work without separating it from the Task and context that connect everything together.
Expected result
- Multiple agents progress independently within one connected Task.
Step 4: Unblock Your Agents
Use Agent Graph to see which sessions are working, blocked, unread, or failed. The “Needs Attention” section surfaces agents waiting for your input. Jump into the relevant session to answer a question, approve a permission, queue a follow-up, or redirect the agent.
Desired outcome
- Know which agents need your attention and act without losing context.
Step 5: Pick Up The Work
When an agent finishes, inspect the worktree's changes and review the diff before anything moves forward. Keep what is right, make adjustments when needed, or run another Action to continue refining the work. Once the result is ready, commit and push the branch. If the work moves into a pull request, keep review comments and follow-up agent sessions connected to the same Task so the context survives through review and merge.
Success criteria
- Agent work stays connected to the original Task and context.
- Changes are reviewed and refined before moving forward.
- The Task progresses from idea or issue toward a merged PR.
Step 6: Get The Tools To Complete This Workflow
You have seen the workflow, now choose the tools that make it repeatable. Kepler keeps agent sessions organized around the task, GitKraken Desktop gives you visual control of branches, commits, pull request prep, and conflicts, and GitLens brings code history and authorship into your IDE. Start with the tool that matches how you work today, or use GitKraken Pro at 60% off to bring the full plan-to-main workflow together under one subscription.
Success criteria
- Download the GitKraken tool that fits where you work most: your agent workspace, repository, or IDE
- Create a free account and unlock every feature for 14 days
- Connect your repository and integrations, then put your first agent to work on a task or issue