Skip to content

feat: show project skill actions above project chat composers - #30884

Merged
jaaydenh merged 300 commits into
mainfrom
chat-project-skills/actions-site
Oct 23, 2026
Merged

jaaydenh merged 300 commits into
mainfrom
chat-project-skills/actions-site

Conversation

@jaaydenh

@jaaydenh jaaydenh commented Oct 15, 2026 •

Copy link
Copy Markdown
Collaborator

Exposes the two project skill settings from #30882 and adds project actions above project chat composers.

  • The project skill editor gets two switches, "Show as action" and "Agents can use it automatically". New skills start with actions off and automatic use on, importing a SKILL.md with disable-model-invocation: true starts automatic use off, and a settings-only change saves without rewriting SKILL.md. The skills list shows "Action" and "Manual only" badges.
  • A new ProjectSkillActions bar 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 through insertSkill; 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.
  • The bar appears above the project page's new-chat composer and above the composer of ongoing project chats (subagents use the root chat's project). It's hidden when the composer is read-only and behind the chat-projects experiment. The list refetches when the window regains focus and after a send fails because a skill is no longer available.
  • The extending agents docs describe both settings.

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_skill can'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.

Project page actions with More open Action chip in an ongoing chat
Project page composer with three action buttons and More open Ongoing project chat with an action chip inserted
Editor switches List badges
Project skill editor with the two switches Project skills list with Action and Manual only badges

Stack (merge top to bottom):

@github-actions

github-actions Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Docs preview

Check 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.

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>
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.
Base automatically changed from chat-project-skills/settings-api to main October 23, 2026 12:32
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>
@jaaydenh
jaaydenh merged commit 63f3bde into main Oct 23, 2026
30 checks passed
@jaaydenh
jaaydenh deleted the chat-project-skills/actions-site branch October 23, 2026 12:53
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 23, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants