Skip to main content

Liney Documentation

Diagram showing how Liney connects a workspace to worktrees and terminal sessions

Liney is a native macOS workspace for repositories, worktrees, terminal sessions, and parallel coding flow.

This documentation is organized around how you actually use the product:

  • start with one repository
  • create worktrees for parallel tasks
  • keep terminal sessions attached to the worktree that owns them
  • use the sidebar as a live map of what is active
  • add remote and agent-backed sessions when local shells are not enough
  • reuse workflows instead of rebuilding the same setup every day

If you are coming back to Liney​

The latest product surface is much stronger around reusable launch setup.

If you already know the basics, start here:

Start here​

If you are new to Liney, read these in order:

  1. Getting Started
  2. Worktrees & Sessions
  3. Command Palette & Quick Commands
  4. Presets and Reusable Launchers
  5. Overview & Canvas
  6. Hidden Features

Quick routes by goal​

If you want the shortest path to a specific outcome, use these routes:

Guides​

Use the guides section when you want to understand a surface in the app:

Workflows​

Use the workflows section when you want to shape your daily operating model:

What makes Liney different​

Most terminal tools give you shells.

Liney gives you:

  • repository-aware workspace structure
  • visible worktree state
  • pane and tab context that stays attached to the right checkout
  • workflows, remote targets, and agent presets that stay attached to the repository
  • a faster way to re-enter active work without rebuilding context

Who this is for​

Liney is best suited for developers who:

  • juggle multiple branches or worktrees
  • keep several terminal tasks alive at once
  • switch often between coding, review, testing, and debugging
  • want native macOS behavior instead of a browser shell

A good upgrade path​

You do not need to adopt every feature at once.

A practical path is:

  1. add one repository
  2. open one local session
  3. split active work into worktrees
  4. save one SSH target or one agent preset you reuse often
  5. turn your daily startup path into a workflow