Automa
Run your AI company from your phone. Tasks, approvals, agents and files — and agents that can ask your phone for the files they need.
Platform: Android · Server port: 3100 · Developer: Nathan · Origin: Jamaica
Automa is an Android app from CorX Labs for running a company of AI agents from a phone. The agents do not live in the app. They run on a server — either the same phone under Termux, or a machine somewhere else reachable over HTTPS — and Automa is the control surface: the place where you see what they are doing, approve what needs a human, and hand over the files they are waiting on.
The design bet is that a phone is a bad place to supervise work and a good place to unblock it. So the home screen does not try to show the company. It shows one heading — Needs you — and four things under it: your inbox, approvals, file requests, and who is working on what. Everything an agent can finish on its own never reaches that screen.
Automa is Android-only and new, and there is no public download link on this page yet. What follows is a description of the app and how it works, drawn from the build itself — not a store listing, and not a set of performance claims. Get in touch if you want to try it.
- Platform
- Android
- Shape
- Client for an agent server
- Server
- This phone (Termux) or HTTPS
- Default port
3100- Primary nav
- Home, Tasks, +, Files, Inbox
- File channel
- Device Files, one shared folder
- Recurring work
- Routines → execution tasks
- Connections
- First-party & provider-hosted MCP
- Download
- Not linked here yet
1. How it is wired
Three parts, and it matters which one is where. The phone holds the app and one shared folder. The server holds the agents, their tasks and their routines, and does the work. The connections are how the server reaches services that are not yours to host — mail, code, docs, chat. Solid lines carry requests outward; dashed lines are the three things that come back to you.
| Part | Where it runs | Responsible for | Keeps working if the phone sleeps |
|---|---|---|---|
| Automa | The phone | Showing what needs a human; creating tasks; sending files | Not needed — it is only the control surface |
| Agent server | The phone under Termux, or a machine on an HTTPS address | Running the agents, the tasks and the routines | Only if the server is not the phone |
| Shared folder | The phone, always | The only files agents can ask for | Requests queue; the file goes when the phone is reachable |
| Connections | The provider, or a provider-hosted MCP server | Mail, code, docs, chat — scoped per agent | Yes |
2. The app, screen by screen
Eight screens, in the order you meet them. Every action sits in the bottom third where a thumb reaches — Home, Tasks, a raised create button, Files, Inbox — and the destructive ones undo rather than confirm.
The screens above are drawn from the build, not photographed from it — they are vector redraws, so they stay sharp and follow the site’s light and dark themes. Names, addresses and task titles are examples.
3. Device Files — the part worth reading twice
Most agent tooling breaks at the same place: the agent needs a file, and the file is on your phone. Automa makes that an explicit channel rather than a dead end. You share one folder. The phone then shows up to the agents as a connected device, and when an agent needs something it posts a request — which lands on the Files tab and on the home screen under Needs you.
Nothing outside the folder you chose is visible. That is the boundary, and it is the only one, so it is worth choosing narrowly.
Auto-send removes you from the loop. That is the feature and that is the risk. With the switch off, every file leaves the phone because you tapped Send. With it on, a file an agent asks for goes without asking you — so anything inside the shared folder can leave the device without a decision at the moment it happens.
Share a folder that exists for this purpose, not your whole Documents tree, and leave auto-send off until the folder is one you would be comfortable handing over wholesale. An agent that can ask for a file can ask for any file in there.
| Auto-send off | Auto-send on | |
|---|---|---|
| A file leaves when | You tap Send on the request | The agent asks for it |
| You find out | Before — it is a request | After — it is a log line, with Undo |
| Agent is blocked | Until you look at your phone | Not at all |
| Reasonable when | Always | The shared folder holds nothing you would mind sending |
4. Tasks, routines and approvals
Three objects, kept deliberately separate.
- A task is one unit of work with one owner and one state. It carries a
tag like
NOR-7, an agent, and where it has got to. Created by you from the centre button, or by a routine, or by an agent that decided it needed one. - A routine is a recurring definition, not the work. When it fires it materialises an ordinary execution task — same list, same owner, same audit trail. A weekly report is a routine; each Monday’s report is a task.
- An approval is a task that has stopped and is waiting on a human. Hires, budgets, plans. Nothing proceeds past one until you answer it, which is the point: the phone is where that answer is cheap to give.
Auto mode sits on a task, not on the company. A task in auto mode lets its agent choose its own next step; the approvals it runs into still come to you. There is no global switch that turns supervision off.
5. Built for one hand
The interface rules are short, and they are the reason the app feels different from a dashboard shrunk to phone width.
- Every action lives in the thumb zone. The five-slot bottom bar — Home, Tasks, a raised create button, Files, Inbox — and both buttons of every sheet sit in the bottom third of the screen.
- One create button. Tasks, routines and agents are all made from the same raised centre control, so there is never a hunt for the right plus.
- Undo, not confirm. Destructive actions happen and offer a way back, rather than stopping to ask. Leaving an agent, sending a file and moving a task all work this way.
- Haptics carry the state change. A send, an approval and an undo each feel different, so you do not have to read a toast to know what happened.
- One mascot, many moods. A single gradient character covers empty states and confirmations instead of a set of unrelated illustrations.
- The home screen is a filter, not a summary. It answers one question — what needs you — and leaves everything else to the tabs.
6. What Automa is not
It is not the agents, and it is not a model. Automa does not contain an AI. It talks to a server that runs the agents; if that server is off, the app has nothing to show. Whether the agents are any good is a question about the server and the models behind it, not about this app.
It is not a claim that this replaces a company. The words “CEO” and “CTO” in the app are role labels that decide what an agent may touch. They are scoping, not seniority.
Current limits, stated plainly
- Android only. There is no iOS build and no desktop build.
- No public download link on this page yet. This page describes the app; it is not a store listing.
- The server is yours to run. Automa does not host anything for you — you point it at an address, on this phone under Termux or on a machine over HTTPS.
- If the server is the phone, the company sleeps when the phone does. Work carries on overnight only if the server is somewhere else.
- One shared folder, not a file browser. Agents see the folder you chose and nothing else — which is the safety property, and also the limitation.
- No published benchmarks or reliability numbers. Nothing on this page is a performance claim, because none have been measured.
7. Questions
What is Automa?
An Android app built by Nathan at CorX Labs in Jamaica. It is the control surface for a company of AI agents: the agents run on a server, and the phone is where you see what they are doing, approve the things that need a human, and hand over the files they ask for. It is not the model and not the agent runtime — it is the thing you hold.
Do I need a server?
Yes — Automa is a client, and it connects to an agent server by
address, on port 3100 by default. There are two ways to get one. The server
can run on the phone itself under Termux, in which case the phone is both
server and client. Or it can run on another machine reachable over an
HTTPS address, which is what you want if the work should carry on while
the phone is asleep.
What does the home screen show?
Only what needs a human. Four rows under one heading that says Needs you: the inbox, approvals waiting on you for hires, budgets and plans, file requests where an agent is blocked on a file, and agents — who is working on what. Below that is the roster, with the task each agent is on and when it last finished something. Anything an agent can do without you stays off that screen.
How does an agent get a file off my phone?
Through Device Files. You share one folder — Documents, say — and the phone appears to the agents as a connected device. When an agent needs a file it posts a request; the request shows up on the Files tab and on the home screen, and you send it. Nothing outside the folder you picked is visible to the agents.
Should I turn auto-send on?
Only once you know what it changes. Off, every file leaves because you tapped Send. On, a file an agent asks for is sent without asking you — so anything in the shared folder can leave the phone without a decision at the moment it happens. That is the feature and it is also the risk. Share a narrow folder that exists for this, not your whole Documents tree, and leave the switch off until that folder is one you would be comfortable handing over wholesale.
What is a routine, and how is it different from a task?
A routine is a recurring work definition — deliberately not the work. When it fires it materialises an ordinary execution task: one that appears in the task list, is attributed to an agent, and leaves the same audit trail as a task you made by hand. A weekly report or a daily inbox sweep is a routine; each Monday’s report is a task.
How is an agent’s access to Gmail or GitHub scoped?
Three separate choices per connection, not one on-off switch: which agents get access, which account they use, and which actions they may take. An engineer agent can hold write access on one repository while the rest of the company has none; a designer agent can read a docs space without being able to change it. Alongside first-party connections, Automa also lists provider-hosted MCP servers — Airtable, for instance — scoped exactly the same way.
Can I download it, and is there an iOS version?
Automa is Android-only, and there is no public download link on this page yet — this page describes what the app is and how it works rather than shipping it. There is no iOS or desktop build. If you want to try it, get in touch.
Automa
The company runs on a server. You carry the decisions.
Approvals, file requests and an inbox — the three things that actually need a person — on the device that is already in your hand. Android, built in Jamaica.