Skip to content

Every unwatched Claude session a skill's instructions start runs in auto mode #249

Open

Description

@ooloth

Current state

A skill can tell an agent to start a Claude session that nobody watches in bypass mode, and no check notices. Until 89ac2e4, plan-unattended started implement-unattended in a tmux window through cc.bash without --unattended, and off the work laptop cc.bash defaults to bypassPermissions, so that session read ticket text with no permission checks. The skills lint fails only a script that calls claude-tab.bash without the flag, so a cc.bash launch written in a skill's instructions passes unchecked.

Ideal state

  • The skills lint fails a skill whose instructions start a session nobody watches through cc.bash without --unattended, naming the file and line
  • A launch the user watches, such as the review session CLAUDE.md opens in a tmux window, passes the lint

Decisions

Constraints

Open

  • How does the check tell a launch the user watches from one nobody watches: an exemption list, a marker in the skill, or something else? (Listed at the requester's request rather than as a one-way decision.)

Starting points

  • tools/agents/check-skills.py — the existing --unattended check for claude-tab.bash scripts
  • tools/claude/cc.bash — how --unattended sets the permission mode
  • tools/claude/config/CLAUDE.md — the watched review launch in "Work in Small Steps", step 9

Activity

  1. added
    maintenanceUpkeep that changes how the repo is built, not what it does
    on Nov 5, 2026
  2. ooloth commented on Nov 19, 2026

    @ooloth
    OwnerAuthor

    Since 2ef2c50, cc.bash has a second way into auto mode: a caller's own --permission-mode is kept. That path still runs the work logins, which wait with no time limit, so an unwatched launch using --permission-mode auto instead of --unattended can hang before Claude starts. hub uses this path (ooloth/hub#435), but it isn't a skill, so the lint wouldn't cover it.

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

    maintenanceUpkeep that changes how the repo is built, not what it does

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions