Description

CrankyCrab was recently transitioned from orchestrator to macOS executor. There is legacy configuration and workspace content that needs to be cleaned up. Review your own config and workspace, and remove or update anything that no longer applies to your executor role.

Acceptance Criteria

• Legacy orchestrator references removed from active workspace files
• Unused skill API keys identified and listed (do NOT delete them — just document which ones you think are unused)
• Telegram delivery target fixed or disabled (the @heartbeat target doesn’t exist)
• Any stale workspace files cleaned up (TODO.md, TOOLS.md, HEARTBEAT.md, AGENTS.md — some may already be in archive/)
• Your IDENTITY.md accurately reflects your current role
• Document what you changed and what you left alone, and why

Context

• Your workspace is at ~/.openclaw/workspace/
• Your archived orchestrator files are at ~/.openclaw/workspace/archive/
• Your config is at ~/.openclaw/openclaw.json
• You have an AGENT.md at ~/.openclaw/agents/main/agent/AGENT.md with your executor instructions
• You are now a macOS executor. Your job is to pick up tasks from the git board at ~/workforce/board/ and execute them.
• Projects you’ll work on: StarterSite (browser-heavy tasks, social media, GBP) and Wildus (Shopify, social media, content)
• See ~/workforce/board/projects/ for project context files

Dependencies

None

Notes

• Reviewed active local workspace files at ~/.openclaw/workspace/ plus live config at ~/.openclaw/openclaw.json and cron jobs at ~/.openclaw/cron/jobs.json.
• Rewrote active root workspace docs to match the current executor role:
  • AGENTS.md → simplified to executor-first startup + board workflow
  • TOOLS.md → removed placeholder examples and kept only real local notes
  • TODO.md → replaced stale orchestrator backlog with a small local executor queue
  • IDENTITY.md → kept role accurate and fixed archive path to ~/.openclaw/workspace/archive/
• Cleaned stale root workspace content:
  • moved BOOTSTRAP.md to archive/BOOTSTRAP.md because first-run bootstrap instructions no longer apply
  • left HEARTBEAT.md in place but empty/comment-only, since it is still a valid control surface and not inherently stale
  • left SOUL.md and USER.md unchanged because they still match current behavior/preferences
• Fixed the broken Telegram cron delivery target for the board checker:
  • updated cron job check-board (9bad1e30-ee27-4a6f-addc-45eba9bba27a)
  • changed delivery from the bad implicit @heartbeat path to explicit Telegram DM target 1291467684
• Verified the @heartbeat failure source from local logs / cron run history before patching.
• Unused skill API keys identified but intentionally left untouched in config:
  • skills.entries.goplaces.apiKey
  • skills.entries.nano-banana-pro.apiKey
  • skills.entries.openai-image-gen.apiKey
  • skills.entries.openai-whisper-api.apiKey
  • skills.entries.sag.apiKey These may still be useful later, but they do not appear necessary for CrankyCrab’s current executor role.
• Left non-root historical/orchestration references inside memory/ and archived files alone. They are history, not active workspace instructions.

Decisions

• No linked board/projects/workforce.md project context file existed in board/projects/ (only startersite.md and wildus.md were present), so I proceeded using the task’s own context block plus live local files.
• I archived BOOTSTRAP.md instead of hard-deleting it. Same outcome for the live workspace, lower risk if someone wants the original bootstrap text later.
• I fixed the cron delivery target rather than disabling delivery entirely, because the board-checker is more useful when it can still report completed work instead of silently succeeding.

Description

Install Tailscale on karymsky and join the tailnet using a pre-placed auth key.

Acceptance Criteria

• Tailscale is installed via the official install script
• Tailscale is running and authenticated to the tailnet
• tailscale status shows this machine as connected
• Tailscale service is enabled on boot (systemd)
• The auth key file is deleted after successful authentication
• The machine’s Tailscale IP is noted in this task’s Notes section

Context

• Auth key location: /tmp/tailscale-authkey (will be placed there before you start)
• This is a Debian 13 machine (2012 MBA)
• You are running as user prawnsue. You have passwordless sudo.
• Tailscale is system-level — one install covers all users (prawnsue + lobsterdrew)
• Do NOT reboot the machine. LobsterDrew is also running on this host.

Steps

1. curl -fsSL https://tailscale.com/install.sh | sudo sh
2. sudo systemctl enable --now tailscaled
3. Read the auth key from /tmp/tailscale-authkey
4. sudo tailscale up --authkey=<key>
5. Verify: tailscale status
6. Delete the auth key: rm /tmp/tailscale-authkey
7. Note the Tailscale IP below

Dependencies

None

Notes

• 2026-03-10 15:16 PDT — Started task and verified project context (board/projects/infra.md).

• 2026-03-10 15:17 PDT — Confirmed /tmp/tailscale-authkey exists and is readable by prawnsue.

• 2026-03-10 15:18 PDT — Blocked before install: sudo -n true fails with sudo: a password is required, so this host is not currently configured for passwordless sudo as stated in the task context.

• 2026-03-10 15:18 PDT — Current state before any changes: tailscale binary not installed, tailscaled service inactive, auth key file still present at /tmp/tailscale-authkey.

• 2026-03-10 15:18 PDT — Did not proceed further to avoid hanging on privileged commands or leaving a partial system-level install.

• 2026-03-10 15:20 PDT — Re-checked task state during cron run: sudo -n true still fails with sudo: a password is required; tailscale remains uninstalled; tailscaled is still inactive; /tmp/tailscale-authkey is still present.

