ARKTOR Go
A portable Windows remote-assistance core for explicit user-started sessions, outbound-only connectivity, provider-neutral control and signed optional modules without permanent service installation by default.
Why this product exists
Older or damaged Windows systems may not have enough local compute, installed tooling or stable configuration for effective AI-assisted repair. ARKTOR Go provides a temporary, auditable tool environment while the reasoning model can run remotely.
What it can do
- Portable Windows x64 execution with no permanent service required by default
- Outbound authenticated ARKTOR Link design with no inbound target port
- Bounded system, process and text-file primitives with explicit session lifecycle and audit
- SHA-256 and Ed25519-verified signed modules kept outside the small Core
How it works
- Start the portable ARKTOR-Go executable on the target Windows PC
- Approve the visible Windows elevation request when a full-control session requires it
- ARKTOR Go establishes its outbound authenticated device link without opening an inbound target port
- The authorised AI side uses built-in primitives or requests separately signed modules, then the session ends without installing 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 are proven on a real Windows target
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. The current ARKTOR Go 0.6 Rust target also passes 17 active tests with reconnect behaviour covered; one local Node-binary test is intentionally environment-gated.
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.
Live-tested 0.6.0 alpha with the portable v1 direction fixed and external Windows E2E verified through ARKTOR Link. Public availability remains gated by final signed-module distribution, production code signing, public one-click onboarding and release-soak validation.