Getting Started

This page gives you the fastest path to building your first workflow. You can test everything on the public installation.

GitHub access and token setup

GitHub setup is important for day-to-day EAGLE use.

Without a token

You can still load graphs and palettes from public repositories. This is useful for first-time users and quick testing.

Limitations without a token:

  • You cannot save changes back to GitHub from EAGLE.

  • You cannot access private repositories.

  • GitHub API requests are heavily rate-limited for anonymous users (typically around 60 requests per hour per IP).

Classic personal access token

EAGLE currently uses a GitHub personal access token (classic). Fine-grained tokens are not currently used in EAGLE.

The screenshot below shows the permissions used when creating a token for EAGLE.

Show token permission screenshot

GitHub classic personal access token permissions for EAGLE

Example GitHub classic token configuration for EAGLE.

Based on this setup, enable:

  • repo

  • read:user

  • read:public_key

Set your token in EAGLE under Settings in External Services -> GitHub Access Token.

The in-app Quick Start tutorial also walks through adding the token. To access the tutorial, follow the steps in the next section.

For token creation steps, see the official GitHub guide: Managing your personal access tokens.

Getting started with the UI

We offer several in-app tutorials to help you familiarize yourself with EAGLE. You can launch them directly on the live EAGLE instance:

For a longer walkthrough of the full workflow, see Hello World Example.