Repository navigation
feat: show project skill actions above project chat composers - #30884
Merged
Merged
Conversation
…roject-skills/settings-api
…ject-skills/skill-chips-transcript
… remove buttons keyboard reachable
…s to project skills
…ject chat composers
…h SKILL.md import
…s inside the chat input
…ons gate and cover long names
…hanges and cap chips at eight
…reaks around skill chips
…roject-skills/settings-api
…oject-skills/project-skills-details
…ject-skills/skill-chips-transcript
…he chip remove button comment
… a JSDoc that restates removeSkills
…henever the chat project changes
…roject-skills/settings-api
…roject-skills/invocation-api
…kills/skill-chips-composer
…ject-skills/skill-chips-transcript
…roject-skills/settings-api
…unchanged on settings-only skill edits
Contributor
Docs previewCheck off each page once it's been reviewed. If a page changes in a later push, its checkbox clears automatically so it gets a fresh look. Pages not yet wired into the docs navigation aren't listed here. |
…after main's 000630 and 000631
Co-authored-by: Nick Vigilante <nickvigilante@users.noreply.github.com>
…transcript' into rs-skill-chips-transcript
jaaydenh
added a commit
that referenced
this pull request
Oct 22, 2026
Choosing a skill from the `/` menu now inserts a skill chip into the composer instead of `/alias` text, and the message sends it as a structured `skill-invocation` part (#30861), so chatd loads that exact skill's body into the prompt. - A Lexical `SkillInvocationNode` renders the chip with a remove button; `/clear` and `/compact` still insert as commands, and typed `/name` text that wasn't picked from the menu still goes out as plain text (#31126 turns a typed full alias into a chip). - `buildChatInputContent` emits text and skill parts in document order, a chip-only message can be sent, drafts keep chips, and the new chat form forwards them. - `insertSkill(source, name)` on the composer handle inserts a chip at the caret without duplicating one that's already there. The project action bar later in this stack uses it. - Arrow keys step over chips instead of selecting them. Selecting a chip node dropped the browser selection, so the next keystroke landed at the start of the message; file reference chips had the same bug and get the same fix. - Copy and paste keep chips: copied text includes `/source/name`, pasting skips a chip that's already in the composer, and a chip for a skill this chat can't use is pasted as plain text. Rendering the parts in the transcript and edit flow is in the next PR. Dogfood UAT passed on this stack: picking project, personal and organization skills sends one skill part each and the agent answers from the skill body without calling `read_skill`; the caret, paste and copy cases above, drafts, `/clear`, `/compact` and the 400 for a disabled or deleted skill all behaved as expected. | Chip in the composer | Sent message in the transcript | | --- | --- | | <img alt="Skill chip in the project composer" src="https://raw.githubusercontent.com/coder/coder/assets/pr-30880-skill-chips/pr/composer-chip.png" width="600" /> | <img alt="Skill chip in the sent message with the codeword reply" src="https://raw.githubusercontent.com/coder/coder/assets/pr-30880-skill-chips/pr/transcript-chip.png" width="600" /> | Stack (merge top to bottom): - #30826 - #30827 - #30838 - #30840 - #30854 - #30855 - #30856 - #30861 - #30880 👈 - #30881 - #30882 - #30884 - #31122 - #31126 --------- Co-authored-by: Cursor <cursoragent@cursor.com>
jaaydenh
added a commit
that referenced
this pull request
Oct 22, 2026
Renders `skill-invocation` parts from #30861 in the conversation. A user message shows its skill chips inline with the text, and a message with only a skill invocation is no longer treated as empty. Editing a past message restores its chips in the composer (the editable payload now carries the serialized editor state), optimistic edits keep skill parts, and queued messages show the skill. | Editing a message with a chip | Queued message | | --- | --- | | <img alt="Editing a past message restores its skill chip" src="https://raw.githubusercontent.com/coder/coder/assets/pr-30880-skill-chips/pr/edit-chip.png" width="600" /> | <img alt="Queued message showing its skill" src="https://raw.githubusercontent.com/coder/coder/assets/pr-30880-skill-chips/pr/queued-chip.png" width="600" /> | Stack (merge top to bottom): - #30826 - #30827 - #30838 - #30840 - #30854 - #30855 - #30856 - #30861 - #30880 - #30881 👈 - #30882 - #30884 - #31122 - #31126 --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Nick Vigilante <nickvigilante@users.noreply.github.com>
…after main's 000632
coderd/apidoc/.gen formats swagger.json with biome from site/node_modules, but only the downstream swagger.json rule depended on the site install. When make reached .gen through another target (offlinedocs), formatting was skipped and CI saw an unformatted swagger.json.
jaaydenh
added a commit
that referenced
this pull request
Oct 23, 2026
Adds two per-skill settings that the project skills UI will expose next: - `action` marks a project skill to show as an action button above project chat composers. A `skills_action_project_only` check keeps it to project skills; the personal and organization routes reject `action` with 400. - `model_invocable` (default true, every stored source) controls automatic use. When it's false the skill is left out of `<available-skills>` and `read_skill` reports it as not found, but a structured skill invocation (a chip from the `/` menu or an action) still loads it, as long as the skill is enabled and the chat owner can read it. Workspace skills always count as model-invocable. Migration 000625 adds both columns with defaults, so existing skills keep today's behavior. The list, get, insert and update queries, `codersdk.SkillMetadata` and the create/update requests carry both fields, and the audit table tracks them. `coderd/x/chatd/ARCHITECTURE.md` gets TODO notes for the author. **NOTE**: the migration adds two columns with constant defaults and a CHECK constraint to `skills`. Stack (merge top to bottom): - #30826 - #30827 - #30838 - #30840 - #30854 - #30855 - #30856 - #30861 - #30880 - #30881 - #30882 👈 - #30884 - #31122 - #31126 --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Nick Vigilante <nickvigilante@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Exposes the two project skill settings from #30882 and adds project actions above project chat composers.
disable-model-invocation: truestarts automatic use off, and a settings-only change saves without rewriting SKILL.md. The skills list shows "Action" and "Manual only" badges.ProjectSkillActionsbar shows enabled action skills sorted by name: up to three buttons (description as tooltip), the rest under "More". Clicking one inserts that skill's chip into the composer throughinsertSkill; it doesn't start a chat, and a chip that's already there isn't duplicated. It renders nothing while loading, on error, or with no actions.chat-projectsexperiment. The list refetches when the window regains focus and after a send fails because a skill is no longer available.Dogfood UAT passed: three buttons plus More on the project page and in ongoing chats, chips inserted without creating a chat, the agent answering from action-invoked skills (including a manual-only skill that
read_skillcan't load), the bar updating after settings changes and after a deleted skill's send failed, settings-only saves leaving SKILL.md unchanged, and no bar outside projects.Stack (merge top to bottom):