When an AI client cannot reach your site, open NibWP → Status before anything else. It is read-only, so it is safe to run and safe to screenshot.

1. Press Re-run diagnostic. Each check comes back Pass, Check, Problem or Info, grouped as Connection, Authentication, WordPress & server, Plugins, themes & firewalls, and Sandbox & extensions.
2. Read the verdict at the top. When something is broken it names one Fix this first. Checks that failed only because of that one are marked as caused by it, so you have a single thing to fix rather than a column of red that clears all at once.
3. The three causes we see most often:
   • Permalinks set to Plain. Go to Settings → Permalinks, choose anything else, then copy the endpoint again from NibWP → Connect, because it will have changed.
   • Application passwords switched off — by a security plugin, by a WP_APPLICATION_PASSWORDS constant in wp-config.php, or because the site is not served over HTTPS.
   • The server stripping the Authorization header before PHP sees it. The credentials are correct, the server discards them, and the request looks exactly like a wrong password. On Apache or LiteSpeed the screen offers a one-click, reversible fix; on nginx it is a fastcgi_param HTTP_AUTHORIZATION line in the PHP location block.
4. Check the Your endpoint card. That address has to be reachable from the machine running the client, not only from the server. Open it in a private window to test: a login prompt or a JSON error means reachable, a firewall page or a timeout does not.
5. Still stuck? Deactivate security and firewall plugins one at a time, re-running after each, then generate a fresh application password. If it still fails, copy the Support report and send it to us — site address and versions only, no passwords or keys.

Full guide: How to: read NIBWP Status

Your Pro or Bundle key is activated on the site itself. That is what unlocks the paid parts and what keeps updates arriving.

1. Go to NibWP → License.
2. Paste your key into License key and activate. Keys are domain-locked, so each site you want it on is activated on that site.
3. Lost the key? Use find my licenses by email. Enter the email you used at checkout and a six-digit code is sent to it — check spam as well. Once verified, every licence tied to that email is listed, ready to activate one at a time or all at once.
4. Activating unlocks the premium integrations, toolkits and Skills. Saved Workflows need Pro; a Bundle adds every Skill on top of Pro. Agent View, Memory, NibWP Design, the abilities and the Status screen are free on every install.
5. The card on that screen reads Active or Inactive, with Refresh, Reactivate and Deactivate beside it. Refresh is the first thing to try if a licence looks inactive after a domain change or a renewal. Deactivate releases the key from this site, which is what you want before retiring or moving one.

With an active key, the plugin asks nibwp.com what the current version is and Pro updates then appear in your usual Plugins screen. With no active key, WordPress falls back to the WordPress.org listing.

Worth knowing: the WordPress.org build is deliberately one release behind the nibwp.com build. Nothing is stuck — each release is proven on nibwp.com first. If you hold a licence, you are already on the newer one.

Full guide: Activating your Pro / Bundle license

Left to itself, an assistant builds the page every assistant builds. NibWP Design decides how a page should look before anything is built, and it decides it from your site rather than from a template. It is free on every install.

• Your assistant calls the design direction ability before it builds a page, section or component. You should not have to answer "what colours would you like".
• It reads what the site already has: your ACSS variables, the theme.json palette and type scale, and the colours in your logo. Where the site says nothing, it falls back to a catalogue seeded per site, so two installs never start from the same place.
• What comes back is a direction: colour roles with contrast already checked and corrected to WCAG AA, a heading and body pairing with its scale, a spacing rhythm and a line measure, shape language for radius, shadow and borders, and the section sequence that suits that kind of page.
• It also returns the generic defaults to refuse on that page, each with its reason — the centred hero stack, three equal cards in a row, one flat padding value throughout, body text run to the full width of a wide container.
• It names the builder this site uses and the tokens to express the direction in, so you get real elements and site tokens instead of pasted markup.
• The direction is remembered. Page two matches page one, which is what makes a site read as designed rather than assembled. Ask for a fresh look only when you genuinely want a different one.

NibWP Design never writes markup itself. It directs whichever builder does the work.

Full guide: How to: set a design direction

Memory is a small set of notes your assistant keeps on the site, so you are not re-explaining the same things at the start of every session.

