naudachu
e628ad6fd9
BREAKING: the plugin is `kettle`, not `tea`, and its commands are `/kettle:*`. It also now needs a binary on PATH that it did not need before; the README and every skill say how to get one and what a missing one looks like. The plugin was 3800 lines of Python doing what a compiled binary does better, and the name pointed at a tool that no longer takes part: `tea` is Gitea's CLI, and since the transport moved into the binary nothing here shells out to it for issues at all. A plugin named after it was going to keep suggesting otherwise. Deleted: 19 scripts, the 14-file unittest suite, and the tea-guard hook. The guard blocked any `tea` invocation that would run under a login the model picked instead of the operator; the binary holds its own credentials and reads the pinned login out of the project's own config, so that failure is no longer expressible and there is nothing left to police. agents-sync stays — it is about AGENTS.md symlinks and has nothing to do with any of this. What the plugin keeps is what only a plugin can carry: the rules an operator states and a binary cannot enforce. `init` still refuses to run inside a linked worktree and still may not be model-invoked, because which directory is the project is a statement a person makes. The issue format reference stays here and stays the source of truth. The runner subagent is still for batches and still may not decide what an issue says. The command reference in the issue, sync and project skills is GENERATED from the binary's own command registry, between markers, so a flag that changed cannot ship with a skill that recommends the old one. `kettle gen skills --check` exits non-zero when they drift. The generator owns the region and nothing outside it: the frontmatter description, which is what decides whether a skill loads at all, stays hand-written. `use` survives and is the one place `tea` is still named — for releases, webhooks and actions, which kettle does not cover. Its instruction to write `--login "$GITEA_LOGIN"` and let the hook substitute the pin was true until this commit and is now rewritten: `tea` keeps its own configuration, kettle keeps its own, and configuring one configures nothing in the other. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.9 KiB
tea CLI — HELPERS
See ./index.md for global options and common flags shared by all commands.
tea open, o
Open the current repository/context in a web browser.
tea notifications (aliases: notification, n)
Defaults to the current repo; --mine/-m aggregates across all your repos. Fields: id,status,updated,index,type,state,title,repository. Filters: --types/-t {issue|pull|repository|commit}, --states/-s {pinned|unread|read} (default: unread,pinned).
ls, listread, r [all | <id>]unread, u [all | <id>]pin, p [all | <id>]unpin [all | <id>]
tea clone, C <repo-slug> [target-dir]
Clone without requiring a local git install. Accepts slug forms: gitea/tea, tea, gitea.com/gitea/tea, git@gitea.com:gitea/tea, https://gitea.com/gitea/tea, ssh://gitea.com:22/gitea/tea. A host in the slug overrides --login. Options: --depth/-d, --login/-l.
tea api <endpoint>
Authenticated HTTP request to the Gitea API. Endpoints are auto-prefixed with /api/v1/ unless they start with /api/ or http(s)://. Placeholders {owner} and {repo} are filled from the repo context.
--method/-X {GET|POST|PUT|PATCH|DELETE}(default GET; switches to POST automatically when a body is provided)--field/-f key=value— string field on body (repeatable).--Field/-F key=value— typed field (numbers, booleans, null, JSON arrays/objects);@fileor@-(stdin);"null"forces literal string.--data/-d— raw JSON body (@file/@-). Incompatible with-f/-F.--header/-H key:value(repeatable)--include/-i— write status + response headers to stderr.--output/-o <file>— write response body to file (-= stdout). Not the entity commands' format flag:-o jsonhere creates a file namedjsonand prints nothing. The body is already JSON.- Quote the endpoint if it contains
?or&to prevent shell expansion.