Questions before you use Agent Ops Suite

Agent Ops Suite is a lightweight local backend for AI agents that need to help manage real business operations. It provides project records, CRM-lite relationship context, campaign and content records, issue tracking, customer-service tickets, approval queues, audit notes and handovers.

No. Agent Ops Suite is agent agnostic. Agent Robbie is one supported operator, but Codex, ChatGPT agents, Claude, Gemini, Copilot, Cursor, Windsurf, Devin, Replit Agent, local agents and custom tools can all work against the same structured operating records when connected appropriately.

Agent Ops Suite is a local installation. Your operational data remains on your hardware by default and is not shared to cloud services unless you deliberately connect a cloud service, AI provider, sync target, email account, repository host or third-party system.

Local-first operation helps with privacy, security, speed and cost control. Agents can read structured local records before making cloud calls, which can reduce repeated context loading, unnecessary provider usage and avoidable exposure of business data.

Your agentic memory layer should hold durable context: policies, brand voice, important source-linked knowledge and compact retrieval packs. Agent Ops Suite holds operational state: contacts, tickets, projects, tasks, content, campaigns, approvals and handovers. That split keeps memory useful without turning it into a CRM or helpdesk.

Yes. The product is organised by project, so one installation can support multiple brands, products, client accounts, side projects or internal initiatives. Each project can have its own contacts, work items, campaigns, content calendar, support tickets and policies.

CRM here means lightweight relationship and audience context, not a full enterprise sales suite. Agent Ops Suite stores people, organisations, roles, tags, segments, activity notes, opportunities where needed and links to support, marketing and project work.

Yes. Onboarding supports structured CSV-style imports for contacts, organisations, projects, work items, tickets and content records. External IDs can be preserved so future connector sync does not lose the relationship to your source systems.

Start with a project home, import or add core contacts and organisations, define the project policies, add current work items and tickets, then connect the relevant agent. The onboarding page walks through clean-up, mapping, import, review and first agent handoff.

Marketing agents can read campaign plans, audience segments, offers, message repositories, content calendar items and approved claim evidence. They can draft campaign ideas, emails, social posts, ads, launch sequences and landing-page copy, then route outbound assets through approval before publish or send.

Support agents can read inbound messages, identify the customer and project context, retrieve approved answers from your memory layer, draft replies, create tickets, file internal notes and escalate sensitive cases. Customer commitments should stay approval-gated unless you define a trusted policy.

Outbound marketing, customer commitments, refunds, complaints, public claims, pricing promises, legal issues, financial issues, privacy issues, sensitive personal data and reputation-risk work should require approval unless you explicitly create a narrow policy for bounded auto-action.

They can, but autonomy should be earned. The recommended path is research only, draft only, approval queue, bounded auto-action, then limited full autonomy only for low-risk, reversible work with logs and a clear escalation policy.

No. Agent Ops Suite can be the local operations layer and agent backend, but external systems can remain systems of record where that makes sense. The goal is to give agents clean operating context and guardrails without forcing every business process into one heavy app.

Connectors should be read-first by default. Write actions such as sending messages, updating external records, creating public posts or changing customer-facing data should go through policy checks and approval unless the risk is low and the rule is explicit.

Back up the local Agent Ops Suite data folder, exported project records, licence information and any connector configuration you control. If connected services remain the system of record, continue backing those systems up under their own tools and policies.

Agent Ops Suite is $49 one time for a lifetime licence to the installed product, including one year of bug and security fixes. Optional Updates Pass access is $5 per month for new features, connector improvements, refreshed onboarding resources and community membership.

Agent Ops Suite pricing does not include third-party AI, email, hosting, cloud storage, repository, CRM, helpdesk, payment, model-provider or other connected-service costs. Those remain optional and user-controlled.

No. Agent Ops Suite is operational software. AI outputs and workflow suggestions must be reviewed by a qualified human where legal, financial, privacy, safety, employment, regulated or high-consequence decisions are involved.

Your installed version keeps working under the licence that applies to it. The optional Updates Pass affects future updates, new features, connector improvements and community access; it is not required to keep using the version you already licensed.