Use Lorecrew

Projects

Create, add and clone repositories with deliberate ownership.

Projects connects portable project identity with a checkout on this machine. Open Projects in the desktop navigation, or More → Projects on a narrow screen. Search by title, ID or repository alias.

Create, add or clone

Create project asks for a title, explicit parent folder and child folder name. Confirmation creates a Git repository, README and initial commit, then uses the normal confirmed authority path for a new identity. No conversation or task starts automatically.

Add existing repository inspects a usable Git root and preserves its working files, staging area and untracked files. Recognized aliases and existing private lineage reuse recorded identity. An opaque association requires explicit confirmation; a recognized mismatch cannot be overridden.

Clone from vault prepares a checkout for an existing recorded project. Review the source and destination, choosing or confirming a recognized alias or credential-free custom source. Clone preserves the project ID/title and grants no ownership. Unrecorded sources can be cloned with host Git and then added. An empty recorded source stays blocked until usable history exists; it is not scaffolded as a new project.

Folders are on the service host. Browsing is not confirmation, and every new form starts without a selected folder.

Read the readiness separately

ObservationMeaning
Not cloned here / Available here / Needs repairLocal checkout observation
Ready here / Owned elsewhere / Ownership needs verification / Execution needs repairExecution authority and binding observation
Local only / Saved locally / Synchronized / Needs attentionAvailable Git status

An available checkout, portable origin marker or operator assertion does not grant execution ownership. Reading a catalog/detail page does not claim, fetch, push or call a model.

Details link to existing tasks and conversations. Ask agent prepares a draft for explicit sending. Publishing, checkpoint selection and stopped handoff use the existing deliberate agent/CLI operations. See multiple machines.

Interrupted confirmation

Confirmation freezes source, destination, selected identity and native operation ID. If a response is lost, inspect and resume the original operation. Review original operation can recover its server preview after the browser draft is lost. Refreshing a page observes state without retrying effects.

Do not start another intent to escape an uncertain Git operation. Unknown children, an externally changed index, replaced directories, lost ownership and used bindings remain guarded. A used binding cannot move to a different root or Git common directory.

Project rename/archive/delete, multiple primary checkouts and an embedded project work dashboard remain future extensions.

Read or improve this guide on GitHub

Find your way

Browse all guidesEsc to close