Live CI Debugging
Scrolling through thousands of log lines hoping to spot the issue. Push a debug statement, wait 20 minutes, repeat.
Tests pass locally but fail in CI. The container is gone before you can inspect anything.
Your local machine doesn't match CI. Different OS, different deps, different config. 'Works on my machine' at its worst.
Full terminal in your browser. Run commands, inspect files, check environment variables — all inside the actual CI runner.
Switch the interface to code-server and get a full VS Code IDE in your browser. Edit files, run debuggers, install extensions.
Every session gets a unique HTTPS URL with embedded credentials. Share it with a teammate — two pairs of eyes on the same environment.
Install from the GitHub Marketplace or the GitLab CI/CD Catalog. Works on Ubuntu, macOS, and Windows runners.
API key for production use, ephemeral tokens for quick debugging, or pre-existing credentials from the ASD CLI. Choose what fits your workflow.
Configure pipelines to pause instead of exit. Debug in the exact failing state before the container is cleaned up.
Generate an API key with cicd:provision scope in your ASD workspace. Add it as ASD_API_KEY in your CI provider's secrets.
GitHub: install asd-devinci from the Marketplace. GitLab: include the component from the CI/CD Catalog. One block of YAML.
DevInCi starts a web terminal or VS Code inside the CI runner and exposes it via a secure tunnel URL.
Open the URL in any browser. Full shell access to the exact environment where the failure happened. No SSH keys needed.
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci
- run: npm test
- name: DevInCi — Debug on failure
if: failure()
uses: asd-engineering/asd-devinci@v1
with:
api-key: ${{ secrets.ASD_API_KEY }}
tunnel-name: debug-${{ github.run_id }}Available on the GitHub Marketplace. Full setup guide → /en/howto/devinci-setup
Start free. No credit card required.