• Find it at NibWP → Memory. The screen is headed AI Memory and shows one card per entry.
• Each entry is a key, its content, any tags, and the date it was last updated. In practice that means brand voice, your naming conventions, palette decisions, project context, known issues — the things you would otherwise repeat.
• The assistant writes and reads these itself, through the nibwp/memory-store and nibwp/memory-recall abilities. You do not have to ask it to save anything.
• Memory is per site. Entries live in your own WordPress database, not in a third-party service, and every other site you connect keeps its own separate set.
• The store holds up to 100 entries. From 80 onwards the assistant is told to tidy up; at 100 a new entry is refused until something is removed.
• A search box appears once you have more than five entries, and it matches keys, content and tags.
• To remove one entry, use the × on its card. To empty the store, use Clear All at the top of the screen. Both ask you to confirm first.

Treat it as context, not storage: voice, conventions and decisions. It is not the place for passwords, keys or anything you would rather an assistant did not read back to you later.

Full guide: How to: use Memory

Agent View is a full-screen workspace where your own site opens in tabs and you watch the assistant work, step by step.

• Open it from NibWP → Agent View. It fills the browser window rather than sitting inside the admin sidebar, because the site is the point.
• These are real pages, not a preview. The assistant opens admin screens and front-end pages as tabs, reads what is actually rendered, and every save appears on screen as it lands.
• Ask first is on by default. Reading, hovering, screenshots and audits run freely. Anything that changes the site — a click, a filled field, an insert, a delete — stops and waits for Allow or Refuse. Batched steps are judged step by step, so batching is not a way around the prompt.
• Being asked forty times is why people switch safety off, so the prompt also offers Allow, and stop asking. The switch in the top bar always shows which state you are in.
• The Activity panel docks along the bottom and lists each step as it is made.
• The width buttons — Mobile, Tablet, Laptop, Desktop, Fill the window — let you check a layout at each size without leaving the workspace.
• Keep the workspace open, signed in as the same WordPress user as the connected assistant. If you close it, the visual abilities return a clear error rather than editing blind.

It earns its keep for design review across widths, accessibility checks on the rendered page, guided edits you want to supervise, and reading the browser console while something is being debugged.

Full guide: How to: work in Agent View

Jobs are the recurring maintenance you would rather not remember. You add one from a card, run it now or put it on a schedule, and read the result in plain English. Four jobs run end to end today.

• Find broken links — collects the links from your recent posts and pages, checks each one with a real request, and reports what is broken with its status code, marking internal and external separately. Read-only.
• Security scan — checks the things that quietly stay wrong: debug output exposed to visitors, a stray debug.log, the built-in file editor left enabled, a user called "admin", open registration handing out a privileged role, a site URL still on HTTP, and outdated core, plugins or themes. Read-only.
• Check for updates — lists every pending plugin, theme and core update with its current and new version, read from WordPress's own check, so there is no network wait.
• Clean up the database — scans for old revisions, auto-drafts, spam, trash, expired transients and orphaned meta, then stops and waits for you.

How the safety and the schedule work:

1. Anything that changes your site goes to Approvals first. The job pauses, shows what it found, and applies nothing until you approve. Deny it and the run closes with the reason recorded.
2. Set each job to Manual, Daily or Weekly. Scheduled runs go through WP-Cron and drop their results into Reports on their own.
3. Activity is a live timeline of every step, newest first, and Reports keeps the plain-English result of every run — what was checked, what passed, what needs attention.

Full guide: Jobs

A workflow is a playbook you write once: when to use it, the principles behind it, the process in order, the strict rules, the checks that have to pass, and the shape of the final report. NibWP hands it to the assistant as context it must follow, so the same task comes back the same way each time.

• Starters are already there. Open NibWP → Workflows and you have playbooks for page builds, converting HTML or a Figma frame, SEO passes, redirect fixes, pre-launch checks, WooCommerce products, course builds and more. Edit any of them — once edited, it is yours.
• A workflow does not have to be pinned to be used. The assistant loads one on its own when your task matches its "when to use" section.
• Pin one to make it always-on. A pinned workflow is injected as strict context on every request, whatever you ask. Pin it exclusively when you want exactly one set of rules in force and nothing else.
• Revisions are kept. Every edit is saved as a revision, so a rule that turned out wrong can be rolled back.
• Categories keep it organised — Build Sites, SEO, Content, Forms, Automations, E-commerce, Maintenance, or a category you name yourself.
• Share it when it works. Keep a workflow private, share it with your License Circle, or publish it to the community, where other installs can vote on it.

