|
WordCamp Agent is a free Telegram assistant for WCEU attendees. It plans your trip, browses the schedule, remembers which sessions you care about, and pings you before they start. |
All you need is a WordPress.com free account to get started. And once you’re in, you’ll also get a preview of something more interesting: a working preview of WordPress Guidelines, the agent-context system shipping in Gutenberg and on its way to WordPress Core. It’s also the easiest way to see Guidelines working end-to-end in a real production environment. |
How WordCamp Agent is built |
The agent lives on Telegram and is bound to a regular WordPress site at wcagent.wordpress.com. When you message it for the first time, you’re added as a contributor on that site — your conversation, preferences, and notes become real WordPress content, stored against your user, private to your account, and deletable at any time |
- Ask for travel tips for Kraków and get accurate answers.
- Browse the live conference schedule.
- Tell it which sessions interest you, who you want to meet, or what accessibility needs you have. It remembers, across sessions and devices.
- Save notes during talks that you can turn into a post or a recap.
None of that required custom application code. Every behavior — the personality, the schedule lookup, the memory of your preferences — is a published Guideline on the WordPress site behind the bot. If you can publish a post, you can extend the agent. |
WordPress Guidelines: The system under the hood |
WordPress Guidelines stores four kinds of agent-facing knowledge as standard WordPress content: |
- Instructions: Site-wide guidance that shapes how an agent behaves. WordCamp Agent uses these for its personality and core event knowledge.
- Skills: Reusable capabilities. The live schedule and venue lookups are skills. Swap the skill, change the agent’s behavior — no code change.
- Memory: Facts the agent accumulates while working with you. Your session interests, dietary preferences, networking goals.
- Artifacts: Work-in-progress. Notes, drafts, fragments you’ll come back to.
All four are represented as a single wp_guideline custom post type, classified by a wp_guideline_type taxonomy. They use WordPress’s existing roles and capabilities, and they’re accessible via standard REST endpoints. |
What this looks like for developers |
Guidelines reuse primitives and conventions you already know: |
- A single wp_guideline custom post type
- wp_guideline_type taxonomy for distinguishing between instructions, skills, artifacts and memories
- Native post revisions for versioning
- Capability-based access control: administrators see everything; contributors, authors, and editors get read/edit on their own private guidelines; subscribers are blocked at the post-type level
For a deeper technical walkthrough of Guidelines, take a look at Grzegorz’s post. |
Coming to WordPress Core: Guidelines |
The next step is WordPress Core. |
We’re proposing it as a Core API because the alternative — every plugin shipping its own memory store, its own permissions model, its own REST surface — is exactly the kind of fragmentation WordPress has historically avoided. |
Putting Guidelines in Core means every WordPress site, hosted anywhere, becomes agent-ready by default. |
The single best way to understand Guidelines is to use a site that’s already built on it. Ask it to plan your Kraków trip. Tell it what sessions you care about. Come back tomorrow and watch it remember. |
|
|
|
|
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.