PostHog / PostHog/posthog

Auto-exit Plan Mode when executing a skill

Open
#76,260 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature/desktop
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
6h 51m
Merged PRs (30d)
232

Description

Context

Raised in Slack. Users who prefer Plan Mode as their default frequently kick off skills as new tasks. Skills almost never benefit from running in Plan Mode, they are meant to execute, not plan.

Problem

When a user is in Plan Mode and triggers a skill (e.g. /commit, /simplify), the skill runs in Plan Mode too. This means the skill describes what it would do instead of actually doing it, which is almost never the desired behavior.

Expected behavior

Two possible improvements (not mutually exclusive):

  1. Prompt on discrepancy: When a skill is triggered while in Plan Mode, show a prompt like: "It looks like you're running a skill in Plan Mode. Did you mean to execute the skill?" with options to continue in Plan Mode or switch to execution.

  2. Auto-exit Plan Mode for skills (preferred): Automatically exit Plan Mode when a skill is invoked, so the skill executes normally. This could be controlled by a setting (e.g. autoExitPlanModeForSkills: true) for users who want the current behavior.

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing how Plan Mode state is handled when a skill such as /commit or /simplify is invoked, then determine where the mode transition should occur. Done means skill execution no longer remains in Plan Mode, while the proposed prompt or setting behavior is resolved.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.