projects and machines

Keep your projects in one list, and take them to another machine.

After this page, you can add a project, read what is delivered but not landed, and give a second machine the project names, icons, and untracked skills that Git does not carry.

Checked against the product on 6 October 2026

Latest release: Clawdline v2.9.0 · platform support

Before you start

  • Free and local. The Projects page and clawdline project need no account.
  • The console follows your system language. Labels are shown in Traditional Chinese, as on a Taiwanese Mac, with their meaning in parentheses.

Add a project

A project is a directory an assistant has run in; Clawdline finds those by itself. To add a directory before any assistant has run there: 

clawdline project add ~/code/my-app
clawdline project list
clawdline project remove ~/code/my-app

These work without the daemon, and remove deletes nothing on disk. In the console, the + in Start a session adds a folder the same way. Expected result: the directory is offered when you start a Session.

Read the Projects page

  1. Open 專案 (Projects). It lists directories an assistant ran in that still exist.
  2. Under 版本庫生命週期 (repository lifecycle), each repository shows its 工作樹 (worktrees), work that is 做完了，沒有落地 (delivered, not landed), and what is 已落地 (landed).
  3. Press 重新觀測 (look again) to refresh. The view is read-only.

專案能力健檢 (project capability check) at the top shows, per project, whether its icon, deploy progress, dev servers, and Git origin are set up. Press 補齊設定 (complete setup) to open a new Session ready to set them up; no Session is created until you confirm the start. The files involved are listed in Project files.

Share project rules and skills between Claude Code and Codex

From the repository root, run clawdline project unify to preview how both assistants can read the same project instructions and skills. You can also pass a project directory. The preview lists the files each assistant reads now, the proposed changes, and any conflicts; this command writes nothing. 

clawdline project unify
clawdline project unify --apply
clawdline project unify --check

Review the preview before running --apply. It puts shared rules in AGENTS.md and makes CLAUDE.md import them when needed. Shared skills live in .agents/skills/, with .claude/skills/ entries pointing to the same directories (or copies where links are unavailable). --apply uses the plan it just printed and stops if the files changed in the meantime. It never commits to Git.

Differences that need your decision remain in the conflict list: for example, Claude-only instructions or two skills with the same name but different contents. Move rules meant for both assistants into AGENTS.md and resolve differing skills yourself; unify will not choose which version wins. Expected result: --check prints status: unified after all changes and conflicts are resolved. A drifting project exits 1; one it cannot inspect exits 3. The same preview is in the Project gear under Claude 與 Codex 共用.

Bring projects to another machine

A second machine can have the repositories and still lack what Git does not carry. One machine (the source) owns those settings; the others mirror them. Projects are matched by their Git origin, so checkouts may sit at different paths.

CopiedNever copied
The project's name and iconFiles tracked by Git (they come with the repository)
Untracked files under .claude/skills, .claude/commands, .claude/agents.claude/settings.local.json, which holds the source's permission grants
CLAUDE.local.mdDot files such as .env, build caches, and your personal ~/.claude/skills

Through Clawdline Cloud

Both machines run this version, your browser is paired with both, and the receiving machine allows Cloud commands.

  1. In the hosted console, open the receiving machine and go to 專案.
  2. Open 專案設定同步 (project settings sync) and choose the source under 主要機器 (main machine).
  3. Press 讀取它的專案 (read its projects). Untick what you do not want; tick the clone line if this machine lacks some repositories.
  4. Press 同步所選的 N 個專案 (sync the selected projects).

Expected result: each project reports files written, files kept because they were edited here, or a clone in progress. Opening 專案 on the receiving machine later applies new changes from the source. Undo: press 改回本機設定 (use this machine's settings) on a project's row.

Without Cloud

clawdline project export --out projects.json          # on the source machine
clawdline project import --clone projects.json        # on the receiving machine

--clone clones repositories the receiving machine lacks; without it they are reported as missing. Expected result: each project shows the source's name and icon, and a mirrored skill is in that checkout's .claude/skills/.

Project icons

A project's icon is, in order: an icon copied on the Projects page, its entry in ~/.claude/project-icons.json (see Project files), or one generated from its path. A mirrored project's icon belongs to its source. To give one project another project's icon, possibly on another machine:

  1. On the Projects page, open 複製專案圖示 (copy project icon), choose the source project, and copy its icon.
  2. Switch to the receiving machine if needed, return to Projects, and choose the destination.
  3. Compare the current and copied icons, then apply.

It is a one-time copy held only in this browser tab; later changes to the source do not follow. If the destination's icon changed meanwhile, the apply is refused: read again and decide.

Where to go deeper