# What to let Corey run on its own

Split work by whether your judgement is the point. Let Corey run marketing, finance admin, analytics, research and maintenance on its own. Keep anything you judge by looking at it at your desk. Then apply one rule - only let Corey ship unattended where a machine can tell it got the change wrong.

## FAQ
Q: What should I never let Corey do unattended?
A: Anything your customers pay for. Your product, your billing, your customer dashboard. Prepare the change automatically by all means, but look at it before it goes live. The cost of a bad marketing page is an hour of embarrassment; the cost of a bad product deploy is a refund and a lost customer.

Q: How do I know if something is safe to automate?
A: Ask whether a machine could tell you it went wrong. If a script can check the work - tests pass, the build succeeds, the links resolve, the styling uses your approved colours - then Corey can ship it while you sleep. If the only way to know is a human looking at it, keep it at your desk. That is the whole rule.

Q: Why does my issue tracker matter for automation?
A: Because once Corey works from your backlog, every open issue reads as a fact. A ticket that says a bug is unfixed when it was fixed last month will send Corey off to fix it again. A human skims past a stale ticket; an autonomous assistant acts on it. Keep the backlog true, or keep Corey out of it.

Q: Do I need a server to run Corey unattended?
A: Yes, for the always-on half. Corey running on your laptop stops when you close the lid. A small VPS costs a few pounds a month and gives you scheduled tasks that run overnight. The desk half needs nothing extra - that is just Corey working alongside you as normal.

Corey does this for you. Start with Corey, 28 days on us: https://getcorey.ai/get-started