Skip to content

Latest commit

 

History

History
113 lines (94 loc) · 6.24 KB

setup.md

File metadata and controls

113 lines (94 loc) · 6.24 KB

Set up a new machine

This page gives the steps to set up a new machine, so that an orchestrator session can run the tickets of codeguru42/tasker there. The user is the person who sets up the machine. The user does each step of this page. The local clone is $HOME/src/mine/tasker. The configuration file is the file of tasker that docs/config.md describes.

The tools

On 2026-10-18, the machine used Node 26.7.0, git 2.47.3, gh 2.101.0 and Claude Code 2.1.302.

  1. Install git, gh, Claude Code and nvm.
  2. Log in to gh as the account codeguru42: gh auth login --hostname github.com --scopes project. The scope project is for the project board. The token scopes of docs/config.md give the scope that tasker needs. If a command of the project board fails for a missing scope, follow the fix in The project board.
  3. Make sure that the ssh key of the account reaches git@github.com, because the remote of the repo uses ssh: ssh -T git@github.com. Facts about outside tools gives the exit codes of this command. If the exit code shows a wrong key, fix the ssh key of the account. Then run the command again.

The local clone

  1. Clone the repo to the local clone: git clone git@github.com:codeguru42/tasker.git $HOME/src/mine/tasker. The orchestrator and its task subagents run git and tasker from this clone.
  2. In the local clone, run nvm install, so that the clone uses the Node version of step 1 of Set up a working copy.
  3. The folder bullet of Limits gives the place of the task worktree. Do not change the other entries of $HOME/src/mine/tasker-worktrees/. They belong to other work.

The installed tasker

The orchestrator runs the tickets with the installed tasker, as docs/orchestrator.md says.

  1. Set up the configuration file:

    • Open the configuration file. Where the file is gives its place.
    • If the configuration file does not exist, make it with the top-level keys of the example of docs/config.md, for example dataRoot, skillsDirs and limits.
    • Under repos, add this entry. In a new file, it is the only entry under repos:
    "codeguru42/tasker": {
      "issueTracker": { "provider": "github", "account": "codeguru42", "updateOnStart": true, "updateOnFinish": true },
      "remote": "git@github.com:codeguru42/tasker.git",
      "defaultBaseBranch": "main",
      "bootstrap": { "commands": ["npm ci"], "env": [] },
      "verify": { "commands": ["npm run check"], "env": [] },
      "assistant": {
        "provider": "claude-code",
        "models": {
          "plan": { "model": "claude-opus-5-5", "effort": "medium" },
          "execute": { "model": "claude-sonnet-5-5", "effort": "medium" },
          "review": { "model": "claude-opus-5-5", "effort": "medium" }
        }
      },
      "sessions": {
        "models": {
          "operator": { "model": "claude-sonnet-5-5", "effort": "medium" },
          "planner": { "model": "claude-opus-5-5", "effort": "high" },
          "orchestrator": { "model": "claude-sonnet-5-5", "effort": "medium" }
        }
      }
    }
  2. In the local clone, do the steps of the Install section of README.md. The steps run npm run install:global. The script never checks out another commit. The script runs tasker install-skills. That command copies the skills of the installed tasker into each folder of skillsDirs. These skills come from the folder skills/ of the repo. That command needs the configuration file.

  3. Run tasker doctor. It must pass. If a check fails, fix the cause that the check names. Then run tasker doctor again.

  4. If the tasker clone does not exist yet, run tasker start for one issue first. Then, in the local clone, add the read-only tasker remote, as steps 1 and 2 of docs/dev/rebase-conflicts.md say.

Claude Code

The repo file .claude/settings.json needs no change, as the plain-form rule says.

The permission rules of the actors of the orchestration live in the docs. See the permission model. The exception is the ask rules of the steps below. They live in the user file and reach each actor.

  1. In $HOME/.claude/settings.json, set permissions.defaultMode to "auto".
  2. Add these rules to permissions.ask, so that the user approves each such command:
    • Bash(tasker approve-credits) and Bash(tasker approve-credits *)
    • Bash(tasker abort) and Bash(tasker abort *)
    • Bash(tasker update-branch *--undo*)
    • Bash(git push --force*), Bash(git push * --force*), Bash(git push -f *), Bash(git push * -f *) and Bash(git push * +*)
    • Each git command and each cd command that names the data root of the installed tasker, for example Bash(git -C $HOME/.local/share/tasker/*), Bash(git --git-dir $HOME/.local/share/tasker/*), Bash(git --git-dir=$HOME/.local/share/tasker/*), Bash(git --work-tree $HOME/.local/share/tasker/*), Bash(git --work-tree=$HOME/.local/share/tasker/*) and Bash(cd $HOME/.local/share/tasker/*)
  3. In each rule, write the absolute path of the home folder in place of $HOME.
  4. Install the skill simple-english in $HOME/.claude/skills/.
  5. The repo holds the skill /session-review in .claude/skills/session-review/. If $HOME/.claude/skills/session-review/ exists, remove it, because Claude Code loads that copy in place of the copy of the repo.
  6. Install the Claude Code plugin superpowers: claude plugin install superpowers@claude-plugins-official.
  7. In $HOME/.claude/CLAUDE.md, add the line activate simple-english in all sessions.

Codex

  1. Install Codex: npm install -g @openai/codex.
  2. Log in to Codex: codex login.

pi

  1. Install pi: curl -fsSL https://pi.dev/install.sh | sh. No one tested this command.
  2. Log in to each upstream with /login in pi.
  3. Install superpowers: pi install git:github.com/obra/superpowers.
  4. Copy the skill folder simple-english that Claude Code installs in $HOME/.claude/skills/ to $HOME/.agents/skills/.