Authorise a tool once with the narrowest scopes it needs. Astron reads context when a task requires it and proposes any write before it happens.
Development
Communication
Planning
Knowledge
Connectors become available in a workspace once their OAuth credentials exist on the deployment. Astron never displays a connection it does not hold.
Astron pulls the context a task actually requires, then acts through the tools you have authorised.
Summarize the latest project blockers and draft updates for the team.
Connectors activate once their OAuth credentials are configured. Astron never shows a connection it does not have.
How authorisation works
Astron requests the narrowest scopes needed for the capabilities you enable, and nothing more.
Tokens are stored server-side and are never sent to browser JavaScript, logs, or analytics.
Reads can run inside an agent loop. Writes always pause for a recorded human approval.
Expired, revoked, and permission-denied states are surfaced honestly with a reconnect path.
Astron records what it did, asks before it acts outside the workspace, and never reports success it did not achieve.
Read the security modelWorkspace isolation
Every query is scoped to a workspace you belong to, checked on the server.
Server held credentials
Provider keys and connector tokens never reach the browser.
Approval before external actions
Anything that leaves Astron waits for a recorded human decision.
Audit trail
Runs, tool calls, approvals, and decisions are written down and readable.
Memory you control
Inspect, disable, or delete anything Astron remembers.
Create a workspace, name your coworker, and give it something you have been putting off.
Get Astron