GitHub
Development

Your scripts and client projects, searchable from the ticket.

A client's nightly sync job failed. Junto finds the repository your team built for that client, reads the script, checks the latest commits, and opens a GitHub issue linked back to the ticket with your approval.

Many MSPs keep scripts, automation, and custom client projects in their own GitHub organization. Junto connects through the Junto GitHub App, installed on your MSP's GitHub organization with the repositories you choose, so no password or personal token is stored. You describe each repository and the customer it was built for, and that customer's repositories come first when the agent works their tickets. The agent can search code, read files, issues, pull requests, and commits, and with approval open or close issues. Tickets can be linked to GitHub issues so the requester hears when the fix ships.

What this means for your team

Code search across your repositories, with a customer's projects listed first
Scripts and config files can be read without cloning anything
Recent commits and pull requests explain what changed before a break
Issues open from the ticket with a link back, after your approval
Repositories you turn off are invisible to the agent

Ready to connect GitHub?

Setup takes minutes. Our docs walk you through every step.

View setup guide

See GitHub + Junto in action

15-minute demo. We'll walk you through exactly how Junto works with GitHub.

Book a demo