ARKTOR Go
Take your ARKTOR to another Windows PC. Bring your AI connection and controlled tool environment to inspect problems, organise files, prepare migrations and recover useful knowledge — without making persistent remote access the default.
Who this product is for
People or teams who occasionally need to inspect, organise, migrate or troubleshoot another Windows PC without making permanent remote access the default.
The decision moment
You need a known ARKTOR environment on an older, weak or temporary Windows machine and want to leave with verified results rather than another installed dependency.
Bring your ARKTOR to the computer that needs attention.
Older Windows PCs often contain both problems and valuable information. ARKTOR Go is designed so you can bring a known AI-assisted environment to that machine, understand what is there, work on it under explicit control, and take useful results or selected knowledge back with you instead of rebuilding your whole workflow on the target PC.
One portable environment. Several practical jobs.
- Inspect and debug a Windows PC that still starts
- Understand, sort and structure old files and documents
- Prepare a cleaner migration to a new computer or archive
- Identify useful information worth keeping instead of copying everything blindly
- Bring selected, approved knowledge into ARKTOR Vault for later use
Evidence boundary: these are the intended product workflows. The current verified alpha proof covers portable Windows startup/control, authenticated Link and bounded system, file and process actions; it does not claim every workflow above is already a finished one-click feature.
What is retained and currently implemented
- Portable Windows x64 execution with no permanent service required by default
- Outbound session design with no inbound target port by default
- Bounded system, process and file work under explicit session control
- Permission-bounded modular capabilities
How it works
- Start ARKTOR Go explicitly on the target Windows PC
- Approve elevation only when the requested action genuinely requires it
- Establish the controlled outbound session
- Perform approved work and end the session without persistence by default
Portable by default. Persistent only by explicit choice.
Bring capable AI to weak or older Windows hardware without turning remote access into a permanent hidden dependency.
- The user explicitly starts the portable session; removable-media AutoRun is not part of the product model
- Elevation is requested only when the requested capability genuinely needs it
- The endpoint uses outbound connectivity and stores no AI-provider credential
- Closing the portable application ends the remote-access session by default; an installed service is not the normal mode
ARKTOR Go and Link have a retained real Windows proof
On 17 August 2026 the native owner path verified an online, owner-bound and elevated full-control session on an external Windows x64 target. Remote system.info, file listing, file reading and harmless process execution all completed successfully through ARKTOR Link. That retained proof remains valid for the tested build and path.
Latest product gate — 3 September 2026: the retained one-click build started, resolved its ARKTOR identity and completed system.info on SBKEE. A later step exposed a session-lifecycle regression during fresh release testing. This does not erase the 17 August E2E, but it means the latest release/product gate is pending, not “verified today”.
Portable packaging proof retained
The retained Windows x64 development build demonstrated that the portable product, its bounded execution layer and selected modular capabilities could be packaged and exercised together.
Boundary: internal module inventory, signing contract and packaging structure are engineering details rather than public product specifications.
What remains before a general public release
- The live signed-module distribution path is not yet a general public service
- Production code signing and public one-click Windows onboarding still require release validation
- Long-duration release soak remains a product-release quality gate rather than a functional E2E blocker
- Windows x64 is the first target; broader platform builds remain future work
Why portable, session-scoped AI access matters
Read Portable & Remote AI Assistance on Windows for the architecture, permission and persistence trade-offs behind this product direction.
ARKTOR Rescue — when Windows itself no longer starts.
ARKTOR Go assumes the target Windows system can still start. ARKTOR Rescue is now the separate bootable recovery path for machines that cannot. Physical V0.1 proof covers independent boot, controlled diagnosis, read-only Windows inspection and hash-verified data rescue.
Current boundary: continuous multi-reboot repair handoff is still the next milestone, and Rescue is not yet a general public release. Explore ARKTOR Rescue →
0.6.0 alpha with retained external Windows E2E from 17 August. The fresh 3 September product gate passed initial startup checks before a session-lifecycle regression blocked the full release workflow, so the latest release/product gate remains pending. Public availability remains gated by Link/release hardening, signed-module distribution, production code signing, public one-click onboarding and release-soak validation.