AI Agent Use Cases

Added today

11All 202

Trying Codex Automated QA for a Flutter App

The author reports that after integrating Codex automated QA into a Flutter app under development, slow tests and unintended changes to features became problems.

Codex
Dev

Making a 3D Cube Net App for Children's Math Study

Grok Bot reportedly created a 3D app where children can fold all 11 cube nets from their textbooks, which are usually shown only as flat diagrams, using their fingers.

Grok Bot
Learning & Careers

1–20 of 202

Work & Research

Outsourcing Microsoft 365 Setup and Management for a One-Person Company

The author did not know how to set up Microsoft 365 Business, so they entrusted Grok Bot with connecting the company domain, migrating email, and conducting weekly security checks.

How it works

  1. Grok Bot added the company domain to Microsoft 365 and carried out the verification process.
  2. They migrated the company email to 365 without affecting the existing website. The author reports they did not interact with the admin interface themselves.
  3. Currently, Grok Bot checks the settings weekly, tightens any weak security areas, monitors for new threats, and explains the results in simple terms. Before making any changes, Grok Bot shows what will be changed and why, and only applies them after the author approves.

Results

The author reports that, as a one-person company without an IT department, they now feel no need for one. No specific inspection results or figures were disclosed.

Notes

It is not confirmed which security settings were changed or whether there were any issues during the email migration.

Source

X Original post ↗

Example prompt · Grok Bot

Help set up a business email and account management service for a small company for the first time, and enable ongoing weekly checkups.

Input: Company domain [domain], desired service [e.g., Microsoft 365 Business], current email and website hosting provider [hosting/DNS provider], number of users [number]. First, read and back up all current DNS records, and show which records are needed for the website and which are for email. If you do not have admin account access, only tell me what I need to do.

Steps: 1) Add the records needed to verify domain ownership. 2) Before changing email records, summarize how to migrate existing email and how to revert, and get my approval. 3) Do not touch website records; after changes, check that both the website and email sending/receiving work. 4) On a set day each week, check security settings (multi-factor authentication, external sharing, number of admins, login alerts) and report in plain language. 5) For any changes, first show what and why you want to change, and only apply those I approve.

Deliverables: DNS backup, change log, email migration confirmation, weekly checkup report template. First, test email sending/receiving with one user before rolling out to all users.