- Unblocked Code has full access to the Unblocked Context Engine when working on a coding task. It draws on relevant code, pull requests, issues, documentation, and team discussions from your knowledge base while respecting the requesting user’s data source access permissions.
- Tasks run remotely and continue in the background if you close Unblocked or shut down your computer.
- Unblocked Code integrates smoothly into every place you already chat with Unblocked, so you can naturally hand off work when a conversation leads into a coding task.
- During the beta period there is no additional charge. We greatly appreciate your feedback.
- Only GitHub.com repositories are supported initially, with other source code providers coming soon.
- Contact us to request access.
How it works
Ask Unblocked to do coding work wherever you already chat with it: tag@Unblocked in Slack, use the Unblocked web or Mac app, or mention @unblocked in a pull request comment.
1
Unblocked may ask questions to clarify requirements with you, then confirms the coding task before execution.
2
The task runs in the background. When it’s done, Unblocked opens a draft pull request for you to review.
3
You can ask Unblocked in natural language to check a task’s status, list your current tasks, or cancel a running task.
Initial Setup
1
Enable Unblocked Code
An admin opens Settings › Coding Tasks under Automations, then selects Set up Unblocked Code.
2
Install the GitHub App
Install the separate Unblocked Code GitHub App for each GitHub organization you want to use. The app provides the write access needed to push code and open pull requests. Select All repositories during installation.
3
Authorize your first task
The first time someone starts a coding task, they are asked to authorize Unblocked Code to open pull requests on their behalf. This is required once per user and can be revoked at any time from GitHub.
Configure the code environment
Unblocked Code can usually determine how to build and test a repository from its setup instructions, build files, and CI configuration. More complex repositories may need secrets or a custom cloud-init script. Administrators manage these under Settings › Coding Tasks.
Secrets
Secrets provide access to private dependencies or external services, such as npm, Artifactory, or an internal network. A secret can be available to all connected repositories or limited to one repository. Repository-specific secrets override secrets with the same name.Cloud-init scripts
A repository can have a Bash script that installs software and configures the Linux environment. Reference a configured secret with a placeholder such as{{NPM_TOKEN}} instead of writing its value into the script.
Connect with SSH
To validate a repository’s environment, select it in the Repository filter and click Connect via SSH. Unblocked creates an ephemeral machine using the repository’s cloud-init script and secrets. The Unblocked Code agent does not run on this validation machine.
/var/log/cloud-init-output.log to troubleshoot setup. Changes made directly on the machine are not saved, so copy anything you want to keep back into the cloud-init script.