currents.dev valid
Currents Documentation
For agents: Currents: cloud dashboard and test orchestrator for running and managing automated Playwright tests in CI, with API docs.
playwrighttest orchestrationci testinggithub actionstest dashboard
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T05:57:28.524Z. Cached copy · Source on currents.dev
# Currents Documentation
## Currents
- [Overview](https://docs.currents.dev/getting-started/readme.md): Currents is a cloud platform, dashboard and test orchestrator aimed to help SDET and Software Teams to manage the complexity of running automated tests in CI.
- [Quick Start](https://docs.currents.dev/getting-started/your-first-playwright-run.md): Running Playwright tests with Currents Dashboard
- [Set Up with an AI Agent](https://docs.currents.dev/getting-started/setup-with-an-agent.md): Set up Currents with Claude Code, Cursor, Codex or another coding agent, locally and in CI
- [CI Setup](https://docs.currents.dev/getting-started/ci-setup.md): Learn how to integrate Currents with your CI provider.
- [GitHub Actions](https://docs.currents.dev/getting-started/ci-setup/github-actions.md): Running tests with Currents in GitHub Actions
- [Quick Start](https://docs.currents.dev/getting-started/ci-setup/github-actions/playwright-github-actions.md): Running Playwright tests in Parallel in GitHub Actions using Matrix Workflow
- [Re-run Only Failed Tests](https://docs.currents.dev/getting-started/ci-setup/github-actions/re-run-failed-only-tests.md): How to set up failed test re-runs on GitHub Actions
- [Sharded runs](https://docs.currents.dev/getting-started/ci-setup/github-actions/re-run-failed-only-tests/re-run-failed-only-tests-sharded.md): How to set up failed test reruns for sharded Playwright runs on GitHub Actions
- [Orchestrated runs](https://docs.currents.dev/getting-started/ci-setup/github-actions/re-run-failed-only-tests/re-run-failed-only-tests-orchestrated-v2.md): How to set up failed test reruns for Orchestration on GitHub Actions
- [Custom CI Build ID for Re-runs](https://docs.currents.dev/getting-started/ci-setup/github-actions/re-run-failed-only-tests/custom-ci-build-id-for-reruns.md): How to configure custom CI build IDs for failed test reruns on GitHub Actions
- [Cancel Runs on Workflow Cancellation](https://docs.currents.dev/getting-started/ci-setup/github-actions/cancel-runs.md): Cancel the Currents run when a GitHub Actions workflow is cancelled
- [Commit data for GitHub Actions](https://docs.currents.dev/getting-started/ci-setup/github-actions/commit-data-for-github-actions.md): How to get correct git commit information when using GitHub Actions
- [Custom Docker runners](https://docs.currents.dev/getting-started/ci-setup/github-actions/custom-docker-runners.md): Self hosted/managed docker runners
- [Named Runners](https://docs.currents.dev/getting-started/ci-setup/github-actions/named-runners.md): Github Actions provides the ability to use human-readable runner names, and Currents displays these in the dashboard, allowing you to see which runner executed each spec file.
- [GitLab](https://docs.currents.dev/getting-started/ci-setup/gitlab.md)
- [Quick Start](https://docs.currents.dev/getting-started/ci-setup/gitlab/playwright-gitlab-ci-cd.md): Running Playwright test in parallel using GitLab CI/CD
- [Re-run Only Failed Tests](ht
…
Related sites
Other listed sites in AI and machine learning. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| sourcey.com | Sourcey | interface AI and machine learning AI agents and MCP | — | 70 | ✓ | ✓ | |
| gofrantic.com | Frantic | interface AI and machine learning AI agents and MCP | — | 61 | ✓ | ||
| intellweb.ai | Intellweb | documentation Ecommerce Productivity +3 | US | 61 | ✓ | ✓ | |
| agentwebmap.com | Agent Web Map | interface AI and machine learning AI agents and MCP +1 | FR | 60 | ✓ | ✓ | |
| cloudflare.com | Cloudflare | interface AI and machine learning Cybersecurity +1 | — | 85 | ✓ | ✓ | |
| adobe.com | Adobe Tools | transactional AI and machine learning Design +1 | FR | 75 | ✓ | ||
| taboola.com | Taboola.com | documentation AI and machine learning Marketing | — | 75 | ✓ | ✓ | |
| opera.com | The Opera browser overview | documentation Infrastructure AI and machine learning +2 | NL | 74 | ✓ |
Machine-readable: GET /v1/resolve?q=currents.dev · GET /v1/domain/currents.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage currents.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for currents.dev:
1. POST https://agentwebmap.com/v1/sites/currents.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://currents.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/currents.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/currents.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.