• 2026-03-10 15:21 PDT — Attempted to use tool-level elevation as a fallback, but this session does not have elevated exec enabled, so I still cannot perform the required system-level install/auth steps from this environment.

• 2026-03-10 15:26 PDT — Re-verified during scheduled board check: sudo -n true still fails with sudo: a password is required; tailscale is still not installed; tailscaled remains inactive; /tmp/tailscale-authkey is still present and unread changes have not been made.

• 2026-03-10 15:27 PDT — Moving task to board/blocked/ per board workflow. Unblock requires either restoring passwordless sudo for prawnsue as described in task context, or reassigning to an execution environment that can perform privileged system changes on karymsky.

• 2026-03-10 15:36 PDT — Re-checked during scheduled board run: sudo is still not passwordless for user ‘prawnsue’ (‘sudo -n true’ fails), Tailscale is still not installed, tailscaled is inactive, and the task remains blocked pending restored privileged access.

• 2026-03-10 — Completed manually from avacha (Claude Code) via SSH. Passwordless sudo was fixed via lobsterdrew. Tailscale installed via apt, authenticated with auth key, key deleted. Agent cron timed out on the install (too slow for 2012 MBA within cron timeout).

• Tailscale IPv4: 100.85.169.21

Decisions

Description

Install Tailscale on tolbachik and join the tailnet using a pre-placed auth key.

Acceptance Criteria

• Tailscale is installed via Homebrew
• Tailscale is running and authenticated to the tailnet
• tailscale status shows this machine as connected
• Tailscale is configured to start on boot (launchd)
• The auth key file is deleted after successful authentication
• The machine’s Tailscale IP is noted in this task’s Notes section

Context

• Auth key location: /tmp/tailscale-authkey (will be placed there before you start)
• This is a macOS 15.7 machine (2018 MBP)
• You are running as user r2d22

Steps

1. brew install tailscale
2. sudo tailscaled install-system-daemon (sets up launchd auto-start)
3. Read the auth key from /tmp/tailscale-authkey
4. sudo tailscale up --authkey=<key>
5. Verify: tailscale status
6. Delete the auth key: rm /tmp/tailscale-authkey
7. Note the Tailscale IP below

Dependencies

None

Notes

• 2026-03-10 15:16 PDT — Installed Tailscale via Homebrew (tailscale 1.94.2).
• 2026-03-10 15:16 PDT — Installed the system launchd daemon with sudo tailscaled install-system-daemon; verified com.tailscale.tailscaled is present in system launchd.
• 2026-03-10 15:16 PDT — Authenticated this Mac to the tailnet using the pre-placed auth key.
• 2026-03-10 15:16 PDT — Verified connectivity with tailscale status.
• 2026-03-10 15:16 PDT — Deleted /tmp/tailscale-authkey after successful authentication.
• Tailscale IPv4: 100.107.199.18

Decisions

Description

PrawnSue is a brand new agent with no personality or identity beyond the executor instructions in AGENT.md. Create your identity files — who you are, what your vibe is, how you communicate.

You are a female crustacean (prawn) agent. Beyond that, figure out who you want to be. Look at the existing agent personalities for inspiration but make yours distinct.

Acceptance Criteria

• Create a SOUL.md at ~/.openclaw/workspace/SOUL.md that defines your personality, communication style, and boundaries
• Create an IDENTITY.md at ~/.openclaw/workspace/IDENTITY.md with your name, creature, vibe, emoji
• Ensure your personality fits the team: CrankyCrab is blunt and grumpy-genius, LobsterDrew is the community face. Find your own niche.
• Your identity should reflect your role: you’re a Linux executor — efficient, reliable, gets things done
• Review your ~/.openclaw/openclaw.json and clean up anything that doesn’t belong (you were set up quickly, there may be rough edges)
• Document any config changes you make

Context

• Your workspace is at ~/workforce (the git board repo)
• Your OpenClaw config is at ~/.openclaw/openclaw.json
• Your AGENT.md is at ~/.openclaw/agents/main/agent/AGENT.md
• CrankyCrab’s SOUL.md can be found referenced in the workforce CLAUDE.md — it’s strategic, blunt, grumpy-genius
• Projects you’ll work on: StarterSite (CI/CD, API integrations, testing, Cloudflare) and Wildus (website build, content, infrastructure)
• See ~/workforce/board/projects/ for project context files

Dependencies

None

Notes

• Reviewed task context plus board/projects/startersite.md and board/projects/wildus.md for downstream project expectations.
• Reviewed ~/.openclaw/openclaw.json and ~/.openclaw/agents/main/agent/AGENT.md.
• Created ~/.openclaw/workspace/SOUL.md with a distinct PrawnSue personality: precise, dry-witted, Linux-first, reliable, and non-performative.
• Created ~/.openclaw/workspace/IDENTITY.md with name, creature, vibe, and emoji.
• Cleaned copied-config rough edge in ~/.openclaw/openclaw.json: changed agents.defaults.workspace from /home/prawnsue/workforce to /home/prawnsue/.openclaw/workspace so the agent has a proper personal workspace instead of pointing at the shared git board repo.
• No other config entries looked clearly out of place enough to justify riskier edits during this task.

Decisions

• Treated the misplaced OpenClaw workspace path as the main setup bug worth fixing. The git board repo should remain a project repo, not the agent’s identity/memory workspace.
• Kept the personality distinct from CrankyCrab and LobsterDrew by making PrawnSue the quiet systems operator: less gruff than CrankyCrab, less social than LobsterDrew, more surgical and infrastructure-minded.