A source code control architecture. A client user checks out a copy of a source code file to the client using a file checkout process. A client cache maintains a pristine copy of the file, and a client activity list maintains a list of commands executed during the offline mode to effect modifications to the copy. The client cache contains a pristine copy of all source code files that are modified or deleted in a local client workspace. The cache is maintained whether the user is online or offline. When the user is offline, the cache is utilized to facilitate many of the activities that historically would require server connectivity. The command activity list allows a developer to continue changing the source code while offline by automatically recording the executed commands. The offline commands are reconciled to the server, and used to update the server file(s) when the client returns online.