Act where the work lives
A member takes the action in the system where the work lives. Where there is a connection, it uses it. Where there is none, it works the system the way a person would. Two ways, one binding flow, on the same layers: enterprise, team, member, role and task.
Integrates with any system
Where a system has a connection, you connect it once and the member uses it. The credential stays in the binding. Bind it for the enterprise, a team, a member, a role or a task, and the same connection set further down takes the place of the one above it. GitHub and Slack work this way, as does every system in the tool directory that has a connection.
Operates like a human
Where there is nothing to connect, the member works the system the way a person would, for that run.
- You name where it may go and where it starts.
- Reading and typing proceed on their own.
- Submitting, sending, paying or deleting waits for you, with what was on screen as the record.
- The session ends when the run ends, when you cancel, and when spend is exhausted. The next run can already be signed in.
- You can watch, and you can take the session back.
- Files go in and out.
It is not a second way into a system the member is already connected to, not your laptop, and not a machine that stays up between runs.
A place to work
When a member writes software, it works in a place of its own: code, tests and git run in a throwaway environment that dies with the run.
From outside
A webhook starts a run. A scoped token lets something you trust call the OS. Another agent can run this enterprise through the same boundary.