Skip to main content
Jig UI shows the projects you connect on one page: each with its tasks counted and what waits for you in it, and a board of its tasks one click away.

​
Connect a project

Paste the path of the project’s main checkout — the folder you cloned — into the field on the page and choose Connect. A path inside the project works too; Jig UI connects the project’s root. ~/ stands for your home folder. The project needs Jig 0.29.0 or later. Each project gets a short id from its folder name (My Project becomes my-project, a second api becomes api-2); the page names it by that id. A path is refused when it is:
  • not inside a git repository, or does not exist;
  • a worktree. A task started in a worktree keeps its records in the main checkout, which lists every task of the clone. Connect the main checkout instead;
  • a repository without Jig. Run jig init in it first.
Connecting a project that is already connected changes nothing.

​
What the page shows

Each connected project, in the order you connected them. For a readable project:
  • Its live tasks counted — active, paused and ready (finished tasks are not counted).
  • What needs you — the same items jig status lists under “Needs you”, most urgent first: a design waiting at its gate, a stopped autopilot run, a pull request waiting for review, a task to close. Each says what happened and what to do; a pull request comes with a link to it.
  • A note when pull request facts may be out of date. Jig reads pull requests only during jig housekeeping; when its last run is old or the forge did not answer, a waiting pull request may be missing until you run it.
The page follows the projects while it is open — see Staying current. A project whose state is not readable shows why:

​
The board

Open board on a readable project shows its live tasks in five columns. Jig UI works the column out from the task’s state in Jig every time it reads it, and stores it nowhere; the first rule that fits wins: A card shows the task’s id, class and goal, and what it waits for. Finished tasks are only counted under the board. The order inside a column is Jig’s (by id) for now.

​
Staying current

While the page is open, Jig UI watches each connected project’s .ai/ folder. When an agent or a person changes a task — through Jig, by editing a file, or with git (a pull, a checkout) — the workspace and the board show it within about two seconds, without a reload. Every minute each project is also read again, for a change the system did not report. A read that fails while an agent is in the middle of writing does not blank the page: the last good read stays until the next one. A project that keeps failing shows why, as in the table above. Watching stops when the last page closes; nothing is written in the project. If the page says its session has ended, Jig UI was restarted: run npx @fapost/jig-ui again to reopen it.

​
Disconnect a project

Disconnect removes the project from Jig UI. Nothing in the project changes: Jig UI never writes a file in a project.

​
Where the list is kept

The list of connected projects is projects.json in Jig UI’s config folder — ~/.config/jig-ui/ (or $XDG_CONFIG_HOME/jig-ui/) on Linux and macOS, %APPDATA%\jig-ui\ on Windows. It survives a reinstall. If the file is damaged, Jig UI says so and leaves it as it is, so you can fix or remove it.