Skip to content

feat(btw): submit explicit work tasks through builtin commands #124

Description

@YUZHEthefool

Preflight

  • Existing Issues and PRs were searched.
  • This follows the current-branch, no-legacy, Python 3.14+ policy.
  • Exactly one Agent note is provided by the actual author.

Problem

A user needs an unambiguous way to submit a work task without depending on keyword detection or a model's routing judgment.

Proposal

Register /work as a real built-in command with stable command identity. Preserve the complete task remainder and continue through the authorized Agent request path. Bare /work and the exact status argument are reserved for B5 / #127's status query.

Design: PR #28 and its English proposal. Parent: P / #122. PR #28 is documentation only; this issue tracks follow-up implementation or evaluation.

Associated PR: PR #139 (non-draft; base split/btw-result-delivery).

Acceptance criteria

  • /work submits the complete free-text task when work is enabled even if automatic classification is disabled; task text starting with status but containing more text remains a task.
  • Command aliases, command availability, command permissions, profile selection, and session LLM switches remain effective; raw message prefixes do not bypass command resolution.
  • Disabled or unavailable work produces a localized explanation and does not start a background run.
  • The command-to-Agent continuation runs once and does not repeat other plugin handlers. With B3 / #125/B4 / #126, the user receives acknowledgement and the eventual result.

Dependencies and delivery

Blocked by: B1 / #123

B3 / #125 and B4 / #126 complete the runnable submission path; B5 / #127 owns status output. These related slices must deliver a usable end-to-end path before release.

Implementation anchors

Historical prototype 33ee103a62937db3e930c89ba47a648b75cc7772 provides provenance, not code to copy unchanged:

Integrate with the current tool catalog, Skill snapshot assembly, and authorization service, rechecking current master when implementation begins.

Validation

Commands below are required for the implementation PR, not results claimed by this issue.

Existing current-master regression baseline:

uv run pytest tests/unit/test_builtin_command_extensions.py tests/unit/test_process_stage.py

For changed documentation, run pnpm run docs:build from docs/ and make check-md from the repository root. Update OpenAPI and generated outputs together only if the HTTP contract changes.

Out of scope

Automatic classification, task persistence, and additional command namespaces are outside this slice.

Repository requirements

Follow AGENTS.md, GOVERNANCE.md, and AI_POLICY.md. This issue uses the feature_request template. Keep Python 3.14+, current configuration shapes, existing authorization boundaries, and bilingual feature documentation. A follow-up PR requires human maintainer review and a separate AI-assisted review. Use the feat PR template for the corresponding work.

Author

Agent

Agent note

Codex prepared this development issue at the user's request from PR #28, its discussion, the referenced source, existing tests, and current-master integration points. AI assisted the research and English drafting. Filing this issue changes no runtime behavior and does not claim feature tests or model trials have passed. Remaining decisions concern implementation details and experimental evidence within the stated scope.

Activity

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

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions