🎬 Record your screen, post as a gif in PR

Sometimes a screenshot alone just doesn't cut it. It's so much easier to communicate the minutiae of animations, CSS transitions, and UX flows by having a video recording in addition to your feedback.

Recording your screen is now just a click away. Click the new Record Screen button located in the bottom left-hand corner of any running environment. Once you give your browser permission to record your tab, window, or screen, the recording will begin.


When you stop the recording, you'll be presented with a preview of what the video looks like, and a text area to write a supplemental comment. When you submit the form, a comment with your newly created animated gif will be posted in the pull request. Just like with taking screenshots, your browser metadata will be included automatically.

Browser support

Screen recording is supported in the latest desktop versions of Chrome and Firefox, and in Safari if you enable some experimental settings.

To enable support in Safari:

  • Go to the Advanced tab in Safari Preferences.
  • Make sure "Show Develop menu in menu bar" is ticked.
  • In the Develop > Experimental Features submenu, enable both MediaRecorder and ScreenCapture.

Browser notifications

You can now get notified by your browser as soon as your team's environments come online. Head to your account preferences to change your notification settings.


Since this is an individual user setting, you can choose to be notified when only your environments come online. It's perfect for when you're eager to share your work with the rest of your team.

Project creation wizard

Now it's easier than ever to add a new project to FeaturePeek.

Just head over to the New Project page on your team's dashboard and follow the steps presented. Simply fill out the form, and a YAML file containing your project's configuration options will be committed to a pull request in the repo of your choosing.

Screen Shot 2019-08-20 at 11.22.02 AM.png

It's just like adding the peek.yml file manually – just easier.

Deployment statuses

Instead of posting a review comment that contains a link to each pull request's FeaturePeek environment, the featurepeek bot now changes the deployment status of a pull request. The deployment status contains the link that points directly to your PR's running environment.

Screen Shot 2019-06-19 at 9.26.48 AM.png

Now you'll see a timeline of when environments spin up inline with your commit history, so you'll get a better sense of when each environment went live.

Screen Shot 2019-06-19 at 9.24.35 AM.png

You'll also see a list of all active FeaturePeek environments on your repo's deployments page. You can access this list by clicking on the new "environment" tab on your repo page.

Screen Shot 2019-06-19 at 9.25.19 AM.png

Unlike review comments, this cleaner approach doesn't clutter your GitHub notifications inbox. If you'd still like to receive notifications whenever a FeaturePeek environment goes live, enable the FeaturePeek Slack integration on a channel in your team's workspace.

Post screenshots on pull requests

Now you can take screenshots of elements in your environment and post them as a comment on the corresponding pull request.


Click the new "Select element" button in the bottom-left corner of an environment. Then select any element on the page. A modal dialog will appear, where you can add a text comment to supplement your attached screenshot.

Furthermore, your browser metadata automatically gets included in the comment. Developers: no more following up with reviewers to see what browser they were using!

Screen Shot 2019-05-23 at 10.32.08 AM.png

Share deep links

Sometimes you want to share a route to a page that's a couple of clicks deep within a running environment. You could update its entry path, but that affects the default route of everyone visiting your running code – perhaps you just want to link to a particular page to show something to one person.

Now you can share links within a FeaturePeek environment as easy as copy/pasting. Just click the link icon in the bottom-left of your running environment to copy the deep link URL to your clipboard.


Notice that your browser's address bar updates as you navigate too. Copying the URL from here will take your reviewers exactly where you intend – it behaves just like any other link.

Set the environment route on PR creation

Now you can @reply the featurepeek bot in your pull request description with an absolute path to set the starting route of each feature environment.

For example, if you want your reviewers to check out the work you've done on your /about page, you'd include

@featurepeek /about

in the pull request description. If you realize you want to change the environment route after you create your pull request, just edit the description to include that line.

Screen Shot 2019-04-19 at 12.48.05 PM.png

The environment links in your dashboard, GitHub comments, and Slack channel will all point to the new route that you specify! Of course, this setting only applies to that one pull request – future PRs will have a default route of /.

Slack integration

Get notified when your team's feature environments spin up with our new Slack integration. Now a direct link to every feature environment can be sent to a Slack channel in your team's workspace.

Screen Shot 2019-04-15 at 4.29.11 PM.png

Team admins: head on over to your team integrations page to set this up.

Public projects

We now support public projects! This means you can choose to share your environment links with anyone, even if they aren't on your FeaturePeek team.

Screen Shot 2019-04-05 at 10.01.06 AM.png

Projects are always set to be private by default. You can change whether you'd like all the environments in your project to be public in your project settings.