Skip to content

Document SlipJay workspaces and Land for users #44

Closed

Description

@pechhe

Part of #21. From the Spec review of #21 (Spec 6).

Outcome

Users of a SlipJay project can find out from the user docs that each new thread gets its own SlipJay workspace, what the composer strip shows, and how Land works and reports.

Problems found

  • docs/user says nothing about automatic workspaces, the strip, the landing state, Land, or Git actions being absent in Jujutsu and colocated repositories.
  • The Settings row text still says "new worktree threads", although every thread in a SlipJay project now allocates a workspace.

Acceptance

  • One concise section in the relevant docs/user guide, following the AGENTS.md documentation rules: what happens, how to start, and the unintuitive parts. For example, Land removes the landed workspace, and it needs a SlipJay runner location.
  • The Settings text matches the behaviour.

Activity

  1. pechhe commented on Oct 15, 2026

    @pechhe
    OwnerAuthor

    Landed in c80c7f0: source control guide explains Jujutsu checkouts, SlipJay workspaces, the composer strip and Land; the Settings Workspaces row describes each provider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentSettled scope eligible for dispatch

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions