SenroFlux
| 开发者 |
specflux
stephen1204paul |
|---|---|
| 更新时间 | 2026年10月10日 17:14 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Runs are session-bound. A run acts as the user who started it; nothing runs in the background.
- Tools are WordPress Abilities, restricted per run to an allow-list supplied directly by the consumer, or derived from a registered pack (a named tool surface — pages, posts, site, or commerce, all bundled).
- Two gate modes, resolved once per run. If the SenroGate plugin is active, every call is governed by its gate (packs, tiers, approvals) and audit trail. Without it, SenroFlux falls back to a built-in minimal gate: every call that changes the site still stops for a person to approve it on SenroFlux's own Runs screen before it runs; reads do not. A run's mode is pinned at start and never changes underneath it — if the environment's mode changes mid-run, the run fails cleanly instead of silently switching enforcement.
- Three kinds of park. An approval park (a governed write, resolved by a person), a question park (the model asks the user one structured question), and a plan park (the model proposes a numbered plan before its first write; once accepted, that plan's tool set is a fence — calls outside it are refused until a new plan is accepted).
- Budgets bound every run. Steps, tool calls, tokens, questions and plans. A consumer may only lower a registered ceiling; running out of questions is not a failure — the model loses the ability to ask and proceeds on stated assumptions.
- Four bundled packs. Pages and posts (create/update/publish, with
publish handled as its own governed step), site (navigation, front page,
homepage patterns), and commerce (WooCommerce catalogue and order
operations, when WooCommerce is active). Every content write is validated
before anything is persisted: unrenderable or non-round-tripping markup,
blocks outside the allowed set, disallowed tags or attributes, unresolved
{{placeholder}}text, an unrecognised pattern shape, a slot count out of range, a page-shape rule (e.g. hero must come first), or a slug/title collision with an existing page or post — all refuse the whole write and persist nothing. - Not for multisite. SenroFlux refuses to activate on a WordPress multisite install.
安装:
- Install and activate SenroFlux. It works standalone with a built-in approval gate.
- Optionally install and activate SenroGate for its full audit trail, tiered approvals, and cross-plugin governance — SenroFlux detects it automatically and switches gate modes on the next run started after activation.
- Consumers (e.g. marketing-analytics-chat) detect
senroflux()and offer multi-step runs automatically.
常见问题:
Can the AI add scripts or code to my site?
No. SenroFlux never writes PHP, JavaScript or CSS files and never runs code
the model produces. A run only writes content: pages, posts, navigation,
products and store reports. Every piece of markup it writes is checked
against a fixed list of allowed blocks, tags and attributes before saving,
and anything outside that list (a <script>, an inline event handler, an
unknown block) refuses the whole write. SenroFlux does this itself rather
than relying on WordPress's HTML filtering, because administrators are
allowed unfiltered HTML.
Does it work without SenroGate?
Yes. SenroGate is optional, not required. If it isn't active, SenroFlux uses its own built-in minimal gate: every call that changes the site still stops for a person to approve it on SenroFlux's Runs screen before it runs; read-only calls do not. Installing SenroGate later adds its full audit trail, tiered approval thresholds, and governance shared across other plugins — new runs pick it up automatically.
Does a run keep going while I'm not looking?
No. Runs are session-bound and driven from the browser; nothing executes in the background. A parked run simply waits until someone with permission resolves it.
What happens to a run in progress when I upgrade from 0.2?
A run that was still parked or running at the moment of the upgrade fails
on its next tick with a partial report and the reason "started under 0.2" —
0.2's update-post tier changed under it, so it cannot safely continue.
Completed 0.2 runs still render their full history and report. Nothing is
silently re-tiered or auto-resumed.
Which post statuses can create-post and update-post write?
create-post never publishes — it refuses a publish or future status
outright and only ever creates a draft. update-post covers draft-state
edits only; any transition to publish/future, or any edit to an
already-public post, goes through the separate publish-post ability,
which is a higher-tier, separately governed call.
Will pages use my theme's design?
On block themes, yes. SenroFlux builds each section from one of your theme's
own patterns when one fits the content, and otherwise uses its own layouts
with your theme's spacing and colours. It never adds colours of its own to a
theme pattern. To use only SenroFlux's layouts, untick "Use my theme's block
patterns" under SenroFlux → Settings. Developers can drop individual patterns
with the senroflux_theme_patterns filter.
Does SenroFlux support WordPress multisite?
No. SenroFlux refuses to activate on a multisite install.
更新日志:
- The bundled image patterns no longer reference a remote placeholder image; they use a small image shipped with the plugin.
- Media search and the missing-alt-text list now need the upload_files capability and only show images the current user may read or edit. Saving a store report, setting a featured or product image, and enabling a coupon check the matching post type and attachment capabilities too.
- A question the assistant asks is no longer cut off mid-word at 300 characters.
- A plan step now shows one plain-language badge (Read only, Makes changes, Needs approval) with the actions it will use, instead of the same badge once per action.
- A blank assistant turn no longer shows as an empty chat bubble, and a run still working in the background no longer greys out the Accept and Approve buttons on another run.
- Sanitize the decoded JSON bodies of the admin-ajax start (budget) and tick (park resolution) requests: answer text, choices and plan notes go through sanitize_textarea_field(), budget caps are kept only as non-negative integers.
- Point the Openverse terms-of-service link at its current location.
- Two gate modes: SenroGate when active, otherwise a built-in minimal gate that still pauses every governed write for human approval on the Runs screen. A run's mode is pinned at start.
- Three new packs alongside pages: posts, site (navigation, front page, homepage patterns), and commerce (WooCommerce catalogue/order operations).
- Stock photo search and alt-text/image-generation abilities via the WordPress AI Client and Openverse.
- The Runs screen moved out of Tools to its own top-level "SenroFlux" menu
and is now a React app (
assets/src/runs/, built with@wordpress/scripts);tools.php?page=senroflux-runsredirects there. - Extension API:
SENROFLUX_API_VERSION, a reflection-enforced@apisurface for third-party packs (see "Extension API" above). - Pages follow your theme. Each page layout (hero, text, text with image, services, FAQ, call to action) is built from the active theme's own block patterns where one fits, filled with the run's copy. Twenty Twenty-Five and Ollie have built-in mappings; other block themes are matched automatically, and anything that doesn't fit falls back to SenroFlux's own layouts, using the theme's spacing and colours.
- Section tone: a section can sit on a contrast or accent band taken from the theme palette, only where the text keeps WCAG AA contrast.
- A Settings checkbox, "Use my theme's block patterns", to build every page from SenroFlux's own layouts instead.
senroflux/update-postis now draft-state edits only (Tier 1) — it refuses an already-public target (publish/future/private) and a requested publish/future transition. Newsenroflux/publish-post(Tier 2) covers every publish/future transition and any edit to an already-public post. Update your integration to callpublish-postfor those cases.senroflux/create-postnow refusesslug_collision(409) when a non-trashed page or post of the same type already holds the requested slug, or matches the title case-insensitively.- SenroGate is no longer a hard requirement. 0.2 always failed closed
without it; 0.3 falls back to a built-in minimal gate instead (see the
FAQ above). If you relied on
senroflux_ungovernedmeaning "SenroGate is missing," check the run'sgate_modeinstead. - A run still parked or running under 0.2 at the moment you upgrade to 0.3 fails on its next tick with reason "started under 0.2" instead of continuing — it is not migrated or resumed.
GET /runs(and the Runs screen's run list) is now scoped to what the current viewer may see or resolve, instead of returning every run on the site to any user who could reach the endpoint.
- Schema v2: run status/step-kind enums,
resumeobject replaces the 0.1approval_actionparameter (breaking),max_questions/max_plansbudget keys. - Default budget ceilings raised to
max_steps60,max_tool_calls30 andmax_tokens250000 — a live pages run costs 31-45 steps and up to 90k tokens once the model retries a refused write, and a consumer may only lower a ceiling. - Question parks (
senroflux/ask-user) and plan parks (senroflux/propose-plan) with an accept/veto fence around Tier ≥ 1 writes. - Packs: a named tool surface a run may start from (
packargument tostart()), plus the bundled pages pack and its five polyfill Abilities. - Skills and a rendered system-instruction pipeline
(
senroflux_run_skillsfilter), with a per-run disable list (skills_disable). - Verification read-back and a per-run report surfaced on completion.
- Runs screen: new-run form with preflight, three park cards, polling detail view.
- Initial scaffold: hard-dependency gate against Agent Safety.