The assistant can write and edit workflows as well, which is the easiest way to start: do the job by hand once, then ask for it to be written up as a workflow and correct the draft. Workflows come with Pro and with the Bundle.

Full guide: Workflows: playbooks your agent follows

Hand the assistant a screenshot, a live URL, pasted HTML or a Figma frame and ask for the page. With a builder skill installed the run always takes the same shape, and you get a say at two points in it.

1. Design direction. Before anything is built, colour roles, type, spacing rhythm and the layout sequence are settled, along with the generic defaults to refuse. Switch the NibWP Design skill off if you would rather skip this.
2. Preflight. One round of questions per session: your brand class prefix, which page or post the build goes into, and how to insert it — append, replace a section, or a new page. What is already on the site is detected first, so you are only asked what is missing, and answers like the brand prefix are remembered for next time.
3. Dry run. The skill builds the component and validates it without saving anything. Failures come back with a reason. Improvements come back as recommendations — repeated cards offered as a loop over a custom post type instead of ten static copies, a raw video embed swapped for a real embed block.
4. Save. Only after validation passes and you have answered the recommendations. Nothing is written to your site before this step.
5. Feedback. A thumbs up or down is recorded against the run, so later builds on this site start from what worked.

How to steer it:

• Name the target page in your first message and you skip a preflight question.
• Ask for the dry run only if you just want the validation report.
• To change something afterwards, describe the change — the skill edits the existing component rather than rebuilding the page.

Full guide: How to: install & use Pro Skills

An ability lets the assistant touch your site. A skill teaches it one builder or framework properly, so what comes back is native, editable output rather than HTML guessed into a page.

Each skill ships with its own playbook, its own abilities and its own validator. When a task matches, the skill puts the run on a fixed route — ask, build, validate, then save — and rules out the shortcuts. It will refuse to inline a stylesheet or hardcode a colour where your design tokens belong.

What ships today, under NibWP → Skills:

• Page builders — EtchWP Pro, Bricks Pro, Elementor Pro, Breakdance Pro, Kadence Pro, Voxel Pro
• Design — Figma Pro, which reads the real node tree and Variables instead of a screenshot, and ACSS Pro, which generates a palette plus type and space ramps
• SEO Pro — audit, optimise and validate across Yoast, Rank Math, AIOSEO, SEOPress or Slim SEO
• Courses — Tutor LMS Builder and Tutor LMS Course Mini-site
• NibWP Design — decides how the site should look before anything gets built; included, not premium

Two things worth knowing before you pick one:

1. A skill unlocks only when the plugin it targets is present. EtchWP Pro needs Etch, Bricks Pro needs Bricks, the Tutor skills need Tutor LMS. SEO Pro has no such requirement.
2. The premium skills come with Pro and with the Bundle, or you can buy a single skill licence on its own from €19. The Bundle covers every skill, current and future.

Activate your licence on the same screen and the skills you own appear in the assistant's tool list straight away.

Full guide: Pro Skills explained

Form plugins all do the same job and none of them do it the same way. NibWP covers that twice over: one universal tool for when you do not care which plugin is installed, and a dedicated integration for when you do.

The universal tool

nibwp/forms-manage detects the active form plugin and answers with one shared set of actions: list the installed form plugins, list forms, get a single form, read entries, create an entry, delete an entry. Where several form plugins are installed you can name the one you mean rather than accept the detected one. It is the right tool for "how many enquiries came in last week" on a site you have never seen.

The dedicated integrations

Eleven plugins have their own card on NibWP → Integrations, each reaching far more of that plugin than the universal tool can: Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Ninja Forms, Formidable Forms, Forminator, HappyForms, JetFormBuilder, WS Form, and Bit Form, which arrived in 1.2.11 and reads Bit Form's own tables. Between them they cover fields, entries, notifications, confirmations, add-on feeds, payments, settings and exports.

Because each of those goes deeper, the universal card is no longer listed on the Integrations screen. Anything already switched on keeps working.

The audit

Nine of the eleven carry a read-only audit that looks for the failure you cannot see: a form quietly collecting entries nobody is told about. Depending on the plugin it also catches a submission discarded after the visitor has been thanked, every notification template switched off, a reached entry limit, an expired schedule, or an inactive form still embedded on a page. Findings arrive with their fix attached, and nothing is changed for you.

Full guide: Integrations reference