The harness for real files.
The model thinks; a kit lets it see, edit, run, check, and undo a real file.
A kit is an MCP server that follows KHP’s tool conventions, so any MCP-capable agent can use any kit.
Scene 0.1.0: the reference implementation’s 3D scene kit, made by the protocol’s maintainer. Declares the basic tier.
Call log
- scene_inspect (Still life.kscene, preview: true, target: {"view":"camera"}, maxSize: 1200) ok Opened `Still life.kscene`: 1920 × 1080
- scene_commands (Still life.kscene, query: "material keyframe parent") ok No command has every word of `material keyframe parent`; 30 have some of them; showing the best 12.
- scene_run (Still life.kscene, [material.set, add.icoSphere, material.assign, add.empty, object.parent, anim.insertKey, object.transform, anim.insertKey, anim.setInterpolation]) ok Ran 9 commands on `Still life.kscene` (saved): 1920 × 1080
- scene_check (Still life.kscene) ok Checked `Still life.kscene`: no errors, no warnings, 1 note.
- scene_inspect (Still life.kscene, preview: true, target: {"view":"camera"}, maxSize: 1200) ok Opened `Still life.kscene`: 1920 × 1080
- scene_inspect (Still life.kscene, preview: true, target: {"range":[0,3.75],"frames":6}, maxSize: 1200) ok Opened `Still life.kscene`: 1920 × 1080
Preview
01 Open the scene: its objects, materials, lights and camera as JSON, and the view through the camera as the kit renders it.
02 Search the command catalogue for materials, parenting and keyframes.
scene_commands(Still life.kscene, query: "material keyframe parent") · 5 found
- object.parent Parent Parents `objects` (names or ids; the selection without it) to `parent`, keeping their world transform.
- object.clearParent Clear Parent Clears the parent of `objects` (names or ids; the selection without it), keeping their world transform.
- object.parentArmature Parent to Armature Parents `objects` (names or ids; the selection without it) to `armature` with automatic, envelope or empty weights.
- material.new New Material Creates a material with base color, metallic and roughness and answers its id.
- material.set Change Material Changes material `material` (name or id): base color, metallic, roughness, emission, alpha, transmission and more.
03 The request: make the ball glossy coral, add a small faceted pebble, and put the objects on a turntable that turns once in four seconds. This kit keeps no drafts, so the edit goes to the file, saved once.
scene_run → 9 steps · saved
✓ material.set ✓ add.icoSphere ✓ material.assign ✓ add.empty ✓ object.parent ✓ anim.insertKey ✓ object.transform ✓ anim.insertKey ✓ undefined
changes: 2 created, 5 changed
04 Check the scene.
scene_check → 1 note
scene.unusedMaterial: Material Material is not used by any object → fix: material.delete
05 Look through the camera again. The clip is 48 previews of the turn, every other frame, each rendered by the kit.
06 Look at the motion: six frames from the four-second turn, in one picture the kit draws.
Call log
- scene_inspect (Still life.kscene, preview: true, target: {"view":"camera"}, maxSize: 1200) ok Opened `Still life.kscene`: 1920 × 1080
- scene_commands (Still life.kscene, query: "material keyframe parent") ok No command has every word of `material keyframe parent`; 30 have some of them; showing the best 12.
- scene_run (Still life.kscene, [material.set, add.icoSphere, material.assign, add.empty, object.parent, anim.insertKey, object.transform, anim.insertKey, anim.setInterpolation]) ok Ran 9 commands on `Still life.kscene` (saved): 1920 × 1080
- scene_check (Still life.kscene) ok Checked `Still life.kscene`: no errors, no warnings, 1 note.
- scene_inspect (Still life.kscene, preview: true, target: {"view":"camera"}, maxSize: 1200) ok Opened `Still life.kscene`: 1920 × 1080
- scene_inspect (Still life.kscene, preview: true, target: {"range":[0,3.75],"frames":6}, maxSize: 1200) ok Opened `Still life.kscene`: 1920 × 1080
Preview
01 Open the scene: its objects, materials, lights and camera as JSON, and the view through the camera as the kit renders it.
02 Search the command catalogue for materials, parenting and keyframes.
scene_commands(Still life.kscene, query: "material keyframe parent") · 5 found
- object.parent Parent Parents `objects` (names or ids; the selection without it) to `parent`, keeping their world transform.
- object.clearParent Clear Parent Clears the parent of `objects` (names or ids; the selection without it), keeping their world transform.
- object.parentArmature Parent to Armature Parents `objects` (names or ids; the selection without it) to `armature` with automatic, envelope or empty weights.
- material.new New Material Creates a material with base color, metallic and roughness and answers its id.
- material.set Change Material Changes material `material` (name or id): base color, metallic, roughness, emission, alpha, transmission and more.
03 The request: make the ball glossy coral, add a small faceted pebble, and put the objects on a turntable that turns once in four seconds. This kit keeps no drafts, so the edit goes to the file, saved once.
scene_run → 9 steps · saved
✓ material.set ✓ add.icoSphere ✓ material.assign ✓ add.empty ✓ object.parent ✓ anim.insertKey ✓ object.transform ✓ anim.insertKey ✓ undefined
changes: 2 created, 5 changed
04 Check the scene.
scene_check → 1 note
scene.unusedMaterial: Material Material is not used by any object → fix: material.delete
05 Look through the camera again. The clip is 48 previews of the turn, every other frame, each rendered by the kit.
06 Look at the motion: six frames from the four-second turn, in one picture the kit draws.
Call log
- motion_inspect (Concert title.kmotion, preview: true, target: {"range":[0,3.9],"frames":6}, maxSize: 1200) ok Opened `Concert title.kmotion`: 1280 × 720
- motion_commands (Concert title.kmotion, query: "text preset") ok 2 commands have every word of `text preset`, 61 more some of them; showing the best 12.
- motion_run (Concert title.kmotion, draft: true, [layer.applyTextPreset, layer.setText, layer.applyTextPreset]) ok Ran 3 commands on your draft of `Concert title.kmotion`; the file is unchanged until the person merges the draft.
- motion_check (Concert title.kmotion, draft: true) ok Checked your draft of `Concert title.kmotion`: no errors, no warnings, 3 notes.
- motion_inspect (Concert title.kmotion, preview: true, draft: true, target: {"range":[0,3.9],"frames":6}, maxSize: 1200) ok Opened your draft of `Concert title.kmotion`: 1280 × 720
- motion_export (Concert title.kmotion, draft: true, format: "mp4", to: "after.mp4") ok Exported your draft of `Concert title.kmotion` as MP4 to `after.mp4` (446953 bytes).
- motion_draft_ready (Concert title.kmotion) ok Your draft of `Concert title.kmotion` is ready for review; the person will merge or discard it.
Preview
01 Open the project: its composition and layers as JSON, each with an id, and six frames of the four seconds as the kit renders them. The clip is the kit’s own export of the project as it is.
02 Search the command catalogue for text animations.
motion_commands(Concert title.kmotion, query: "text preset") · 5 found
- layer.applyTextPreset Apply Text Animation Preset Applies a built-in text animation to a text `layer`: `preset` typewriter, fadeUpCharacters, bounceInWords, trackingIn, scramble, blurIn,…
- text.presets Text Animation Presets Lists the built-in text animation presets (id, name, description) layer.applyTextPreset accepts, the promo presets included.
- anim.browsePresets Browse Presets Editor window only: opens the animation preset browser.
- paint.brushPreset Brush Preset Chooses a brush preset for later paint strokes by index or name (`preset`); without `preset` returns the preset names.
- paint.presets Brush Presets Lists the brush presets with index, name, diameter, angle, roundness, hardness and spacing.
03 The request: give the title an entrance, change the date and show it in amber, and bring the date in after the title. In a draft.
motion_run → 3 steps · draft
✓ layer.applyTextPreset ✓ layer.setText ✓ layer.applyTextPreset
changes: 3 changed
− motion.static-text (resolved)
− motion.static-text (resolved)
04 Check the draft.
motion_check → 3 notes
motion.flat-background: The frame is flat (one colour or a linear gradient, no radial light or vignette), which reads as plain; a radial ramp of the background's own colour, lighter behind the subject, gives it depth. → fix: effect.apply
motion.no-depth: No element has a glow or a shadow ("Date", "Title"), so everything sits flat on the background; a soft outer glow sized for the frame lifts them. → fix: layer.style.add
motion.thin-type: "Date" is set in a light or regular weight, which reads faint on video; use Medium or heavier. → fix: layer.setText
05 Look at six frames of the draft: the title rises out of a blur word by word, and the date follows.
06 Export the draft as a video: the kit renders every frame. This is the clip shown here.
07 Hand the draft to the person, who merges or discards it.
motion_draft_ready → ready
Your draft of `Concert title.kmotion` is ready for review; the person will merge or discard it.
Call log
- photo_inspect (Hills at dusk.psd, preview: true, maxSize: 1200) ok Opened `Hills at dusk.psd`: 1200 x 800 px, Rgb, 8-bit, 7 layers
- photo_commands (Hills at dusk.psd, query: "hue saturation adjustment layer") ok 4 commands have every word of `hue saturation adjustment layer`, 492 more some of them; showing the best 12.
- photo_run (Hills at dusk.psd, draft: true, [layer.newAdjustmentLayer.hueSaturation, image.crop, type.create]) ok Ran 3 commands on your draft of `Hills at dusk.psd`; the file is unchanged until the person merges the draft.
- photo_check (Hills at dusk.psd, draft: true) ok Checked your draft of `Hills at dusk.psd`: the kit found nothing wrong.
- photo_inspect (Hills at dusk.psd, draft: true, preview: true, maxSize: 1200) ok Opened your draft of `Hills at dusk.psd`: 1200 x 675 px, Rgb, 8-bit, 9 layers
- photo_draft_ready (Hills at dusk.psd) ok Your draft of `Hills at dusk.psd` is ready for review; the person will merge or discard it.
Preview
01 Open the image: its layers as JSON, each with an id, and the picture as the kit renders it.
02 Search the command catalogue for an adjustment that changes the colours without touching the layers under it.
photo_commands(Hills at dusk.psd, query: "hue saturation adjustment layer") · 5 found
- layer.newAdjustmentLayer.hueSaturation Hue/Saturation… Adds an editable Hue/Saturation adjustment layer above the active layer, which shifts `hue` (−180–180), `saturation` and `lightness` for…
- image.adjustments.hueSaturation Hue/Saturation… Hue/Saturation on the active pixel layer (inside the selection), destructively: shifts `hue` (−180–180), `saturation` and `lightness` for…
- layer.newAdjustmentLayer.vibrance Vibrance… Adds an editable Vibrance adjustment layer above the active layer, which raises saturation mostly in muted colors and protects skin tones…
- image.adjustments.vibrance Vibrance… Vibrance on the active pixel layer (inside the selection), destructively: raises saturation mostly in muted colors and protects skin tones…
- image.adjustments.replaceColor Replace Color… Selects pixels near `color` within `fuzziness` (0–200) and shifts their `hue`, `saturation` and `lightness`; destructive.
03 The request: a cool morning version, cropped to 16:9, with a title. An adjustment layer shifts the colours and stays editable; the crop and the title follow. All in a draft.
photo_run → 3 steps · draft
✓ layer.newAdjustmentLayer.hueSaturation ✓ image.crop ✓ type.create
changes: 2 created, 7 changed
04 Check the draft.
photo_check → No diagnostics
05 Look at the image again as rendered now.
06 Hand the draft to the person, who merges or discards it. The layers stay editable in the .psd.
photo_draft_ready → ready
Your draft of `Hills at dusk.psd` is ready for review; the person will merge or discard it.
Call log
- slide_inspect (Project update.pptx, target: {"slide":3}, preview: true) ok Opened `Project update.pptx`: 4 slides, 960 × 540 pt
- slide_commands (Project update.pptx, query: "chart data theme") ok No command has every word of `chart data theme`; 23 have some of them; showing the best 12.
- slide_run (Project update.pptx, draft: true, [chart.data, design.theme]) diagnostics Ran 2 commands on your draft of `Project update.pptx`; the file is unchanged until the person merges the draft.
- slide_check (Project update.pptx, draft: true) diagnostics Checked your draft of `Project update.pptx`: no errors, 2 warnings, no notes.
- slide_run (Project update.pptx, draft: true, [design.fonts]) ok Ran 1 commands on your draft of `Project update.pptx`; the file is unchanged until the person merges the draft.
- slide_inspect (Project update.pptx, target: {"slide":3}, draft: true, preview: true) ok Opened your draft of `Project update.pptx`: 4 slides, 960 × 540 pt
- slide_draft_ready (Project update.pptx) ok Your draft of `Project update.pptx` is ready for review; the person will merge or discard it.
Preview
01 Open the deck on slide 3 and look at it: the shapes as JSON, each with a stable id, and the slide as the kit renders it.
02 Search the kit’s command catalogue for the chart’s data and the theme, instead of loading one tool per command.
slide_commands(Project update.pptx, query: "chart data theme") · 5 found
- chart.data Edit Data Replaces the categories and series values (and any series color, type or waterfall totals given) of chart `id` (else the selected chart).
- chart.type Change Chart Type Changes the chart `id` (else the selected chart) to another chart type, keeping its data; an unknown type is refused.
- chart.options Chart Elements Sets which chart elements show (title, legend position, data labels, gridlines), the colour palette (colorful1–4, monochrome1–13; others…
- drawing.chart Change Chart Changes a chart drawing object's kind, title, legend, data labels or data.
- design.theme Themes Applies a theme by name (see `design.themes`) to the whole presentation.
03 Add this week to the chart and apply the Harbor theme, in a draft: the file stays as it was until a person merges. The answer already reports new diagnostics.
slide_run → 2 steps · draft
✓ chart.data ✓ design.theme
changes: 8 changed
+ slide.font-substituted
+ slide.font-substituted
04 Check the draft. Harbor’s fonts are not available to the kit, so the slides would be drawn with a stand-in. Each finding has a stable code.
slide_check → 2 warnings
slide.font-substituted: The font "Merriweather" is not available here; its text is drawn with "Inter", so its lines may wrap differently, and apps without it substitute their own font; use an installed family for the same look everywhere.
slide.font-substituted: The font "Open Sans" is not available here; its text is drawn with "Inter", so its lines may wrap differently, and apps without it substitute their own font; use an installed family for the same look everywhere.
05 Keep Harbor’s colours but use a font the kit has. The answer says both warnings are resolved.
slide_run → 1 steps · draft
✓ design.fonts
changes: 8 changed
− slide.font-substituted (resolved)
− slide.font-substituted (resolved)
06 Look at the slide again as rendered now: five weeks, in the new theme’s colours.
07 Hand the draft to the person. Merging or discarding it is theirs; no tool does it.
slide_draft_ready → ready
Your draft of `Project update.pptx` is ready for review; the person will merge or discard it.
Call log
- sheet_inspect (Budget.xlsx, target: {"range":"A1:E7"}, preview: true, scale: 2) ok Opened `Budget.xlsx`: 1926 × 1921
- sheet_commands (Budget.xlsx, query: "set values percentage format") ok No command has every word of `set values percentage format`; 181 have some of them; showing the best 12.
- sheet_run (Budget.xlsx, draft: true, [range.setValues, home.bold, home.fillColor, home.numberFormat]) diagnostics Ran 4 commands on your draft of `Budget.xlsx`; the file is unchanged until the person merges the draft.
- sheet_inspect (Budget.xlsx, target: {"range":"A1:E7"}, draft: true, preview: true, scale: 2) ok Opened your draft of `Budget.xlsx`: 1926 × 1921
- sheet_check (Budget.xlsx, draft: true) diagnostics Checked your draft of `Budget.xlsx`: 1 error, no warnings, no notes.
- sheet_run (Budget.xlsx, draft: true, [cell.set]) ok Ran 1 commands on your draft of `Budget.xlsx`; the file is unchanged until the person merges the draft.
- sheet_inspect (Budget.xlsx, target: {"range":"A1:E7"}, draft: true, preview: true, scale: 2) ok Opened your draft of `Budget.xlsx`: 1926 × 1921
- sheet_draft_ready (Budget.xlsx) ok Your draft of `Budget.xlsx` is ready for review; the person will merge or discard it.
Preview
01 Open the workbook and look at the budget: cells and formulas as JSON, and the range as the kit renders it.
02 Search the kit’s command catalogue for writing a block of cells and a percentage format.
sheet_commands(Budget.xlsx, query: "set values percentage format") · 5 found
- home.numberFormat Number Format Sets how numbers in a range display: a named format (Currency, Percentage, Short Date, Text…) or a custom format code such as 0.00%.
- range.setValues Set Values Writes a block of values starting at the range's top-left cell, one inner list per row; strings starting with = become formulas.
- pivot.valueSettings Value Field Settings Changes a pivot table value field's summary function, caption or show-as calculation (percent of total, running total…).
- home.conditionalFormat Conditional Formatting Adds a conditional formatting rule to a range (cell value with an operator, formula, text, duplicates, top/bottom, dates, data bar, colour…
- chart.formatSelection Format Selection Sets the colour of one series of a chart, by its 0-based index.
03 The request: add a column with the share of each plan already spent. The formulas go to a draft; the file stays as it was until a person merges.
sheet_run → 4 steps · draft
✓ range.setValues ✓ home.bold ✓ home.fillColor ✓ home.numberFormat
changes: 8 created, 2 changed
+ sheet.formula-error
04 Look at the draft: Equipment was never planned, so its share divides by zero.
05 Check the draft. The kit reports the formula error with a stable code and the cell it is in.
sheet_check → 1 error
sheet.formula-error: Sheet1!E6 evaluates to #DIV/0!: =C6/B6
06 Guard the formula instead of deleting it: an item with no plan says so. The answer says the error is resolved.
sheet_run → 1 steps · draft
✓ cell.set
changes: 2 changed
− sheet.formula-error (resolved)
07 Look at the draft again as rendered now.
08 Hand the draft to the person, who merges or discards it.
sheet_draft_ready → ready
Your draft of `Budget.xlsx` is ready for review; the person will merge or discard it.
Call log
- doc_inspect (Office move.docx, preview: true, maxSize: 1200) ok Opened `Office move.docx`: 692 × 872
- doc_commands (Office move.docx, query: "heading style") ok 5 commands have every word of `heading style`, 54 more some of them; showing the best 12.
- doc_run (Office move.docx, draft: true, [select.range, para.heading1, select.range, para.heading2, select.range, text.newParagraph, text.insert]) ok Ran 7 commands on your draft of `Office move.docx`; the file is unchanged until the person merges the draft.
- doc_check (Office move.docx, draft: true) ok Checked your draft of `Office move.docx`: no errors, no warnings, 2 notes.
- doc_inspect (Office move.docx, draft: true, preview: true, maxSize: 1200) ok Opened your draft of `Office move.docx`: 692 × 872
- doc_draft_ready (Office move.docx) ok Your draft of `Office move.docx` is ready for review; the person will merge or discard it.
Preview
01 Open the memo: its paragraphs as JSON, each with an index and a stable id, and the page as the kit lays it out.
02 Search the command catalogue for heading styles: a heading should be a style, not just bold text.
doc_commands(Office move.docx, query: "heading style") · 5 found
- para.heading1 Heading 1 Applies the Heading 1 style to the selected paragraphs.
- para.heading2 Heading 2 Applies the Heading 2 style to the selected paragraphs.
- para.heading3 Heading 3 Applies the Heading 3 style to the selected paragraphs.
- para.style Apply Style Applies a paragraph style (by name or id, such as Heading 1 or Quote) to the selected paragraphs; styles.list names them.
- design.styleSet Style Set Applies a style set (basic, lines, shaded, casual, centered, minimalist, title) that restyles headings and body text.
03 The request: make the two headings real headings and add a line about parking. The edits go to a draft; the file stays as it was until a person merges.
doc_run → 7 steps · draft
✓ select.range ✓ para.heading1 ✓ select.range ✓ para.heading2 ✓ select.range ✓ text.newParagraph ✓ text.insert
changes: 1 created, 3 changed
+ doc.font-substituted
04 Check the draft. The only finding is a note: the theme font is drawn with a substitute here. The file keeps its font, so there is nothing to fix.
doc_check → 2 notes
doc.font-substituted: The font "Aptos" is not available here: its text is drawn with a substitute, so lines may break differently.
doc.font-substituted: The font "Aptos Display" is not available here: its text is drawn with a substitute, so lines may break differently.
05 Look at the draft as laid out now: two headings and the new paragraph.
06 Hand the draft to the person, who merges or discards it.
doc_draft_ready → ready
Your draft of `Office move.docx` is ready for review; the person will merge or discard it.
Call log
- pdf_inspect (Site visit notes.pdf, preview: true, maxSize: 1200) ok Opened `Site visit notes.pdf`: 692 × 872
- pdf_commands (Site visit notes.pdf, query: "highlight comment") ok 2 commands have every word of `highlight comment`, 16 more some of them; showing the best 12.
- pdf_run (Site visit notes.pdf, draft: true, [comment_add, comment_add]) ok Ran 2 commands on your draft of `Site visit notes.pdf`; the file is unchanged until the person merges the draft.
- pdf_check (Site visit notes.pdf, draft: true) ok Checked your draft of `Site visit notes.pdf`: no errors, no warnings, 2 notes.
- pdf_inspect (Site visit notes.pdf, draft: true, preview: true, maxSize: 1200) ok Opened your draft of `Site visit notes.pdf`: 692 × 872
- pdf_draft_ready (Site visit notes.pdf) ok Your draft of `Site visit notes.pdf` is ready for review; the person will merge or discard it.
Preview
01 Open the PDF: its pages as JSON, and page 1 as the kit renders it.
02 Search the command catalogue for comments: a highlight and a note are annotations, not changes to the page text.
pdf_commands(Site visit notes.pdf, query: "highlight comment") · 5 found
- comment_add Add a comment Add a comment as Acrobat's commenting tools do.
- doc_compare_mark Mark differences as comments Add the differences from other (older) to doc (newer) as comments in doc: highlights over replaced (blue) and inserted (green) text, notes…
- comment_list List comments Every comment (annotation other than links, form widgets and pop-ups) with its page, index, id, type, author, text, date, rectangle,…
- comment_reply Reply to a comment Add a reply to a comment's thread.
- comment_set_status Set a comment's status Set a comment's review status (Acrobat: Set status), recorded as a status reply.
03 The request: flag the stairwell stain for the roofer. A highlight finds the text on the page, and a note says what to do. Both go to a draft.
pdf_run → 2 steps · draft
✓ comment_add ✓ comment_add
changes: 2 created, 1 changed
04 Check the draft. Only notes: the text uses standard fonts that every viewer supplies.
pdf_check → 2 notes
pdf.font-not-embedded: The font Helvetica-Bold is not embedded; it is one of the standard 14 fonts, which viewers supply.
pdf.font-not-embedded: The font Helvetica is not embedded; it is one of the standard 14 fonts, which viewers supply.
05 Look at the page again as rendered now: the highlight and the note icon.
06 Hand the draft to the person, who merges or discards it.
pdf_draft_ready → ready
Your draft of `Site visit notes.pdf` is ready for review; the person will merge or discard it.
Call log
- vector_inspect (Open day card.kvector, preview: true) ok Opened `Open day card.kvector`: 800 × 500
- vector_commands (Open day card.kvector, query: "set fill rectangle") ok No command has every word of `set fill rectangle`; 216 have some of them; showing the best 12.
- vector_run (Open day card.kvector, draft: true, [paint.setFill, shape.rectangle, text.create]) ok Ran 3 commands on your draft of `Open day card.kvector`; the file is unchanged until the person merges the draft.
- vector_run (Open day card.kvector, draft: true, [paint.setFill, paint.setStroke]) ok Ran 2 commands on your draft of `Open day card.kvector`; the file is unchanged until the person merges the draft.
- vector_check (Open day card.kvector, draft: true) ok Checked your draft of `Open day card.kvector`: the kit found nothing wrong.
- vector_inspect (Open day card.kvector, draft: true, preview: true) ok Opened your draft of `Open day card.kvector`: 800 × 500
- vector_draft_ready (Open day card.kvector) ok Your draft of `Open day card.kvector` is ready for review; the person will merge or discard it.
Preview
01 Open the card: the artboard, layers and objects as JSON, each with an id, and the card as the kit renders it.
02 Search the command catalogue for the fill and for a rectangle.
vector_commands(Open day card.kvector, query: "set fill rectangle") · 5 found
- object.slice.setRect Set Slice Rectangle Moves or resizes a user slice.
- paint.setFill Fill Sets the fill of the selection or ids (or the default fill) to a colour, a swatch, a gradient, a pattern or none; a global or spot swatch…
- path.setFillRule Fill Rule Sets the fill rule (non-zero or even-odd) of the selected or given paths and compound paths.
- shape.rectangle Rectangle Draws a rectangle at x, y with width and height (optional corner radius and rotation about its centre) in the current layer with the…
- path.rectCut Rectangle Cut Crops the selected paths to a rectangle as real geometry (not a clipping mask).
03 The request: make the circle a warm sun and add a “Free entry” badge. The edits go to a draft; the file stays as it was until a person merges.
vector_run → 3 steps · draft
✓ paint.setFill ✓ shape.rectangle ✓ text.create
changes: 2 created, 1 changed
04 Give the new badge the sun’s colour, by the id the last answer gave it.
vector_run → 2 steps · draft
✓ paint.setFill ✓ paint.setStroke
changes: 1 changed
05 Check the draft: nothing off the artboard, no missing fonts.
vector_check → No diagnostics
06 Look at the card again as rendered now.
07 Hand the draft to the person, who merges or discards it.
vector_draft_ready → ready
Your draft of `Open day card.kvector` is ready for review; the person will merge or discard it.
Call log
- docx_inspect (Report.docx) ok 3 body paragraphs; 1 body tables.
- docx_commands (Report.docx, query: "set text") ok paragraph.set-text, table.set-cell
- docx_run (Report.docx, [paragraph.set-text, table.set-cell]) error not-found at step 1, rolled back 1 No such table cell; call docx_inspect for row and column indexes counted from 0.
- docx_run (Report.docx, [paragraph.set-text, table.set-cell, table.set-cell]) ok 3 steps, saved
- docx_check (Report.docx) ok 0 diagnostics
- docx_inspect (Report.docx) ok 3 body paragraphs; 1 body tables.
Preview
01 Read the document as JSON before touching it.
| Task | Status |
| Collect figures | In progress |
| Write summary | Not started |
02 Search the command catalogue instead of loading one tool per command.
docx_commands(Report.docx, query: "set text") · 2 found
- paragraph.set-text Set paragraph text Replace one body paragraph's inline content and run formatting with plain text; keep its paragraph style.
- table.set-cell Set table cell text Replace a body table cell's content with plain text. Merged cells are refused.
03 An edit with a wrong row index (the table has rows 0 to 2). The kit refuses it with a code and a fix, and rolls back the step that had already succeeded.
| Task | Status | |
| Collect figures | In progress | |
| Write summary | Not started | |
| 3 | ? |
|---|
docx_run → not-found · step 1
No such table cell; call docx_inspect for row and column indexes counted from 0.
rolled back: paragraph.set-text (step 0)
04 The same edit with the right address. All steps apply together, then the file is saved once.
| Task | Status |
| Collect figures | Done |
| Write summary | In review |
docx_run → 3 steps · saved
✓ paragraph.set-text ✓ table.set-cell ✓ table.set-cell
Report.docx → 4512d38
05 Ask the kit to check the saved file.
| Task | Status |
| Collect figures | Done |
| Write summary | In review |
docx_check → No diagnostics
Package opened. No layout, style, accessibility or fidelity checks are implemented at this basic tier.
06 Read it again to confirm what changed.
| Task | Status |
| Collect figures | Done |
| Write summary | In review |
One protocol, 16 kinds of file
These are the kits of the reference implementation, built by the protocol’s maintainer, Kition. All of them have public source. khp’s repository adds a small example kit that wraps python-docx. Anyone can build a kit for a kind of file: implement a kit →
- Note basic .md.markdown
- Table basic .ktable
- Board basic .kboard
- Doc basic .docx opens .html .htm
- Sheet basic .xlsx.xlsm opens .xltx .xltm .xls .xlt +5
- Slide basic .kslide.pptx
- PDF basic .pdf
- HTML basic .html.htm
- Photo basic .psd.psb.kphoto
- Vector basic .kvector opens .svg .ai .eps
- Layout basic .klayout opens .idml
- Design agent-ready .kdesign opens .fig .sketch
- Film basic .kfilm
- Motion basic .kmotion
- CAD basic .dxf
- Scene basic .kscene
From each kit’s kit.json, read 2026-11-18 · github.com/KitionAI/kition-<kit>
01 · The gap
Agents have a harness for code. Files have none.
A coding agent does real work because its harness lets the model read code, edit it, run it, test it, and roll back what went wrong. Slides, spreadsheets, documents, PDFs, images, video projects, and drawings have no such environment. A kit is the harness for one kind of file.
01 Observe
Code Read the source
File today A format made for storage
The document as JSON, typed objects, rendered previews
_inspect_query_hit
02 Act
Code Edit, run a shell
File today Scripts that guess at the format
Commands with parameter schemas; batches of object edits
_commands_run_batch
03 Execute
Code Compiler, runtime
File today Computing and layout locked in desktop apps
The kit’s own engine recalculates, lays out, and renders
engine
04 Verify
Code Tests, type checks
File today Nothing says whether the edit was right
Diagnostics the kit reports about the document
_check
05 Recover
Code Branches, revert
File today The edit lands in the file
Drafts a person reviews and merges
_draft_readyperson merges
KHP says only how an AI agent uses a kit. How a kit is built inside (its engine, data model, editor, or storage) is its own business. Why KHP →
02 · Evidence
What the pilots measured
khp-bench gives an agent the same file tasks through a KHP kit, through a flat MCP server with one tool per command over the same engine, and through plain Python scripts, and grades the files it leaves behind.
fewer tool-definition tokens than a flat MCP server, for one slide kit
With tool search off. With Claude Code’s tool search on, the gap is smaller.
Benchmark · tool definitions
fewer for three kits behind one KHP tool set, against 1,023 flat tools
The gap grows with the number of kits.
Benchmark · tool definitions
clean edits when a conversation comes back to an earlier slide
Flat MCP: 18/30 (p = 0.0001). The cause is addressing: a flat server that names the slide did as well.
Benchmark · coming back to an earlier slide
layout tasks passed under both renderers, with previews
The same kit without images: 42/50.
Benchmark · layoutThese are pilot results, not a finished benchmark: few tasks, mostly one model in one agent harness. On small edits to one file the tool layer did not change success. The benchmark is run by the protocol’s maintainer, who also makes the reference implementation. Read the limits →
03 · The protocol
What KHP defines
Three roles. The kit is an MCP server for one kind of file, started on a workspace folder, with a manifest. The agent harness runs a model, its tools, and its loop, and connects to kits over MCP. The person starts the agent, reviews its drafts, and merges or discards them.
- 01 request The person asks for a change to plan.gantt.
- 02 gantt_inspect → document JSON The agent reads the plan as JSON.
- 03 gantt_commands → schemas It finds the commands it needs.
- 04 gantt_run → ok · draft It moves three tasks, in a draft beside the file.
- 05 gantt_check → dependency-cycle · fix The check reports a dependency cycle, with a fix hint.
- 06 gantt_run → ok It runs the fix.
- 07 gantt_check → no errors It checks again: no errors.
- 08 gantt_draft_ready → ready It asks the person to review the draft.
- 09 review The person compares the draft with the file.
- 10 merge Only the person merges. The agent has no merge tool.
A3 · A22 · A16
Tools
The same tools for every kit, whatever its command set. Optional ones only when the kit has what they need.
- <prefix>_inspectobserve
- _commands · _runact
- _checkverify
- _create · _exportact
- _draft_ready · _draft_reopenrecover
- _query · _batch · _hitoptional
A18 · A21
Results
The document as JSON, rendered previews, diagnostics with stable codes, and structured error codes.
diagnostic { code "slide.text-overflow" severity "warning" target { slide: 3 } message … fix? { command, params } }
A14 · A11 · A29 · A10
Rules
- A14Only a person merges or discards a draft.
- A11An agent’s edits are attributed to the person who started it.
- A29File parameters stay inside the workspace.
- A10Every call is logged.
K2 · K19 · K20
Manifest and tiers
A minimal kit.json, also served as an MCP resource, names the tier a kit claims. khp check tests it.
"khp": "1.0", "id": "org.example.docx-python", "agent": { "prefix": "docx", … }, "level": "basic"
Three tiers, each including the one before
Defined in section 10 of the tools page; Tiers and khp check explains how they are tested.
-
Basic
basicInspect, commands, run, and check; a schema for every agent-facing command; structured errors; the safety rules. Wrapping an existing file library is enough.
-
Agent-ready
agent-readyWorks with no editor open; real previews and checks with a catalogue; create and export; query and batch when the kit has an object model; no network.
-
Agent-ready complete
agent-ready-completeThe layout answer for paginated kits; a guide for models; edits that address only what they change; runs sandboxed.
04 · Cases
What it looks like in use
examples/docx-python · basic
A file library becomes a kit
docx_run → ok · 3 steps, saved
khp’s public example wraps python-docx in an MCP server: six tools, the basic tier, atomic edits, and paths that cannot leave the workspace.
addressing · A46
Coming back to an earlier slide
id reused after the current slide moved
When a conversation returns to an earlier slide, an interface that depends on a hidden “current slide” edits the wrong one. Absolute addresses avoid it.
unified entry · kit_<action>
Three kinds of file, one tool set
kit_inspect → routed by file extension
Slides, a spreadsheet, and a document behind one fixed set of tools. The tool definitions in the context do not grow with the number of commands.
05 · Start
Start where you are
A
Connect a kit to your agent
Register a kit as an MCP server. This uses khp’s example kit, after the setup in its README.
Claude Code
claude mcp add docx -- "$KHP_PYTHON_ENV/bin/python" -B \
"$REPO_ROOT/examples/docx-python/server.py" \
--workspace "$WORKSPACE" --actor "Your Name" Codex
# ~/.codex/config.toml (absolute paths)
[mcp_servers.docx]
command = "/path/to/venv/bin/python"
args = ["-B", "/path/to/khp/examples/docx-python/server.py",
"--workspace", "/path/to/workspace", "--actor", "Your Name"] Other MCP clients
{
"mcpServers": {
"docx": {
"command": "/path/to/venv/bin/python",
"args": ["-B", "/path/to/khp/examples/docx-python/server.py",
"--workspace", "/path/to/workspace", "--actor", "Your Name"]
}
}
} B
Build a kit
Wrap your file library, then test it with khp check. The checker is not on npm yet: build it from a khp checkout.
git clone https://github.com/kitharness/khp && cd khp
pnpm --dir tools/conformance install --frozen-lockfile
pnpm --dir tools/conformance build
node tools/conformance/dist/cli.js check \
--kit "my-kit --workspace {workspace}" \
--package <kit-package> --level basic C
Read the paper and the benchmark
The specification is four pages in the public repository. The paper explains the design; the benchmark gives the method, the pilot results, and their limits.
git clone https://github.com/kitharness/khp
ls khp/spec
# agent.md conformance.md index.md manifest.md 06 · Status
Where KHP stands
- Version
- KHP 1.1, edition 2026.11, draft
- Status
- Open-source protocol draft
- Source
- Developed in the public repository kitharness/khp. The spec pages here are copied from commit
70fab29(2026-11-16). - Conformance
- khp check is in the same repository. It is not published to npm yet.
- Maintainer
- Kition, which also makes the reference implementation. The protocol is meant to move to a neutral foundation later.