Aura Link
The open-source local bridge that connects your machine to the Aura platform. Aura Link runs on your computer and lets Aura's AI agents read files, write code, and run commands in your actual project — securely, without uploading your codebase to the cloud.
How it works
Aura Web (War Room) ──► Aura Backend ──► Aura Link (your machine) ──► your project files
Aura Link opens a WebSocket connection to the Aura backend. When you approve a task in the War Room, the agent's file writes and shell commands are forwarded here and executed locally. Nothing leaves your machine except what the agent explicitly needs to read.
Installation
Option 1 — pip (recommended)
pip install aura-link
Option 2 — clone and install
git clone https://github.com/dev-aura-com/aura-link
cd aura-link
pip install -e .
Requires Python 3.11+.
Usage
Step 1 — log in
aura-link login
This opens a browser tab. Click Authorize and the CLI stores your credentials automatically — no token copying required.
Step 2 — connect your project
cd /path/to/your/project
aura-link connect
The CLI connects to Aura and watches for instructions. Leave this running while you work in the War Room.
Options
aura-link connect --url https://your-backend # custom backend URL
aura-link connect --dir /path/to/project # explicit project directory
aura-link connect --quiet # suppress status messages
aura-link logout # remove saved credentials
Environment variables
| Variable | Description | Default |
|---|---|---|
AURA_SERVER |
Backend API URL | https://api.dev-aura.com |
AURA_TOKEN |
JWT access token (alternative to aura-link login) |
— |
Security
- All file operations are jailed to the project directory — path traversal attempts are blocked.
.envfiles, private keys (*.pem,*.key,id_rsa, etc.), and any file matched by your.gitignoreare never sent to the cloud.- Destructive shell commands (
rm -rf /,sudo,shutdown, etc.) are blocked before execution. - The source code is fully open — you can audit exactly what Aura Link does before running it.
License
MIT
Release files for aura-link 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| aura_link-1.0.1.tar.gz | 14.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aura_link-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.2 kB
Release files / aura_link-1.0.1.tar.gz
| Download URL | aura_link-1.0.1.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6262689066b0bb425ec295a67f5fd722be82ebeb6055f80477e2f66e502852fc
|
|
BLAKE2b-256 checksum How to use checksums |
8d81721d5c65b82c5effb506ae63f26f98ed25396649a3869d4ec59d15392908
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 20, 2026.
Transparency logRelease files / aura_link-1.0.1-py3-none-any.whl
| Download URL | aura_link-1.0.1-py3-none-any.whl |
|---|---|
| Size | 16.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c050568b831b5026656fc2ecbe24d69529e1b4feef4cfdb93100f6dc454a8067
|
|
BLAKE2b-256 checksum How to use checksums |
ab6eb484857debe2939f55fc6a008ce42e917dca7e20e3a64cb2d4a1d9a5d574
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 20, 2026.
Transparency log