Proposed separate higher-privilege companion

Safe hosting operations for when WordPress-level tools are not enough.

IM-Press Hosting Manager is the proposed separate companion for approval-gated cPanel, SSH, email, logs, cache, permissions, and recovery tasks. It is not included in IM-Press Core 5.2.3; the operations below describe the intended safety model.

See hosting toolsBack to Suite
Not core IM-PressWordPress page work stays in the core plugin.
Approval-gatedHigher-risk actions require explicit user intent.
Typed operationsSafer than improvised raw shell commands.
Safety model

Powerful enough for real fixes. Bounded enough to reduce worry.

Sometimes a WordPress problem is really a hosting problem: email settings, PHP logs, OPcache, disk space, DNS, SSL, or a broken plugin. The Hosting Manager concept is intended for those moments — not for everyday page editing.

👀

Read first

Start with diagnostics before changing anything.

  • Disk and inode status
  • PHP/error log checks
  • SSL/DNS summaries
  • Backup status
🧰

Maintain carefully

Low-risk maintenance should be typed, scoped, and logged.

  • Reset OPcache
  • Clear cache folders
  • Fix standard permissions
  • Stage verified artifacts
🛑

Confirm destructive actions

Risky actions need explicit approval, rollback awareness, and audit trail.

  • Disable broken plugin
  • Restore backup
  • Modify DNS/email
  • Edit critical config
Boundary: IM-Press Core should never become a raw SSH shell, cPanel clone, or credential vault. A future Hosting Manager should remain a separate escalation layer for user-approved operations.
Operational tiers

Three proposed tiers for safer host-level work.

The design goal is not “AI can do anything.” It is “a separately implemented agent can do the right thing, in the right risk tier, with the right approval.”

Tier 1 · Read-only

Look, don’t touch

Diagnostics that help decide whether hosting access is actually needed.

  • Tail safe log excerpts
  • Check disk/inodes
  • Read PHP version
  • Inspect cron, SSL, DNS summary
Tier 2 · Maintenance

Fix common issues

Bounded actions that are safer than open-ended SSH sessions.

  • Reset OPcache
  • Clear cache
  • Rotate logs
  • Run safe WP-CLI actions
Tier 3 · Recovery

Confirm, then act

Emergency or destructive changes with user approval and rollback check.

  • Disable plugin
  • Rollback/restore
  • Modify DNS/email record
  • Patch critical config
How it fits with IM-Press

WordPress editing stays calm. Hosting escalation stays explicit.

Most work should happen through IM-Press Core: AI page import, content editing, SEO, Safe Deploy, and review. A separately implemented Hosting Manager should appear only when the task leaves WordPress and enters the hosting account. The example intents below are illustrative, not shipped Core endpoints.

1

Try WordPress first

Use IM-Press Core, REST/OpenAPI, Safe Deploy, and optional MCP workflows only when configured.

2

Diagnose safely

Read-only checks identify whether cPanel/SSH access is required.

3

Ask for approval

User confirms the exact hosting-level action and scope.

4

Act with rollback

Perform the typed operation, validate result, and record what changed.

// example intent, not raw shell
hosting.logs.tail(site="airobotbuild.com", lines=80)
hosting.cache.reset_opcache(site="airobotbuild.com", approved=true)
hosting.email.update_forwarder(domain="example.com", approved=true)
Common use cases

For the occasional moments when hosting access matters.

HostGator/cPanel work does come up: email changes, SSL/DNS checks, logs, permissions, or broken-site recovery. The proposed Hosting Manager is intended to give those tasks a safer workflow instead of relying on memory or ad hoc commands.

Email and DNS support

Assist with cPanel email changes, forwards, DNS summaries, and related checks when requested.

Error diagnosis

Inspect PHP errors, logs, versions, disk, inodes, cron, and cache state before changing a site.

Recovery workflows

When approved, help disable a bad plugin, restore from backup, or repair standard permissions.

Escalate deliberately

Keep hosting control separate if your workflow needs it.

Start with IM-Press Core for WordPress creation and editing. Treat Hosting Manager as a proposed separate, auditable layer that requires its own implementation and approval before higher-privilege use.

Start with IM-Press CoreView the Suite