← Back to open sourceFeatured starting point
Learn the environment boundary before opening a coding agent from a phone or browser
T3 Code explained: the client controls work on another machineT3 Codepingdotgg/t3code
Start reading →Suggested learning path
01 → 09
01·3 min read·Search intent: Learning
Learn the environment boundary before opening a coding agent from a phone or browser
T3 Code explained: the client controls work on another machineT3 Codepingdotgg/t3code
·3 min read·Search intent: Learning
Install the client or CLI without confusing a running UI with a ready agent
T3 Code quickstart: choose one host and one providerT3 Codepingdotgg/t3code
·3 min read·Search intent: Learning
Make the environment reachable without moving files or credentials into the client
Deploying T3 Code for remote useT3 Codepingdotgg/t3code
·3 min read·Search intent: Learning
Follow a command through RPC, event log, outbox and provider work
T3 Code architecture: durable intent before agent side effectsT3 Codepingdotgg/t3code
·3 min read·Search intent: Learning
Use three entry points to separate authorization, durable state and actual execution
Reading T3 Code source: RPC, EventSink and EffectWorkerT3 Codepingdotgg/t3code
·3 min read·Search intent: Learning
Separate UI transport, server startup, provider usage and repository work
T3 Code performance and cost: measure the connection you actually useT3 Codepingdotgg/t3code
·3 min read·Search intent: Learning
Treat a remote control link as authority over the environment, not as a harmless URL
T3 Code security: pairing, scoped RPC and permission defaultsT3 Codepingdotgg/t3code
·3 min read·Search intent: Learning
Match the connection and permission model to the work you actually need
Choosing T3 Code: remote control surface or a simpler local CLI?T3 Codepingdotgg/t3code
·3 min read·Search intent: Learning
Turn a disposable trial into evidence before connecting important repositories
T3 Code next steps: validate one remote workflow end to endT3 Codepingdotgg/t3code
